I’m preparing to transfer our collection of ~500 - 700 CD-based music to digital storage. The immediate driver is to load up a portable music player so my wife can carry her music around with her. My “user” goals are to:
- (generally) rip each CD one time only,
- create an on-line (in-home) catalogue of music,
- create "playlists" targeted for different devices (portable player, CDs, home entertainment system /situations without being tied to artist-album restrictions.
- cull/trim our music collection down to the wanted stuff (keep the one-hit wonders and dump the rest of the album).
- as necessary, archive to off-line storage (DVD-?)
Nothing earth-shattering here, just clarifying that 1-to-1 CD copying and mass on-line file-sharing are not my goals.
Not exactly a "first adapter" on the portable music scene, I expected to be spoiled for choice for integrated SW packages that would meet my needs while focusing on maintaining the quality of the audio tracks and their metadata. Well, I’ve learned lots from the HA forums, about issues I didn’t know were “issues” ‘til I researched here. Thanks, (I think, inspite of the headaches
My initial and most fundamental question concerns CD ripping. Seems that until (circa 2000 ?) Andre Wiethoff developed an audio data “fetch” function that utilizied multiple read-and-compare, it was possible to acquire erroronous track copies. Here’s my understanding – cobbled together from my research -- of the technical basis of the problem:
- the storage format used on audio CDs does not include any data integrity info. Makes sense for the original purpose of linear time replay, but short-sighted from a track-as-digital-record perspective.
- The only way to (absolutely?) know if there is a read error of audio data is to do multiple read and compare. (And EAC’s secure method is the only, and propriatary, approach to the problem.)
- (put another way) there is no technical way (i.e. outside of the user making a knowledgeable assessment of the physical condition of the disc) for an application to “know” if a bad read is/will occur short of actually performing a read.
Therefore, you want an accurate track read, you need to use EAC.
But some, notably rjamorim (who does not seem to me to be complacent about audio quality
So, is this a molehill or a mountain?
- Were all you practicing digital audiophiles plagued by inexplicably error-ridden audio tracks until EAC came along? Life is now good, sounds are all sweet?
- Is EAC finding “false positives” at least in the sense that most of the read errors do not result in audible errors (the only kind that matters in the end).
- Is my construction of the technical problem wrong? Do some rippers have some means of informing the user that a track read is, or might be wrong? (Only then turning to EAC to try again ….)
- Or, given that there are multiple rippers available, do you use EAC only when you expect there to be trouble with a disk? If so, what criteria do you use? (though I realise that could really be a can of worms so don’t kill yourself trying to answer that….)
I think I understand that one suggestion is that to use other rippers (reasons of ease, speed, etc.) for ripping but fall back to EAC for tracks that sound bad. While that is reasonable method in one rip sessions, I would wish to have the ripping work unattended, but maybe that a source of difference in approach (wish I had the equipment, ears, and time to follow that approach for my project
Futurewise, if EAC is the needed, gold standard of ripper to guarantee a good data read, any further update on whether Andre would contemplate releasing his work under a GPL arrangement so that it could be incorporated elsewhere, e.g. dBpowerAmp?
Thanks for helping get set on the best direction.
Ciao for now.