That realy lame comment about “NO CDEX does not have a decent secure mode” gives me the opportunity to comment on technical matters so that even someone like mp3dude learns something (after all, even monkeys are able to learn something new). The ripping procedure followed by CDex and almost any ripping prog out there, when combined with a decent modern drive and the right read speed, will give perfect results on 99% of all cases. The right read speed is not necessarily low, as it can be 12x or higher (and this is the case with many modern drives, where the extra checks implimented in hardware are much improved compared to what was the case 2-3 years ago). For example, most Pioneer and rebadged dvd drives are locked at a speed of 12x, which is manufacturer verified to give perfect results. The rest 1% has to do with scratched cd’s, which is the only case where algorithms like the one implimented in EAC can be really useful. In other words, “secure mode” has a meaning only when you rip a scratched or damaged cd. This can be tested by anyone, including those using cdfs.vxd. Rip from a reasonably clean cd a dozen times and compare the results. As for mp3 encoding, the --r3mix you brag about is about JS. Being one of those able to distinguish JS from S, I can say this doesn’t sound like a quality setting. With a lossy format like MP3, it all comes down to personal preferences and kind of music. The article about LAME 3.89 which got mentioned on CD Freaks a few days ago just shows how contradictory opinions on the “right” settings can be. As you can see, I can give facts and not cheap shots about “ripping securely”. So, next time you want to talk about who knows shit check your diapers first.