Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: CUETools AccurateRip vs foobar2000 v2.0 AccurateRip verification? (Read 1589 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CUETools AccurateRip vs foobar2000 v2.0 AccurateRip verification?

What is the difference between CUETools AccurateRip results and foobar2000 v2.0 AccurateRip results?

One says the rip is not accurate, the other says it is.

From CUETools:

[AccurateRip ID: 0006a62a-001ee5fc-40074005] found.
Track   [  CRC   |   V2   ] Status
 01     [573feb63|3c292757] (0+0/9) No match
 02     [8730d9c4|94a2d884] (0+0/9) No match
 03     [fc0fd046|9a95d74b] (0+0/9) No match
 04     [2263d342|9e1e0ceb] (0+0/9) No match
 05     [f7cc1ecc|29e994a6] (0+0/7) No match
Offsetted by 12:
 01     [e7240158] (2/9) Accurately ripped
 02     [9250483a] (2/9) Accurately ripped
 03     [ca4b33a9] (2/9) Accurately ripped
 04     [11e11666] (2/9) Accurately ripped
 05     [89c8c358] (0/7) No match (V2 was not tested)
Offsetted by 18:
 01     [695e1cbf] (0/9) No match (V2 was not tested)
 02     [6ba2ed5b] (0/9) No match (V2 was not tested)
 03     [4e1b2d87] (0/9) No match (V2 was not tested)
 04     [f1132024] (0/9) No match (V2 was not tested)
 05     [5a63158b] (0/7) No match (V2 was not tested)
Offsetted by 1383:
 01     [c579ff5c] (0/9) No match (V2 was not tested)
 02     [e177853b] (0/9) No match (V2 was not tested)
 03     [bad689b6] (0/9) No match (V2 was not tested)
 04     [fd4e57fe] (0/9) No match (V2 was not tested)
 05     [cba67af4] (0/7) No match (V2 was not tested)

Track Peak [ CRC32  ] [W/O NULL]
 --  100,0 [E2F055BA] [78361896]          
 01  100,0 [3AF51C59] [C446B42F]          
 02  100,0 [FD98DED8] [EC9594B7]          
 03  100,0 [1A6EFD42] [788C72F9]          
 04  100,0 [F1BC41F6] [FA91C2E0]          
 05  100,0 [5073D807] [F2BEC577]          

---

From foobar2000 v2.0

Track 1: AccurateRip Verified Confidence 3, Pressing Offset +18 [ARv2 CRC 4C4D751D]
Track 2: AccurateRip Verified Confidence 3, Pressing Offset +18 [ARv2 CRC 79276404]
Track 3: AccurateRip Verified Confidence 3, Pressing Offset +18 [ARv2 CRC EA0B7AE8]
Track 4: AccurateRip Verified Confidence 2, Pressing Offset +12 [ARv2 CRC 8D9F3F83]
Track 5: AccurateRip Verified Confidence 3, Pressing Offset +18 [ARv2 CRC 89688C5E]



Re: CUETools AccurateRip vs foobar2000 v2.0 AccurateRip verification?

Reply #1 –
Look at the fb2k output. It has verified it with offset "+18", and with "ARv2" checksums.
Look at the CUETools output that is "Offsetted by 18:". It says it hasn't checked v2.
The thing is, CUETools doesn't check ARv2 checksums when offset is nonzero.

Test the same CD in CUETools with offset manually corrected to 18. You will get hits.

Re: CUETools AccurateRip vs foobar2000 v2.0 AccurateRip verification?

Reply #2 –
@Porcus replied while I was typing

foobar2000 v2.0 is showing ARv2 results
Tracks 1,2,3, & 5 Confidence 3 at Pressing Offset +18
Track 4 Confidence 2 at Pressing Offset +12
 
CUETools shows ARv1 results only for all Pressing Offsets 
(V2 was not tested) is telling you there may be ARv2 results available.
Offsetted by 12: (same as Pressing Offset +12 but ARv1 only)
 01     [e7240158] (2/9) Accurately ripped
 02     [9250483a] (2/9) Accurately ripped
 03     [ca4b33a9] (2/9) Accurately ripped
 04     [11e11666] (2/9) Accurately ripped
 05     [89c8c358] (0/7) No match (V2 was not tested)
Offsetted by 18: (same as Pressing Offset +18 but ARv1 only)
 01     [695e1cbf] (0/9) No match (V2 was not tested)
 02     [6ba2ed5b] (0/9) No match (V2 was not tested)
 03     [4e1b2d87] (0/9) No match (V2 was not tested)
 04     [f1132024] (0/9) No match (V2 was not tested)
 05     [5a63158b] (0/7) No match (V2 was not tested)

Only the top AccurateRip section of the CUETools log has ARv1 + ARv2 results (which is your RIP 'as is' without applying additional offset)
Track   [  CRC   |   V2   ] Status
 01     [573feb63|3c292757] (0+0/9) No match
 02     [8730d9c4|94a2d884] (0+0/9) No match
 03     [fc0fd046|9a95d74b] (0+0/9) No match
 04     [2263d342|9e1e0ceb] (0+0/9) No match
 05     [f7cc1ecc|29e994a6] (0+0/7) No match
korth

Re: CUETools AccurateRip vs foobar2000 v2.0 AccurateRip verification?

Reply #3 –
Quote from: Porcus on
Test the same CD in CUETools with offset manually corrected to 18. You will get hits.

Quote from: korth on
foobar2000 v2.0 is showing ARv2 results
Tracks 1,2,3, & 5 Confidence 3 at Pressing Offset +18
Track 4 Confidence 2 at Pressing Offset +12
 

Offset manually corrected to 18 and 12 according to foobar2000 AcurrateRip results:

18:

[AccurateRip ID: 0006a62a-001ee5fc-40074005] found.
Track   [  CRC   |   V2   ] Status
 01     [695e1cbf|4c4d751d] (0+3/9) Accurately ripped
 02     [6ba2ed5b|79276404] (0+3/9) Accurately ripped
 03     [4e1b2d87|ea0b7ae8] (0+3/9) Accurately ripped
 04     [f1132024|6cd33dc7] (0+0/9) No match
 05     [5a63158b|89688c5e] (0+3/7) Accurately ripped
Offsetted by -6:
 01     [e7240158] (2/9) Accurately ripped
 02     [9250483a] (2/9) Accurately ripped
 03     [ca4b33a9] (2/9) Accurately ripped
 04     [11e11666] (2/9) Accurately ripped
 05     [89c8c358] (0/7) No match (V2 was not tested)
Offsetted by 1365:
 01     [c579ff5c] (0/9) No match (V2 was not tested)
 02     [e177853b] (0/9) No match (V2 was not tested)
 03     [bad689b6] (0/9) No match (V2 was not tested)
 04     [fd4e57fe] (0/9) No match (V2 was not tested)
 05     [cba67af4] (0/7) No match (V2 was not tested)

Track Peak [ CRC32  ] [W/O NULL]
 --  100,0 [D3E0289D] [78361896]          
 01  100,0 [0504F172] [E95A98B2]          
 02  100,0 [5CF9BD64] [DB48E731]          
 03  100,0 [52578FAA] [A9F1FDB7]          
 04  100,0 [FC91F831] [2627B612]          
 05  100,0 [DED29071] [CC65BDE3]          

---

12:

[AccurateRip ID: 0006a62a-001ee5fc-40074005] found.
Track   [  CRC   |   V2   ] Status
 01     [e7240158|ccf5ac10] (2+2/9) Accurately ripped
 02     [9250483a|9fcea205] (2+2/9) Accurately ripped
 03     [ca4b33a9|67866e83] (2+2/9) Accurately ripped
 04     [11e11666|8d9f3f83] (2+2/9) Accurately ripped
 05     [89c8c358|ba5aedbc] (0+2/7) Accurately ripped
Offsetted by 6:
 01     [695e1cbf] (0/9) No match (V2 was not tested)
 02     [6ba2ed5b] (0/9) No match (V2 was not tested)
 03     [4e1b2d87] (0/9) No match (V2 was not tested)
 04     [f1132024] (0/9) No match (V2 was not tested)
 05     [5a63158b] (0/7) No match (V2 was not tested)
Offsetted by 1371:
 01     [c579ff5c] (0/9) No match (V2 was not tested)
 02     [e177853b] (0/9) No match (V2 was not tested)
 03     [bad689b6] (0/9) No match (V2 was not tested)
 04     [fd4e57fe] (0/9) No match (V2 was not tested)
 05     [cba67af4] (0/7) No match (V2 was not tested)

Track Peak [ CRC32  ] [W/O NULL]
 --  100,0 [D5205663] [78361896]          
 01  100,0 [54831EB5] [DB08FC09]          
 02  100,0 [95CEDC42] [F522D619]          
 03  100,0 [A9309388] [7CBC3958]          
 04  100,0 [C2DFB6F2] [4FDD0FAE]          
 05  100,0 [08AE614C] [6F64BE09]          

---

With offset manually corrected to 12 all tracks are shows as accurate, even those where an offset of 18 was suggested.
Where should i go from here? Should i transcode to apply the offset manually?

Re: CUETools AccurateRip vs foobar2000 v2.0 AccurateRip verification?

Reply #4 –
Depends on your OCD ...
You might have gotten offset wrong when you ripped, or you might have gotten a rarer pressing. In any case, the bits are OK.

Re: CUETools AccurateRip vs foobar2000 v2.0 AccurateRip verification?

Reply #7 –
Offset applied: 12

[AccurateRip ID: 0006a62a-001ee5fc-40074005] found.
Track   [  CRC   |   V2   ] Status
 01     [e7240158|ccf5ac10] (2+2/9) Accurately ripped
 02     [9250483a|9fcea205] (2+2/9) Accurately ripped
 03     [ca4b33a9|67866e83] (2+2/9) Accurately ripped
 04     [11e11666|8d9f3f83] (2+2/9) Accurately ripped
 05     [89c8c358|ba5aedbc] (0+2/7) Accurately ripped
Offsetted by 6:
 01     [695e1cbf] (0/9) No match (V2 was not tested)
 02     [6ba2ed5b] (0/9) No match (V2 was not tested)
 03     [4e1b2d87] (0/9) No match (V2 was not tested)
 04     [f1132024] (0/9) No match (V2 was not tested)
 05     [5a63158b] (0/7) No match (V2 was not tested)
Offsetted by 1371:
 01     [c579ff5c] (0/9) No match (V2 was not tested)
 02     [e177853b] (0/9) No match (V2 was not tested)
 03     [bad689b6] (0/9) No match (V2 was not tested)
 04     [fd4e57fe] (0/9) No match (V2 was not tested)
 05     [cba67af4] (0/7) No match (V2 was not tested)

Track Peak [ CRC32  ] [W/O NULL]
 --  100,0 [D5205663] [78361896]          
 01  100,0 [54831EB5] [DB08FC09]          
 02  100,0 [95CEDC42] [F522D619]          
 03  100,0 [A9309388] [7CBC3958]          
 04  100,0 [C2DFB6F2] [4FDD0FAE]          
 05  100,0 [08AE614C] [6F64BE09]          

---

Track 1: AccurateRip Verified Confidence 3, Pressing Offset +6 [ARv2 CRC 4C4D751D]
Track 2: AccurateRip Verified Confidence 3, Pressing Offset +6 [ARv2 CRC 79276404]
Track 3: AccurateRip Verified Confidence 3, Pressing Offset +6 [ARv2 CRC EA0B7AE8]
Track 4: AccurateRip Verified Confidence 2, Pressing Offset +0 [ARv2 CRC 8D9F3F83]
Track 5: AccurateRip Verified Confidence 3, Pressing Offset +6 [ARv2 CRC 89688C5E]

---

PerfectTUNES doesn't like those results, it says album not present in AccurateRip :S