Skip to main content
Topic: Newby needs help in interpreting CUETools output (Read 211 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Newby needs help in interpreting CUETools output

Hi everyone, and apologies if this is a FAQ but I haven't managed to find what I need anywhere.

Can someone point me at documentation or explain how to interpret the following CUETools output when I select 'verify'.  In particular, considering just Track 1, why does CUETools show 337/341 for CTDB and (011+059/282) for the AccurateRip CRC FF2887FE?

The logfile created by EAC (a rip from a few years ago) contained:

AccurateRip summary
 
Code: [Select]
Track  1  accurately ripped (confidence 3)  [FF2887FE]  (AR v2)
Track  2  accurately ripped (confidence 3)  [E326A319]  (AR v2)
Track  3  accurately ripped (confidence 3)  [676D99D1]  (AR v2)
Track  4  accurately ripped (confidence 2)  [B9450F90]  (AR v2)

The CUETools output is:

Code: [Select]
[CUETools log; Date: 20/07/2020 21:24:40; Version: 2.1.6]
[CTDB TOCID: DodWJgs8d89A5O4wX38DdzetrSU-] found.
Track | CTDB Status
  1   | (337/341) Accurately ripped
  2   | (336/341) Accurately ripped
  3   | (333/341) Accurately ripped
  4   | (329/341) Accurately ripped
[AccurateRip ID: 000b4174-002e0303-42108f04] found.
Track   [  CRC   |   V2   ] Status
 01     [d53ef7e8|ff2887fe] (011+059/282) Accurately ripped
 02     [674b14f7|e326a319] (011+060/281) Accurately ripped
 03     [508d8948|676d99d1] (011+057/277) Accurately ripped
 04     [20131bd8|b9450f90] (011+053/270) Accurately ripped
Offsetted by -624:
 01     [a70c42df] (003/282) Accurately ripped
 02     [41897e17] (003/281) Accurately ripped
 03     [426c1db8] (003/277) Accurately ripped
 04     [31a407b8] (003/270) Accurately ripped
Offsetted by -618:
 01     [e1519f91] (002/282) Accurately ripped
 02     [f597a963] (002/281) Accurately ripped
 03     [b153d272] (002/277) Accurately ripped
 04     [3dc78f4c] (002/270) Accurately ripped
Offsetted by 6:
 01     [3895837e] (015/282) Accurately ripped
 02     [1b594043] (015/281) Accurately ripped
 03     [bf753e02] (015/277) Accurately ripped
 04     [2c36a36c] (015/270) Accurately ripped
Offsetted by 30:
 01     [dc813311] (035/282) Accurately ripped
 02     [eb91ed73] (035/281) Accurately ripped
 03     [7b1410ea] (035/277) Accurately ripped
 04     [5cc4c1bc] (035/270) Accurately ripped
Offsetted by 40:
 01     [9748efe7] (025/282) Accurately ripped
 02     [6cfee047] (024/281) Accurately ripped
 03     [de963e20] (023/277) Accurately ripped
 04     [70fff908] (022/270) Accurately ripped
Offsetted by 54:
 01     [9f32ea96] (008/282) Accurately ripped
 02     [bbca9aa3] (008/281) Accurately ripped
 03     [36b2e3d2] (008/277) Accurately ripped
 04     [8d52e00c] (008/270) Accurately ripped
Offsetted by 36:
 01     [d2f11863] (000/282) No match (V2 was not tested)
 02     [9fa018bf] (000/281) No match (V2 was not tested)
 03     [e9fbc5a4] (000/277) No match (V2 was not tested)
 04     [68e84950] (000/270) No match (V2 was not tested)

Track Peak [ CRC32  ] [W/O NULL] [  LOG   ]
 --  100.0 [B9FD2742] [37D98A58]   CRC32  
 01  100.0 [61F91A14] [CBE08BE1]          
 02  100.0 [8523C500] [F87AF817]          
 03  100.0 [02F2F8FC] [0CBF5117]          
 04  100.0 [70230AB2] [8AE7CA3E]     
    

MOD Edit: Add code tags


 

Re: Newby needs help in interpreting CUETools output

Reply #2
Thanks, Korth. Not sure how I missed that :-(

 
SimplePortal 1.0.0 RC1 © 2008-2020