I have a problem .EAC seems to have a problem reading cds with errors on 'em (that is 'errors' as in: ............. )
There is no known way to be sure that you have 100% accurately got the data from the CD correctly, especially if the CD is scratched.
1) CD Audio Reading is not a 100% repeatable process with identical results from one rip to another
2) If you have scratches that are beyond the error correction mechanism of CD-readers, then you are out of luck
3) Copy protected CDs add another layer of problem: is the original data on the master before the copy protection was applied (which destroyed some original data as it was applied) what you are after? Or is the copy protected, non-original (in terms of the studio master) data with erroneus C2 data, what you are after?
4) AccurateRip can only give you information that another people got the same result.
What exacty do you mean by "EAC has problems reading CDs with errors". Does it say "there were errors" after extraction finished?
...since EAC is very accurate at reporting errors, but it often can't actually correct them
( BTW, If your answer is No, EAC claims to have a good rip, but I hear pops", then you have probably misconfigured EAC, or using it badly )
... well, there are a few things you can do:
4) AccurateRip can only give you information that another people got the same result. It is statistically a good approach against random errors (such as scratches), but is not perhaps the optimal tool for copy protected discs. Why? Two erroneus rips will be the same if neither of them was able to circumvent the copy protection and there were no scratches
Then, @ DrDoogie: it depends on how you define 'guaranteed correct'... 100% sure you'll never be, but yes we can come pretty close For the rest: This seems to be thestory of the glass of beer.. . Is it half-full, or is it half-empty?
No. It happily rips two different copies of the same CD. With a plextor w1210A firmware 1.10 at 14-32x CAV, mind. Haven't tried at 8x CLV yet... but maybe I should.
Quote...since EAC is very accurate at reporting errors, but it often can't actually correct themIsn't it the DRIVE's responsibility to report C2 errors? Hummmm?
Ripping in Test&Copy mode and getting a CRC mismatch, or WAV compare, are good (secure) ways to be sure of that. Assuming you have done something similar, my guess is the EAC drive options are not correctly set. This can be easily verified: Go to: EAC > Drive Options and set your drive's settings 'safe', i.e.: * Accurate stream: No * Caching: Yes * C2: NoNow rip again & see if you get 2 identical rips...
DrDoogie,Your flag says you are based in Iraq, and ripping a perfect CD is your biggest problem?DUCK! For God's sake, DUCK!
I daresay it is you who are using the wrong settings, my good man...
Aren't you, with these settings, DISABLING ALL (C2) ERROR CHECKS?
QuoteAren't you, with these settings, DISABLING ALL (C2) ERROR CHECKS?No, EAC is software, not firmware. It can't change your drive's working at all. Disabling C2 means: EAC will always read twice, even if your drive says it is not needed (C2 info says 'data ok')
QuoteThere is no known way to be sure that you have 100% accurately got the data from the CD correctly, especially if the CD is scratched.I've read up on this a bit now, and I disagree with the above claim.*) If you have a drive that reports C2 errors with a 100% reliability (oh please God, make it exist!)*) And you get no C2 errors when reading the CD*) GOTO ::ReadGoodCD...
So it reads twice. Allrigh-tee-then.And reading an audio stream twice... does what exactly?Does it guarantee you an error free rip? I cannot see that it does, given that there is the chance that the stream will be "wrong" both times. Does it increase the probability that you have read the stream correctly? I don't see that it does, given that if there is an unrecoverable (C2) error
Well, actually errors 'always' (99.99...%) return different data for every new read.
QuoteWell, actually errors 'always' (99.99...%) return different data for every new read.How do you know that? it might be 60%, or 10%, because it cannot detect when the data is the same you cannot put a % on it. When AccurateRip makes its way onto EAC then you could put a percentage on it.