Hello there.
There are certain AccurateRip results that have been puzzling me lately:
[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
[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.
Okay, I did some further research and realized that the second log basically meant that the rip was not accurate, just as I had suspected. By a sheer coincidence, a friend of mine had just ran across the same record (thank goodness we have the same taste in music), so I was able to "successfully" re-rip it.
01 [79571c8e] (0/1) No match but offset
02 [c4cb2031] (0/1) No match but offset
03 [424a929d] (0/1) No match but offset
04 [24530152] (0/1) No match but offset
05 [0df1acfd] (0/1) No match but offset
06 [390876de] (0/1) No match but offset
AccurateRip v2:
01 [f7ac13a2] (1/1) Accurately ripped
02 [8b23eb0e] (1/1) Accurately ripped
03 [a023c4e2] (1/1) Accurately ripped
04 [82905f87] (1/1) Accurately ripped
05 [bc6e3857] (1/1) Accurately ripped
06 [6c7aaee8] (1/1) Accurately ripped
You've no idea how relieved I am.
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 V
1 CRC results, the bottom half AccurateRip V
2 CRC results.
No match but offset in the upper half suggests your files start off correctly but don't match the V
1 CRCs. The
Accurately ripped in bottom half shows they do match the V
2 CRCs.
The next version of Cuetools will put the V
1 and V
2 results side-by-side (V
1+V
2/Y), so your results would look like
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