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: Verifying Audio with AccurateRip using CueTools (Read 5224 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Verifying Audio with AccurateRip using CueTools

I have recently downloaded latest version of CueTools 2.1.4 to verify some audio files in FLAC format and to check if their data is intact and in good condition. Upon verifying I received a following log:

Quote
[CUETools log; Date: 1/26/2013 3:44:03 AM; Version: 2.1.4]
[CTDB TOCID: CIRFx5dQ.4N9WDS8jx8WeIEidT8-] disk not present in database.
[AccurateRip ID: 0069c39c-02de274b-c712a80f] found.
Track  [  CRC  |  V2  ] Status
01    [e5a69173|048c8131] (0+0/1) No match
02    [d2428b19|252830d0] (0+0/1) No match
03    [92af99ba|339849be] (0+0/1) No match
04    [4887b5f2|cdcf2da8] (0+0/1) No match
05    [97abdd08|e3d7c2c] (0+0/1) No match
06    [22f3b392|d1bbabc7] (0+0/1) No match
07    [905affcv|08f9b5c4] (0+0/1) No match
08    [fd873178|a5df52fc] (0+0/1) No match
09    [00206fnc|5179ebf4] (0+0/1) No match
10    [56bf0841|fd334179] (0+0/1) No match
11    [fgae2e95|0fb37336] (0+0/1) No match
12    [3345734c|2na4ca0a] (0+0/1) No match
13    [be263042|b62fd35c] (0+0/1) No match
14    [96dacce7|b8d367a2] (0+0/1) No match
15    [343db529|a2b2dd20] (0+0/1) No match
Offsetted by 6:
01    [9f50896b] (1/1) Accurately ripped
02    [cc61bbfb] (1/1) Accurately ripped
03    [1d70d340] (1/1) Accurately ripped
04    [6f18326d] (1/1) Accurately ripped
05    [142dbfb6] (1/1) Accurately ripped
06    [98a66f99] (1/1) Accurately ripped
07    [2b1d62cb] (1/1) Accurately ripped
08    [f8e2d9c3] (1/1) Accurately ripped
09    [c4a8738a] (1/1) Accurately ripped
10    [f243f12b] (1/1) Accurately ripped
11    [8f4e3b39] (1/1) Accurately ripped
12    [26d99438] (1/1) Accurately ripped
13    [b7502f51] (1/1) Accurately ripped
14    [213463a1] (1/1) Accurately ripped
15    [8733fd85] (1/1) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL] [  LOG  ]
--  100.0 [712AEFC8] [7984AD5B]         
01  99.7 [97D8BA32] [E9FAD642]  CRC32 
02  99.7 [11643008] [4CCB1273]  CRC32 
03  99.7 [35FFA1B8] [4EA83A91]  CRC32 
04  100.0 [5DF9028A] [754C6D86]  CRC32 
05  99.5 [B3CE5218] [AB312A47]  CRC32 
06  99.7 [528EF9EB] [8E130CCA]  CRC32 
07  99.7 [0CBACCF9] [D0ABE978]  CRC32 
08  99.7 [2CCF3612] [79421C26]  CRC32 
09  100.0 [84C1214C] [0ACE65A9]  CRC32 
10  99.7 [2F03884C] [A2AA1CA0]  CRC32 
11  99.7 [F1D626C4] [889F1C17]  CRC32 
12  100.0 [C69E8617] [102120AE]  CRC32 
13  100.0 [EE8766FF] [F76D9B09]  CRC32 
14  99.7 [9DE1BB02] [C51F844B]  CRC32 
15  99.7 [814D8958] [49D220E5]  CRC32


I have a few questions:

What's the difference between ARv1 and ARv2?
Do I have my Rip in "No match" which is ARv2 or in "Accurately ripped" section below? If my rip didn't match then what does the "AccurateRip ID" signify?

Verifying Audio with AccurateRip using CueTools

Reply #1
Your rip matched one database entry out of one ARv1 database entries but at an offset of 6 samples. There were no ARv2 entries. More info about reading the log here.
AccurateRip (Hydrogenaudio wiki page)
korth

Verifying Audio with AccurateRip using CueTools

Reply #2
Your rip matched one database entry out of one ARv1 database entries but at an offset of 6 samples. There were no ARv2 entries. More info about reading the log here.
AccurateRip (Hydrogenaudio wiki page)


Does it mean if I remove 6 samples from the start, it would match the one entry in ARv1 database? I have gone through the link at the end but I don't quite understand the purpose of ARv2 and pressings. Could you please make it little more clear why was ARv2 created?

Verifying Audio with AccurateRip using CueTools

Reply #3
Your rip (all tracks) matches the only public entry in the database. Offset correction is not necessary but it would be +6 in CUETools.
spoon contributed to the 'Pressings' section of that wiki page and also developed ARv2. In post #7 of this thread, spoon describes pressings. Also elsewhere in that thread and the one at the dbpoweramp forum discuss the development of ARv2.
korth