Are bad rip checksums poisoning the AccurateRip database?

[PhilArmstrong]

I've just been going through my CD collection & re-ripping it with a tool that uses the AccurateRip database. I've discovered that a few "fake CD" cds (specifically in my case the Lord of the Rings soundtrack CDs) are in the AccurateRip database with complete with errors: ie, if I rip them on a drive that doesn't do C2 correction (or feed the C2 data to the ripper) then I get a rip which is given the all clear by the AccurateRip database entry for those CDs, despite the errors in the data.

Since you can hear the noise on the recordings (cracles, hissing and pops) I'm quite surprised at this, but there you go. It looks like people have been pushing rips up to the database which are in fact *in*accurate, and there's enough of them that the accurate rip confidence values are high.

http://www.accuraterip.com/accuraterip/4/4/4/dBAR-019-00292444-0252c7ba-2611c614.bin

is one example.

Can anything be done? I guess just be on the lookout for 'fake CD' CDs and actually listening to the rip is going to be the only way to be sure given that the AccurateRip database has been poisoned by poor rips for these CDs.

[Fortune]

Re: Are bad rip checksums poisoning the AccurateRip database?

Phil,

If I've understood you correctly then am not sure this is a problem is it?

If you have ripped a fake copy of Lord of the Rings soundtrack....and it verifies against accurate rip (lets say confidence 5 for arguements sake) then this just means 5 other people have ripped the same fake cd. Therfore you can be confident you have correctly ripped your fake and all of its crackles and hisses have been faithfully reproduced!

If however, you rip an non-fake copy of the same disc then it would ( i would hope!) only match against the same genuine disk rips and NOT the 5 fakes.

ie. In this case the fake cd can be considered a different pressing.

If thats not the case, and a fake cd is matched against a valid cd (or vica versa) then there is big problem of course !

Does that make sense or have i misunderstood your post?

Cheers.

[brian2090]

Re: Are bad rip checksums poisoning the AccurateRip database?

I think he is saying that enough erroneous data has been submitted from CDs which exhibit consistent errors, vs. when he uses C2 error correction, that the same disc has error-rich and error-free database info available.

[Spoon]

Re: Are bad rip checksums poisoning the AccurateRip database?

If someone submits a bad result, it would not appear in the database, because it has to be verified by someone else to appear. However even if it did appear in the database, it would be on its own, your rip would not match this bad rip, even if your rip was bad, because it would create a different result, there are 4 billion different possibilities for results.