Skip to main content
Topic: Strange AccurateRip results from a 2-disc CD rip in EAC (Read 235 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Strange AccurateRip results from a 2-disc CD rip in EAC

Hello all,
New guy here  :)

I have a 2-CD combo of Bob James / Restoration: The Best of Bob James which I tried to convert to flac yesterday.
Both discs copied without any problems but the AccurateRip gave me very strange results:
while the 2nd disc was accurately ripped with confidence of 1, disc #1 gave me this message:

AccurateRip summary
 
Track  1  cannot be verified as accurate (confidence 15)  [FC4484E8], AccurateRip returned [AD33448E]  (AR v2)
Track  2  cannot be verified as accurate (confidence 15)  [A8AF8979], AccurateRip returned [569D72B6]  (AR v2)
Track  3  cannot be verified as accurate (confidence 15)  [960058A1], AccurateRip returned [5319C892]  (AR v2)
Track  4  cannot be verified as accurate (confidence 13)  [C65A0B39], AccurateRip returned [0B7BA855]  (AR v2)
Track  5  cannot be verified as accurate (confidence 14)  [9FCAD665], AccurateRip returned [E6616F6D]  (AR v2)
Track  6  cannot be verified as accurate (confidence 14)  [4E788448], AccurateRip returned [A2D85268]  (AR v2)
Track  7  cannot be verified as accurate (confidence 13)  [EC653FA5], AccurateRip returned [FCB808A2]  (AR v2)
Track  8  cannot be verified as accurate (confidence 14)  [BCBA4F75], AccurateRip returned [5DE183C5]  (AR v2)
Track  9  cannot be verified as accurate (confidence 15)  [CEC7260B], AccurateRip returned [7ABE98A7]  (AR v2)
Track 10  cannot be verified as accurate (confidence 14)  [9B08C8D5], AccurateRip returned [7C2D28D9]  (AR v2)
Track 11  cannot be verified as accurate (confidence 14)  [429A6766], AccurateRip returned [6CD9A1D4]  (AR v2)
Track 12  cannot be verified as accurate (confidence 14)  [59912D6F], AccurateRip returned [BF8CFC59]  (AR v2)
Track 13  cannot be verified as accurate (confidence 12)  [78F47052], AccurateRip returned [6240A144]  (AR v2)
 
No tracks could be verified as accurate
You may have a different pressing from the one(s) in the database

------------------------------------------------------------------------
Any idea why AccurateRip gave such different results for 2 discs that came in the same box?

Thanks in advance!

Re: Strange AccurateRip results from a 2-disc CD rip in EAC

Reply #1
Where's the rest of the log?

CD1 is possibly an alternate pressing that has no entries in the database (yet).
korth

Re: Strange AccurateRip results from a 2-disc CD rip in EAC

Reply #2
Where's the rest of the log?

CD1 is possibly an alternate pressing that has no entries in the database (yet).

Sorry,
here are both of the logs attached.

Re: Strange AccurateRip results from a 2-disc CD rip in EAC

Reply #3
The CUETools DB Plugin results for CD1 support an alternate pressing. All tracks verified as accurate. CTDB (the CUETools DataBase) stores all like pressings together in one record.
The AccurateRip database stores like pressings separately but grouped side-by-side under the same ID. The AccurateRip plugin in EAC can only look for matches to your RIP and can't check for alternate pressings. If exact matches to your CD aren't found but other records exist, the AccurateRip plugin returns the 'cannot be verified as accurate' message along with information about the first record found, how many times that record was submitted and how the CRC differs from your RIP.

Exact matches for CD2 were found but the confidence is only 1 (only one RIP was submitted so far).

Edit:
   The reason I mentioned CD2 only having one entry was to explain another trait of the AccurateRip database. If only one set of checksums (CRCs) are submitted for a particular CD layout, then the RIP goes into the database. If other checksums for that CD layout already exist, only checksums submitted two or more times stay in the database. Any checksum submitted only once is removed and stored in limbo. The checksum entries are returned to the database when confirmed by a second RIP.
   Once your RIPs are submitted and the database is updated, your RIP of CD1 could confirm a previous RIP submitted at the same time as CD2 but placed in limbo because the checksums were unique and non-matching checksums already existed. Or perhaps the checksums from your RIP could be unique and they will go into limbo awaiting confirmation by a second RIP.
   All of this has been covered several times and can be found by searching the forums.
korth

 

Re: Strange AccurateRip results from a 2-disc CD rip in EAC

Reply #4
Thank you very much for explaining this!
I really appreciate it!

 
SimplePortal 1.0.0 RC1 © 2008-2018