I've been doing some more testing on the EAC vs. cdparanoia/cdrdao subject (the original post is here). This time I've checked the EAC rips against cdparanoia ones and got some strange results once again!
The CD drive is once again Pioneer DVR-110D (1.41+TDB):
Read offset correction: +48
Caches audio (2000 Kb)
Overread: Lead-out
Ripping 1 CD as a single wav.
Cdparanoia version: 10pre1 (svn) with an altered readahead value, OS: Ubuntu Feisty
Here's what I have found out so far:
- md5sums of EAC and paranoia rips never match, but see #2;
- audio data is BYTE IDENTICAL, found this out by comparing individual frames;
- audio data is sometimes different on scratched places (which EAC calls suspicious)
- With offset correction set, EAC successfully overreads into lead-out, but FAILS to "overread into data track": when dealing with cdextra/cdplus media, the rip length is not a multiply of 588 frames - there are 48 missing samples in the end, which means that the rip is truncated! Shouldn't it ALWAYS divide by 588 (2352 bytes)?
- When ripping the same (cdextra) CDs with cdparanoia, I get the rips with filesize = 44 + 2352 * frames. At least, cdparanoia always outputs redbook-compatible audio files.
- cdparanoia in fact did not overread to lead-out, but appended 48 zero frames to the end of rips. I've stumbled upon this with a CD with a last track filled with noise to the very end. Byte-comparing the rips revealed, that last 48 frames in paranoia rip are zeroes. EAC rip contained some audio in this place...
So, EAC failed to overread into data track, cdparanoia failed to overread into lead-out. This makes me think that neither one is the perfect tool. What do you guys think?
P. S. Forgot to mention, that most rips were actually 100% sample-identical, so I think, it's still okay to rip with cdparanoia if you're not after perfect backups
