Skip to main content

Topic: What to do if I found a disc's CRC wrong in AccurateRip database? (Read 2903 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • YumeYao
  • [*]
What to do if I found a disc's CRC wrong in AccurateRip database?
Hi, I'd like to know is there a way to report this to AccurateRip's database so it could get fixed.

I have a cd drive of model "ATAPI - DVD A  DH16ABSH", which is listed on AccurateRip's model list, with a offset of 6.
Also I have verified this offset with some other discs(including 'key discs'), they all gave me 'accurate rips'.

The program I used were EAC 1.00b2 and foobar2k 1.1.18.
EAC just simply reports CRCs don't match:
Quote
AccurateRip summary

Track  1  cannot be verified as accurate (confidence 2)  [1682E82B], AccurateRip returned [5F69F537]  (AR v2)
Track  2  cannot be verified as accurate (confidence 2)  [4FE13BF2], AccurateRip returned [020682CC]  (AR v2)
Track  3  cannot be verified as accurate (confidence 2)  [B180CA80], AccurateRip returned [0894D985]  (AR v2)
Track  4  cannot be verified as accurate (confidence 2)  [5308F85E], AccurateRip returned [EDA9AC80]  (AR v2)
Track  5  cannot be verified as accurate (confidence 2)  [68204D4E], AccurateRip returned [1657B595]  (AR v2)
Track  6  cannot be verified as accurate (confidence 2)  [33367808], AccurateRip returned [5C8979F0]  (AR v2)
Track  7  cannot be verified as accurate (confidence 2)  [5D347CDA], AccurateRip returned [FDD52D5B]  (AR v2)
Track  8  cannot be verified as accurate (confidence 2)  [299FAA13], AccurateRip returned [B9DB361D]  (AR v2)
Track  9  cannot be verified as accurate (confidence 2)  [4C9694AE], AccurateRip returned [BA9F7967]  (AR v2)
Track 10  cannot be verified as accurate (confidence 2)  [F50F5DD2], AccurateRip returned [E2402413]  (AR v2)
Track 11  cannot be verified as accurate (confidence 2)  [21B70EB8], AccurateRip returned [925ABF57]  (AR v2)

No tracks could be verified as accurate
You may have a different pressing from the one(s) in the database

While I know fb2k will try to calculate (and match) CRCs using different offsets, so I used fb2k also, and the output:
Quote
AccurateRip status:
Track  Status
01    Accurately ripped with offset: -515(2).
02    Accurately ripped with offset: -515(2).
03    Accurately ripped with offset: -515(2).
04    Accurately ripped with offset: -515(2).
05    Accurately ripped with offset: -515(2).
06    Accurately ripped with offset: -515(2).
07    Accurately ripped with offset: -515(2).
08    Accurately ripped with offset: -515(2).
09    Accurately ripped with offset: -515(2).
10    Accurately ripped with offset: -515(2).
11    Accurately ripped with offset: -515(2).


FWIW, I have several questions:
Does the confidence 2 in EAC's report refers to there were 2 reports to the accuraterip database before?
And so does the (2) in fb2k's report?

Since I could verify my drive and my ripping settings with different discs, while all other discs I've tried reported exact match, does it mean the probability of wrong CRCs in accuraterip database?

So if I think the CRCs in accuraterip database is not correct, is there a way to fix it?

P.S.
The problematic disc is "小松未歩 - 謎"(Miho Komatsu - Nazo), a jpop disc released in 1997.

EDIT:
(I think) I know exactly what the terms such as read offset, jitter, C2 error, etc. mean, and I know how audio cd is differenct from data cd.
And yes, I know I could simply achieve 'Exact Audio Rip' by just ignoring these and I don't plan to do 'Exact Audio Copy'(means I don't plan to burn it, etc..). But thanks to fidelity, I want to achieve 'Exact Audio Copy'.
  • Last Edit: 15 July, 2013, 01:20:02 PM by YumeYao

  • Anakunda
  • [*][*][*][*][*]
What to do if I found a disc's CRC wrong in AccurateRip database?
Reply #1
You may try to use CUetools to reecnode the tracks with corrected offset, there's an option for automatic fix

  • korth
  • [*][*][*][*][*]
What to do if I found a disc's CRC wrong in AccurateRip database?
Reply #2
does it mean the probability of wrong CRCs in accuraterip database?

EAC can't do cross-pressing verification (it only reports if other entries exist if an exact match to your pressing isn't found). The alternate pressing reported by FB2K is similar to your disc but the CRCs in the AccurareRip database are for that pressing not yours. However you now know your disc is accurate.

You may try to use CUetools to reecnode the tracks with corrected offset, there's an option for automatic fix

Encoding to match the offset of a different pressing is not necessary.
  • Last Edit: 15 July, 2013, 02:13:34 PM by korth
korth

  • YumeYao
  • [*]
What to do if I found a disc's CRC wrong in AccurateRip database?
Reply #3
does it mean the probability of wrong CRCs in accuraterip database?

EAC can't do cross-pressing verification (it only reports if other entries exist if an exact match to your pressing isn't found). The alternate pressing reported by FB2K is similar to your disc but the CRCs in the AccurareRip database are for that pressing not yours. However you now know your disc is accurate.


Thanks for the explanation. I thought CDs produced by the same maker to be totally same and only different versions (such as releases in different countries) to have this problem, but definately I was wrong.

  • spoon
  • [*][*][*][*][*]
  • Administrator
What to do if I found a disc's CRC wrong in AccurateRip database?
Reply #4
Discs are created in batches, or pressings, each pressing can have a different built in offset.