CardinalFang;316984 Wrote: > That's an interesting comment. > > Surely if any other ripping tool were being used it would be using the > same drive and unless the CD were damaged, there would be very little > error concealment going on, only error correction, which by definition > fixes up any read errors. Why would iTunes be worse? It's always worked > well for me.
The issue is handling read errors. It is actually very difficult to detect a read error for audio CDs. Some drives handle errors better than others, however non of them are consistent in how they handle the errors. You can get read errors from a brand new CD. What programs like EAC and dbpoweramp do is read the data over and over until they get the same result back a certain number of times. Which is why they are slower. They also do things like fluch the drives cache to avoid rereading the cache data. Drive offset is another thing to take into account too, each drive has a different offset value. dbpoweramp determines this by comparing your drives read of certain key discs to other drives results it keeps on a server. It also uses this data on the server to determine if your reads for a certain disc corresponds to other peoples reads of the same disc to help identify if you get a good read. He says it better: http://www.dbpoweramp.com/spoons-audio-guide-cd-ripping.htm -- m1abrams ------------------------------------------------------------------------ m1abrams's Profile: http://forums.slimdevices.com/member.php?userid=850 View this thread: http://forums.slimdevices.com/showthread.php?t=49492 _______________________________________________ audiophiles mailing list audiophiles@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/audiophiles
