CUETools log

From CUETools wiki
Jump to: navigation, search

This page shows an example of the CUETools Verification Log (verbose) along with some tips on how to read it.

CUETools and CUERipper save this log as a file with the default name format: %filename%.accurip (but this name format can be changed if you want).

Contents

CUETools Log Header

Simple one-line header showing:

Title; Date/Time; Version

[CUETools log; Date: 4/11/2012 10:48:23 AM; Version: 2.1.4]

Special Messages Section

CD-Extra data track length xx:xx:xx
Data track detected or manually applied Data track correction in CUETools
Pregap length xx:xx:xx
Pregap detected or manually applied Pregap correction in CUETools
CUETools DB: corrected xx errors
repair script used
HDCD: peak extend: xx, transient filter: xx, gain: xx
HDCD encoding detected (Detection can be disabled)
Offset applied: xx
fix offset script used or manually applied Offset correction in CUETools
Truncated 4608 extra samples in some input files
Extra 4608 zero samples at end of file(s) detected and removed (Detection can be disabled)
Using preserved id, actual id is xxxxxxxx-xxxxxxxx-xxxxxxxx
Preserved ACCURATERIPID in cue does not match actual calculated AccurateRip ID of file(s), preserved ID used
CDDBId mismatch: xxxxxxxx vs xxxxxxxx
Preserved DISCID in cue does not match actual calculated CDDBId of file(s)
Padded some input files to a frame boundary
File(s) truncated and do not align on a frame (sector) boundary, zeroes padded to next frame (sector) boundary

CTDB (CUETools Database) Section

CTDB TOCID
Identifier based on the CD's TOC (table of contents)
found.
The database has at least one record for a pressing of this CD. Comparison info may follow.
disk not present in database.
The database has no records for any pressings of this CD. No comparison info will follow.
[CTDB TOCID: jwbCIS8AlSqzES7CrVwQ.1bfhoQ-] found.

Comparison of this rip (whole disc) to CTDB records

As of 2.1.4, requires CTDB: Detailed log = True.

CTDBID
Modified CRC32 of all tracks combined (CDImage)
Status
(X/Y)
X = Number of database records under CTDBID
Y = Total database records under CTDB TOCID
Accurately ripped
Your rip matches database records under CTDBID
Differs in ...
Partial match under CTDBID, might be repairable
CD-Extra data track length xx:xx:xx,
CTDBID includes a data track (length as shown)
Has no data track,
Your disc includes a data track, this CTDBID doesn't
Has pregap length xx:xx:xx,
CTDBID includes a pregap (length as shown)
No match
Too many samples differ
        [ CTDBID ] Status
        [2780a681] (68/76) Accurately ripped
        [8eb13402] (01/76) Differs in 78 samples @48:10:50,50:31:02
        [e9bcfc58] (01/76) No match
        [295eb06b] (01/76) No match
        [7af752c1] (01/76) Differs in 4879 samples @65:36:73-65:36:74,
65:40:48-65:40:49,65:40:69-65:40:70,65:45:32-65:45:33,65:48:60-65:48:61,
65:49:06-65:49:07,65:49:70-65:49:71,65:51:25-65:51:27,65:51:47-65:51:48,
65:53:02-65:53:03,65:54:12-65:54:13,65:56:10-65:56:11,65:57:62-65:57:63,
65:58:08,65:59:39-65:59:40,65:59:60-65:59:61,66:01:16-66:01:17,
66:01:37-66:01:38,66:02:46-66:02:48,66:04:02-66:04:03,66:05:12-66:05:13,
66:05:54-66:05:55,66:06:00-66:06:01,66:06:43-66:06:44,66:06:64-66:06:65,
66:07:31-66:07:32,66:07:52-66:07:54,66:07:74-66:08:00
        [6cd3669e] (01/76) No match
        [d5a2b98e] (01/76) No match
        [0df356ef] (01/76) No match
        [4f7d5a04] (01/76) No match

Comparison of this rip (individual tracks) to CTDB records

TrackNEW in 2.1.4
Gives the status of the individual tracks
CTDB Status
(X/Y)
X = Number of matching DB records all CTDBID's
Y = Total database records under CTDB TOCID
Accurately ripped
Your rip matches database records for this track
Differs in ...
Partial match this track, might be repairable
No match
Too many samples differ
Track | CTDB Status
  1   | (75/76) Accurately ripped
  2   | (76/76) Accurately ripped
  3   | (75/76) Accurately ripped
  4   | (74/76) Accurately ripped
  5   | (75/76) Accurately ripped
  6   | (75/76) Accurately ripped
  7   | (74/76) Accurately ripped
  8   | (75/76) Accurately ripped
  9   | (74/76) Accurately ripped, or (1/76) differs in 78 samples 
@01:41:24,04:01:51
 10   | (74/76) Accurately ripped
 11   | (71/76) Accurately ripped, or (1/76) differs in 4879 samples 
@07:43:59-07:43:60,
07:47:34-07:47:35,07:47:55-07:47:56,07:52:18-07:52:19,07:55:46-07:55:47,
07:55:67-07:55:68,07:56:56-07:56:57,07:58:11-07:58:13,07:58:33-07:58:34,
07:59:63-07:59:64,08:00:73-08:00:74,08:02:71-08:02:72,08:04:48-08:04:49,
08:04:69,08:06:25-08:06:26,08:06:46-08:06:47,08:08:02-08:08:03,
08:08:23-08:08:24,08:09:32-08:09:34,08:10:63-08:10:64,08:11:73-08:11:74,
08:12:40-08:12:41,08:12:61-08:12:62,08:13:29-08:13:30,08:13:50-08:13:51,
08:14:17-08:14:18,08:14:38-08:14:40,08:14:60-08:14:61

