IPB

Welcome Guest ( Log In | Register )

Interpreting certain AR results
Dario
post Apr 13 2012, 20:05
Post #1





Group: Members
Posts: 158
Joined: 20-September 11
Member No.: 93842



Hello there.

There are certain AccurateRip results that have been puzzling me lately:

CODE
[AccurateRip ID: 000b319b-0041b438-6b088407] found.
Track   [ CRC    ] Status
01     [0f7071cf] (0/3) No match but offset
02     [cc2e97d5] (0/3) No match but offset
03     [4b13addd] (0/3) No match but offset
04     [5902a690] (0/3) No match but offset
05     [ede2aafd] (0/3) No match but offset
06     [4765cef8] (0/3) No match but offset
07     [6f1c3b0f] (0/3) No match but offset
AccurateRip v2:
01     [8f3cd2dc] (3/3) Accurately ripped
02     [78c0b244] (3/3) Accurately ripped
03     [7dd47c9a] (3/3) Accurately ripped
04     [aac1d9a2] (3/3) Accurately ripped
05     [38afe031] (3/3) Accurately ripped
06     [cab3d6ff] (3/3) Accurately ripped
07     [42d3b401] (3/3) Accurately ripped


CODE
[AccurateRip ID: 00079f34-00299f0d-4808ef06] found.
Track   [ CRC    ] Status
01     [79571c8e] (0/1) No match but offset
02     [827ab2de] (0/1) No match but offset
03     [d187caca] (0/1) No match but offset
04     [0705728c] (0/1) No match but offset
05     [8d4ecb5e] (0/1) No match but offset
06     [eb713fe4] (0/1) No match but offset
AccurateRip v2:
01     [f7ac13a2] (1/1) Accurately ripped
02     [48d03cc1] (0/1) No match but offset
03     [2f5e0e10] (0/1) No match but offset
04     [653ffd03] (0/1) No match but offset
05     [3bc89dc3] (0/1) No match but offset
06     [1ee0a3e8] (0/1) No match but offset


What would "No match but offset" suggest here? I've read that it's used as some kind of a "pressing-detector", but couldn't understand much (sorry). The second log comes from a rather rare record that I no longer own (and wasn't in AR's database at the time it was ripped), so I'd really like to resolve this. Note that there are no audible glitches whatsoever, and as far as memory serves me, the CD was not scratched or anything.

Thank you for your assistance.
Go to the top of the page
+Quote Post
 
Start new topic
Replies
korth
post Apr 16 2012, 04:01
Post #2





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



The results you posted are from a CUETools log.
No match but offset suggests that there is an AccurateRip record at that offset, your file data starts at that offset, but the CRC of your file doesn't match the CRC in the AccurateRip record.
To further confuse you. The top half of the log shows AccurateRip V1 CRC results, the bottom half AccurateRip V2 CRC results. No match but offset in the upper half suggests your files start off correctly but don't match the V1 CRCs. The Accurately ripped in bottom half shows they do match the V2 CRCs.
The next version of Cuetools will put the V1 and V2 results side-by-side (V1+V2/Y), so your results would look like
CODE
Track [ CRC | V2 ] Status
01 [79571c8e|f7ac13a2] (0+1/1) Accurately ripped
02 [c4cb2031|8b23eb0e] (0+1/1) Accurately ripped
03 [424a929d|a023c4e2] (0+1/1) Accurately ripped
04 [24530152|82905f87] (0+1/1) Accurately ripped
05 [0df1acfd|bc6e3857] (0+1/1) Accurately ripped
06 [390876de|6c7aaee8] (0+1/1) Accurately ripped



--------------------
korth
Go to the top of the page
+Quote Post

Posts in this topic


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: 25th July 2014 - 10:07