A secure ripper for linux
Reply #6 – 2005-10-31 20:27:40
Though I did mention the module, I made it more clear now. About drives that cache being useless: Is it really absolutely impossible to have a correct rip from them? According to my knowledge cdparanoia can't handle any error correction. But does it always need error correction to provide a correct rip? [a href="index.php?act=findpost&pid=338602"][{POST_SNAPBACK}][/a] I think the problem is that drives that cache do not report an error as they re-read the data from their cache instead from the CD. However, if you rip the complete track twice and compare the CRCs, caching is no problem (like in EAC's test© feature). But then you also don't need any "secure" ripping methods, you can just as well rip in burst mode, which is way faster.Therefore, using "secure" ripping methods with "test©" feature is pointless, as the matching CRCs are safety enough. And for error correction through re-reading (as in EAC's secure mode), drives that cache audio are worthless because, as said above, they re-read from their cache instead of trying to read the disc again. The only way to avoid this is to DISABLE the cache as e.g. EAC and Plextools Pro can do. So, the real challenge is to find a way to disable the cache in conjunction with cdparanoia. Then, it would probably have the same usefulness for secure rips as EAC. As for error correction, this is not necessary for perfect rips as long as the discs have no errors