AccurateRip Section

AccurateRip ID
Identifier based on the CD's TOC (table of contents)
Track
Gives the status of the individual tracks only
CRC
AccurateRip's Modified ARv1 CRC
V2
AccurateRip's Modified ARv2 CRC
Status
(V1+V2/Y)NEW in 2.1.4 or (V1/Y)
V1 = Number of matching ARv1 database records
V2 = Number of matching ARv2 database records
Y = Total database records under AccurateRip ID

Note: The first set of tracks listed are for this disc at zero offset ('zero' after any read offset correction was applied). Alternate database records listed below this set show 'Offsetted by xxx' that indicates the offset difference from the current 'zero' offset of this disc.


Accurately ripped
Your rip matches database records for this track
No match
No CRC match
No match (V2 was not tested)NEW in 2.1.4
Track starts at correct position (for that offset) but CRC doesn't match, possible ARv2 CRC matches
Offsetted by xxx
ARv1 database records found under alternate offsets
Likely different pressings of the same disc

(ARv2 is only tested at zero offset)


From versions prior to 2.1.4

AccurateRip v2:

(V2/Y)
V2 = Number of matching ARv2 database records
Y = Total database records under AccurateRip ID
No match but offset
Short for No match, but offset probably correct. Similar to No match (V2 was not tested)

[AccurateRip ID: 001a2e35-00e484f6-7d0f930b] found.
Track   [  CRC   |   V2   ] Status
 01     [f95b16c0|d0f748ba] (10+02/34) Accurately ripped
 02     [5eef1118|0f0c8580] (10+02/34) Accurately ripped
 03     [00248574|0d99e791] (10+02/34) Accurately ripped
 04     [cc9e24e7|f4dc29dc] (10+02/34) Accurately ripped
 05     [e6fd9130|438257a5] (09+02/33) Accurately ripped
 06     [34202e80|43b6221d] (09+02/33) Accurately ripped
 07     [571937a8|84c14501] (10+02/34) Accurately ripped
 08     [508b17f8|ad9290ab] (10+02/34) Accurately ripped
 09     [b6f6b44c|53e873f4] (10+02/34) Accurately ripped
 10     [3d895f9c|10884fde] (10+02/34) Accurately ripped
 11     [b2e61af3|641b0eb8] (10+02/34) Accurately ripped
Offsetted by 640:
 01     [c32a7a37] (12/34) Accurately ripped
 02     [bdce2b36] (12/34) Accurately ripped
 03     [2ebbecba] (12/34) Accurately ripped
 04     [f6e6189e] (12/34) Accurately ripped
 05     [e4ad72e7] (12/33) Accurately ripped
 06     [e2f3af13] (12/33) Accurately ripped
 07     [0f1a708f] (12/34) Accurately ripped
 08     [340ffd6a] (12/34) Accurately ripped
 09     [8d44eb63] (12/34) Accurately ripped
 10     [0c933dc7] (12/34) Accurately ripped
 11     [b3f51a58] (12/34) Accurately ripped

EAC-Style Info Section

Track
-- all tracks combined (CDImage)
Peak
Same as Peak level found in the EAC log
CRC32
Null samples used in CRC calculations
W/O NULL
Null samples NOT used in CRC calculations

(Peak, CRC32, & W/O NULL column values are generated by CUETools)


(The LOG column is added when CUETools finds an EAC log in the same folder as the files, then the EAC log Copy CRC values are compared to values generated by CUETools)

LOG

CRC32
EAC log Copy CRC matches CRC under CRC32
W/O NULL
EAC log Copy CRC matches CRC under
W/O NULL
CRC32 (or W/O NULL) for track xx
EAC log Copy CRC matches CRC under CRC32 (or W/O NULL) for a different track. This is usually caused by tracks somehow getting mixed up, or a strange log - for example, when there are several logs appended, CUETools can fail to determine which CRC is related to which track.
CRC32 (or W/O NULL) : offset xxx
EAC log Copy CRC would match CRC under CRC32 (or W/O NULL) with offset xxx. This can happen if you apply offset correction to the files after the rip was made.
[xxxxxxxx]
EAC log Copy CRC is displayed if it neither matches the CRC under CRC32 nor the one under W/O NULL.

Track Peak [ CRC32  ] [W/O NULL] [  LOG   ]
 --   86.8 [B7D6DB3D] [51BF2520]           
 01   68.7 [9C655D54] [8A9D382B]   CRC32   
 02   85.6 [DBF7A2CF] [227E3BE7]   CRC32   
 03   86.2 [D2B21899] [76DAD014]   CRC32   
 04   82.3 [47FF5BCA] [262076AD]   CRC32   
 05   84.3 [AE0321E6] [BBDBFDD2]   CRC32   
 06   70.6 [BEF07E47] [68A2BCB6]   CRC32   
 07   86.7 [F9345AAD] [D49AE1A9]   CRC32   
 08   86.1 [1A8CADB1] [57E25460]   CRC32   
 09   86.8 [3B582663] [49599556]   CRC32   
 10   84.2 [16013D49] [00FA7C28]   CRC32   
 11   86.1 [805C163D] [DAD7B768]   CRC32
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox