IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
What to do if I found a disc's CRC wrong in AccurateRip database?, [moved from General Audio/TOS #6]
YumeYao
post Jul 15 2013, 18:07
Post #1





Group: Members
Posts: 10
Joined: 26-November 08
Member No.: 63204



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'. smile.gif

This post has been edited by YumeYao: Jul 15 2013, 18:20
Go to the top of the page
+Quote Post
Anakunda
post Jul 15 2013, 18:22
Post #2





Group: Members
Posts: 456
Joined: 24-November 08
Member No.: 63072



You may try to use CUetools to reecnode the tracks with corrected offset, there's an option for automatic fix
Go to the top of the page
+Quote Post
korth
post Jul 15 2013, 18:52
Post #3





Group: Members
Posts: 429
Joined: 13-March 11
Member No.: 88969



QUOTE (YumeYao @ Jul 15 2013, 18:07) *
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.

QUOTE (Anakunda @ Jul 15 2013, 18:22) *
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.

This post has been edited by korth: Jul 15 2013, 19:13


--------------------
korth
Go to the top of the page
+Quote Post
YumeYao
post Jul 15 2013, 19:45
Post #4





Group: Members
Posts: 10
Joined: 26-November 08
Member No.: 63204



QUOTE (korth @ Jul 16 2013, 01:52) *
QUOTE (YumeYao @ Jul 15 2013, 18:07) *
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. laugh.gif
Go to the top of the page
+Quote Post
spoon
post Jul 16 2013, 09:47
Post #5


dBpowerAMP developer


Group: Developer (Donating)
Posts: 2745
Joined: 24-March 02
Member No.: 1615



Discs are created in batches, or pressings, each pressing can have a different built in offset.


--------------------
Spoon http://www.dbpoweramp.com
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 23rd August 2014 - 00:00