AccurateRip problems - filesize differences

[Amadablam]

I've been testing out AccurateRip today and have had a couple problems. The main problem I wanted to bring to your attention was that AccurateRip seems to be producing files that are a couple bytes larger than those I can produce with EAC and cdparanoia. Using the WAV Compare in EAC tells me all the files are the same, but there's something about the file ripped with AccurateRip that is making it 2 bytes larger. Any ideas?

Also, I frequently am unable to rip some of the tracks from a CD, particularly the first track. I get the error:

CODEC decompression error for \\CDROM\Track01.cda
Unable to Rip track - make sure correct Ripping method is selected and CD Drive supports digital audio extraction.

I've changed some of the options for my drive, like the read command and the CD Communication, but still no luck.

But keep up the good work! I think the AccurateRip concept is an excellent idea and I hope its usage spreads. I'd really like to see it integrated with cdparanoia, and I'll be adding my CDs to the database when I know everything is working correctly. Thanks!

[Spoon]

dBpowerAMP writes a WAVEFORMATEX header, rather than a WAVEFORMAT (it needs to as it creates compressed wave files as well). Headers are different, data is identical.

You might try the Spin up option for your drive, see if that helps.

[Amadablam]

Ah - the differences in the header certainly explains how the filesize could be different. It doesn't help me much when using md5sum to compare files, but that's just fine.

I messed around with other AccurateRip options, like spin-up and drive speeds, and neither helped. What did fix the problem, however, was resetting the status, thereby eliminating the offset settings. This again leads me to believe there's a problem dealing with the lead-in on track 1...any other ideas? I believe I've tried 4 or 5 albums so far (with multiple attempts to rip track 1 on each) and every one has failed.

Thanks again!

[Unregistered]

So my Toshiba drive won't read the first track because it has a negative offset correction...but I have a Mitsumi drive with a positive offset correction, so it reads the first track just fine, but can't properly read the last track. While not convenient, I can use both drives to get a perfectly-read copy. Are my results still useful for the AccurateRip database? The results will show that I'm ripping part of each CD twice. I'd like to help out, but want to make sure my data is going to be useful. Thanks!

[Spoon]

Your data will be useful both results