Skip to main content

Notice

If you are using a Hotmail or Outlook email address, please change it now, as Microsoft is rejecting all email from our service outright.
Topic: CTDB Confidence for CDs with Pregap (Read 733 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CTDB Confidence for CDs with Pregap

When I check the CTDB confidence of CDs with pregaps I get something like:

Code: [Select]
[CUETools log; Date: 13.01.2021 23:29:47; Version: 2.1.6]
[CTDB TOCID: qx19vGe46qZxXtyM2IiEZU3ps2c-] found.
        [ CTDBID ] Status
        [ecf2bc10] (39/86) Has pregap length 00:00:32, No match
        [97a60cd8] (40/86) Has pregap length 00:00:32, Accurately ripped
        [bf3d3e1a] (01/86) Has pregap length 00:00:32, No match
        [1128ca57] (01/86) Has pregap length 00:00:32, No match
        [c450cc11] (01/86) Has pregap length 00:00:32, No match
        [7c8132e8] (01/86) Has pregap length 00:00:32, No match
        [4121101e] (01/86) Has pregap length 00:00:32, No match
        [d434bb74] (01/86) Has pregap length 00:00:32, No match
        [fe782361] (01/86) Has pregap length 00:00:32, No match
Track | CTDB Status
  1   | (86/86) Accurately ripped
  2   | (84/86) Accurately ripped
  3   | (86/86) Accurately ripped
  4   | (86/86) Accurately ripped
  5   | (41/86) Accurately ripped
[AccurateRip ID: 000e4a98-0043e3ca-3f128405] disk not present in database.

Track Peak [ CRC32  ] [W/O NULL]
 --   99,9 [DBBAA7E1] [E68286A2]          
 01   99,9 [584051A7] [90509F25]          
 02   99,9 [76FD06CF] [C6D1E636]          
 03   42,1 [8D87B9C2] [BC904017]          
 04   99,9 [1CCE4ECB] [CD09C764]          
 05   99,9 [8FA12031] [6B78A17F]          

When I check in CUETools under the folder "By CTDB Confidence", this disc is listed under 0 confidence, even though it should have a confidence of 40.

When I manually apply the pregap length 00:00:32, I get:

Code: [Select]
[CUETools log; Date: 13.01.2021 23:26:40; Version: 2.1.6]
Pregap length 00:00:32.
[CTDB TOCID: qx19vGe46qZxXtyM2IiEZU3ps2c-] found.
        [ CTDBID ] Status
        [ecf2bc10] (39/86) No match
        [97a60cd8] (40/86) Accurately ripped
        [bf3d3e1a] (01/86) No match
        [1128ca57] (01/86) No match
        [c450cc11] (01/86) No match
        [7c8132e8] (01/86) No match
        [4121101e] (01/86) No match
        [d434bb74] (01/86) No match
        [fe782361] (01/86) No match
Track | CTDB Status
  1   | (86/86) Accurately ripped
  2   | (84/86) Accurately ripped
  3   | (86/86) Accurately ripped
  4   | (86/86) Accurately ripped
  5   | (41/86) Accurately ripped
[AccurateRip ID: 000e4b58-0043e669-3f128405] found.
Track   [  CRC   |   V2   ] Status
 01     [17047733|55731067] (09+17/57) Accurately ripped
 02     [c17985f5|4d9d540c] (09+16/56) Accurately ripped
 03     [3f2ce7d3|6219f016] (09+16/56) Accurately ripped
 04     [9d9bea9c|a352ac77] (09+16/57) Accurately ripped
 05     [6223bb58|f4df439b] (09+16/54) Accurately ripped
Offsetted by -1331:
 01     [6469bc58] (02/57) Accurately ripped
 02     [ed091aae] (02/56) Accurately ripped
 03     [7f45058b] (02/56) Accurately ripped
 04     [ba7d9a0a] (02/57) Accurately ripped
 05     [d1eb8b6c] (00/54) No match (V2 was not tested)
Offsetted by -667:
 01     [47aa0426] (04/57) Accurately ripped
 02     [598ee98d] (04/56) Accurately ripped
 03     [f2546b76] (04/56) Accurately ripped
 04     [25da7bb2] (04/57) Accurately ripped
 05     [82a4292e] (00/54) No match (V2 was not tested)
Offsetted by -664:
 01     [571fa8c9] (00/57) No match (V2 was not tested)
 02     [22b90a19] (00/56) No match (V2 was not tested)
 03     [a15c2bbe] (00/56) No match (V2 was not tested)
 04     [e22719d3] (00/57) No match (V2 was not tested)
 05     [3cbd6328] (00/54) No match (V2 was not tested)

Track Peak [ CRC32  ] [W/O NULL]
 --   99,9 [F3FF585E] [E68286A2]          
 01   99,9 [584051A7] [90509F25]          
 02   99,9 [76FD06CF] [C6D1E636]          
 03   42,1 [8D87B9C2] [BC904017]          
 04   99,9 [1CCE4ECB] [CD09C764]          
 05   99,9 [8FA12031] [6B78A17F]          

and the CD is correctly listed under the folder named "< 50".

Is this really the intended behaviour? Why the distinction? I find this confusing. I mean the rip is correct and should also without manually applying the pregap be listed under the "< 50" confidence folder.

Re: CTDB Confidence for CDs with Pregap

Reply #1
So you're referring to ranking in the Local DataBase (Local DB)
The only rips in the CTDB (in the example above) all have a pregap length of 00:00:32
In the 1st log the pregap was missing from your rip so there wasn't an exact match (zero exact matches) to any existing CTDBID but there was a pressing match to CTDBID 97a60cd8.
In the 2nd log you applied the 00:00:32 pregap to your rip so there was an exact match to CTDBID 97a60cd8.

CTDB doesn't require the length of the pregap to verify your rip but AccurateRip does. If the rip(s) with a pregap weren't stored under a different CTDBID than the rips without then in the 1st log you wouldn't know why the rip wasn't in the AccurateRip database
Code: [Select]
[AccurateRip ID: 000e4a98-0043e3ca-3f128405] disk not present in database.
or what pregap needed to be applied.

korth

Re: CTDB Confidence for CDs with Pregap

Reply #2
I understand that AccurateRip makes this distinction between pregap or not. But when I verify a CD rip later on (I rip my CDs to individual files per track, so the pregap info is gone), I don't really care about this. I just want to check if my rip is correct and what the confidence is.

BTW: is there a mode to automatically apply the detected pregap in CUETools instead of doing it manually? CUETools figures out, that the most likely pregap is 00:00:32 in this case. So it could automatically apply it when verifying a rip.

So this is maybe more of a feature request then: It would be great to see the confidence independent of pregap in the local database.

Additional idea: show the maximum of the CUETools or AccurateRip confidence, i.e a combined confidence. Everything >=2 should be fine. Then you only have to check the CD rips with combined confidence 0 or 1.

Re: CTDB Confidence for CDs with Pregap

Reply #3
I understand that AccurateRip makes this distinction between pregap or not. But when I verify a CD rip later on (I rip my CDs to individual files per track, so the pregap info is gone), I don't really care about this. I just want to check if my rip is correct and what the confidence is.
AFAIUnderstand, for CUETools to identify the AccurateRip ID, it needs pregap length. If you don't have the file, then an EAC log file or a <CDTOC> tag will suffice to find it - or it can read the ID itself from the tag <ACCURATERIPID>. (Can it use dBpoweramp's <ACCURATERIPDISCID> tag? I don't remember.)

An alternative to verify with AccurateRip is https://www.dbpoweramp.com/perfecttunes.htm . It also tells you the AccurateRip ID it finds in case you want to use CUETools for a later try.
High Voltage socket-nose-avatar

 
SimplePortal 1.0.0 RC1 © 2008-2021