Hydrogenaudio Forums > [OFF-TOPIC] From: CUETools 1.9.5

Full Version: [OFF-TOPIC] From: CUETools 1.9.5

Hydrogenaudio Forums > Misc. > Recycle Bin

Chinch

Nov 1 2009, 00:12

uh oh... looks like you have a little big of competition gregory.... foorbar just added this to their 'verifier' plugin:

2009-10-05
The File Integrity Verifier component has been updated; it can now verify complete disc rips against the AccurateRip database.

although i wouldn't be too worried... not nearly robust as your program, by far. compare your output:

CODE

X:\TOOL-Lateralus-2001\TOOL - Lateralus - 2001.cue: hdcd detected, rip accurate (201/553).
[Verification date: 10/31/2009 7:05:33 PM]
[Disc ID: 00233e73-0168391d-c612800d]
HDCD: peak extend: none, transient filter: none, gain: -4.0dB..0.0dB
Track     Status
01     (218/592) Accurately ripped, all offset(s) -646(20),-68(3),-66(2),0(193)
02     (550/590) Accurately ripped, all offset(s) -1558(15),-1515(2),-1502(101),-1487(2),-823(165),-646(21),-386(44),-68(3),-66(2),0(195)
03     (216/579) Accurately ripped, all offset(s) -646(20),-68(3),-66(2),0(191)
04     (222/591) Accurately ripped, all offset(s) -646(20),-68(3),-66(2),0(197)
05     (218/592) Accurately ripped, all offset(s) -646(20),-68(3),-66(2),0(193)
06     (220/591) Accurately ripped, all offset(s) -646(22),-68(3),-66(2),0(193)
07     (218/593) Accurately ripped, all offset(s) -646(21),-68(3),-66(2),0(192)
08     (212/580) Accurately ripped, all offset(s) -646(20),-68(3),-66(2),0(187)
09     (219/587) Accurately ripped, all offset(s) -646(21),-68(3),-66(2),0(193)
10     (543/581) Accurately ripped, all offset(s) -1558(15),-1515(2),-1502(101),-1487(2),-823(161),-646(21),-386(45),-68(3),-66(2),0(191)
11     (212/563) Accurately ripped, all offset(s) -646(19),-68(3),-66(2),0(188)
12     (211/559) Accurately ripped, all offset(s) -646(19),-68(3),-66(2),0(187)
13     (201/553) Accurately ripped, all offset(s) -646(21),-68(3),-66(2),0(175)

Track    [ CRC32  ]    [W/O NULL]    [  LOG   ]
--    [AE681285]    [44AED297]      CRC32
01    [73BC6448]    [9B55B762]
02    [8CFDA9DC]    [DE8B00F1]
03    [E589F55D]    [AECD7BD5]
04    [82D96496]    [08E71A13]
05    [6AE4F103]    [578877F8]
06    [D5515381]    [D646A9D0]
07    [7008F39E]    [DE26D8F3]
08    [7BDE32B6]    [83612D37]
09    [485087A9]    [AC589A6B]
10    [9C9945F2]    [79D15D5D]
11    [DE32DE87]    [7AAD792D]
12    [5B50358A]    [435CE20D]
13    [59407D2E]    [0DEAB317]

and then their plugin output:

CODE

Track  Status
01     Accurately ripped, confidence: 193.
02     Accurately ripped, confidence: 195.
03     Accurately ripped, confidence: 191.
04     Accurately ripped, confidence: 197.
05     Accurately ripped, confidence: 193.
06     Accurately ripped, confidence: 193.
07     Accurately ripped, confidence: 192.
08     Accurately ripped, confidence: 187.
09     Accurately ripped, confidence: 193.
10     Accurately ripped, confidence: 191.
11     Accurately ripped, confidence: 188.
12     Accurately ripped, confidence: 187.
13     Accurately ripped, confidence: 175.

and finally, EAC's log output:

CODE

Track  1  accurately ripped (confidence 185)  [44D496F8]
Track  2  accurately ripped (confidence 187)  [0B0B8C08]
Track  3  accurately ripped (confidence 183)  [84D50FDB]
Track  4  accurately ripped (confidence 189)  [3AB04BC4]
Track  5  accurately ripped (confidence 185)  [2BBEDE5B]
Track  6  accurately ripped (confidence 185)  [B1C48A28]
Track  7  accurately ripped (confidence 184)  [81F900BE]
Track  8  accurately ripped (confidence 180)  [5BC2D2C4]
Track  9  accurately ripped (confidence 185)  [EBF1A632]
Track 10  accurately ripped (confidence 183)  [F92D58C5]
Track 11  accurately ripped (confidence 181)  [CED91160]
Track 12  accurately ripped (confidence 181)  [4402D13F]
Track 13  accurately ripped (confidence 169)  [E948BEC9]

All tracks accurately ripped

looks to me like it doesn't check alternate offsets even... it has a few more positive hits than EAC, but that could just possibly be because more people have ripped and added to the DB since then..

doesn't look like a reason to throw away my copy of CUETools -- yet.

Just kidding! I'm just trying to bully you into releasing a new version of CUETools, it has been a while

glebe

Nov 2 2009, 11:34

QUOTE (Chinch @ Nov 1 2009, 00:12)

looks to me like it doesn't check alternate offsets even... it has a few more positive hits than EAC, but that could just possibly be because more people have ripped and added to the DB since then..

No, foobar2000's plugin simply is not as verbose as CUEtools. If the database contains values for zero-offset disc, foo_verifier reports only them. If the database have values only for offsetted versions than foo_verifier reports all non-zero offsets for which rip is accurate. Maybe fb2k's plugin is based on CUEtools code.

for example:

CODE

Track  Status
01     NOT ACCURATE even with offsets: 48(5), 84(4).
02     Accurately ripped with offsets: 48(5), 84(4).
03     NOT ACCURATE even with offsets: 48(5), 84(4).
04     NOT ACCURATE even with offsets: 48(5), 84(4).
05     NOT ACCURATE even with offsets: 48(5), 84(4).
06     NOT ACCURATE even with offsets: 48(5), 84(4).
07     NOT ACCURATE even with offsets: 48(5), 84(4).
08     NOT ACCURATE even with offsets: 48(5), 84(3).
09     NOT ACCURATE even with offsets: 48(5), 84(4).
10     NOT ACCURATE even with offsets: 48(5), 84(4).
11     NOT ACCURATE even with offsets: 48(5), 84(4).
12     NOT ACCURATE even with offsets: 48(5), 84(4).
13     NOT ACCURATE even with offsets: 48(5), 84(4).
14     NOT ACCURATE even with offsets: 48(5), 84(4).
15     NOT ACCURATE even with offsets: 48(5), 84(2).

CODE

Track  Status
01     Accurately ripped, confidence: 7.
02     Accurately ripped, confidence: 6.
03     Accurately ripped, confidence: 7.
04     Accurately ripped, confidence: 7.
05     Accurately ripped, confidence: 7.
06     Accurately ripped, confidence: 7.
07     Accurately ripped, confidence: 6.
08     Accurately ripped, confidence: 6.
09     Accurately ripped, confidence: 6.
10     Accurately ripped, confidence: 7.
11     Accurately ripped, confidence: 7.
12     Accurately ripped, confidence: 7.
13     Accurately ripped, confidence: 7.
14     Accurately ripped, confidence: 7.
15     Accurately ripped, confidence: 7.
16     Accurately ripped, confidence: 7.
17     NOT ACCURATE even with offsets: -750(2), -664(5), 0(7), 238(25), 505(6).
18     NOT ACCURATE even with offsets: -750(2), -664(5), 0(7), 238(27), 505(6).

Chinch

Nov 2 2009, 21:03

QUOTE

now that you mention it, when i found the option for "verbose" listing under foobar's preferences.... the output looked eerily familiar:

CODE

Track    [ CRC    ] Status
   01    [59a4d9d4] (06/08) Accurately ripped as in pressing(s) #1
   02    [321680c1] (06/08) Accurately ripped as in pressing(s) #1
   03    [1ff59d69] (06/08) Accurately ripped as in pressing(s) #1
   04    [b19a05ec] (06/08) Accurately ripped as in pressing(s) #1
   05    [d99e76e7] (06/08) Accurately ripped as in pressing(s) #1
   06    [43a99553] (06/08) Accurately ripped as in pressing(s) #1
   07    [5b3c0242] (06/08) Accurately ripped as in pressing(s) #1
   08    [c03e9291] (06/08) Accurately ripped as in pressing(s) #1
   09    [99a42171] (06/08) Accurately ripped as in pressing(s) #1
   10    [044968bb] (06/08) Accurately ripped as in pressing(s) #1
   11    [59592ac2] (06/08) Accurately ripped as in pressing(s) #1
   12    [19c671e3] (05/07) Accurately ripped as in pressing(s) #1
  Offseted by 550:
   01    [59f9f9b0] (02/08) Accurately ripped as in pressing(s) #2
   02    [6c1eb5c6] (02/08) Accurately ripped as in pressing(s) #2
   03    [92a84c60] (02/08) Accurately ripped as in pressing(s) #2
   04    [287cbbe4] (02/08) Accurately ripped as in pressing(s) #2
   05    [487e1f7b] (02/08) Accurately ripped as in pressing(s) #2
   06    [e5abb186] (02/08) Accurately ripped as in pressing(s) #2
   07    [8133187a] (02/08) Accurately ripped as in pressing(s) #2
   08    [224044da] (02/08) Accurately ripped as in pressing(s) #2
   09    [8eb6a74b] (02/08) Accurately ripped as in pressing(s) #2
   10    [78e1d0dd] (02/08) Accurately ripped as in pressing(s) #2
   11    [1d18095a] (02/08) Accurately ripped as in pressing(s) #2
   12    [92d952d9] (02/07) Accurately ripped as in pressing(s) #2

  Track    [ CRC32  ]    [W/O NULL]
   01    [26881466]    [D922090F]
   02    [5F47C81D]    [6218239F]
   03    [9D8F2543]    [42C786CB]
   04    [694705E5]    [686D8204]
   05    [C0649823]    [9274F842]
   06    [2E6EFD42]    [1D5BF99B]
   07    [BE0C99A1]    [1C3A7EBD]
   08    [A01BEB93]    [426A15B8]
   09    [D30F0150]    [29EEE371]
   10    [18AD46B6]    [D5987613]
   11    [A3EA76AD]    [2803B754]
   12    [443086C8]    [A51BC2D4]

ever seen that before? seems i have, somewhere...............

oh wait. wasn't that the exact format a couple of versions ago of CUETools? (output below is of current version)

CODE

[Verification date: 11/2/2009 3:05:41 PM]
[Disc ID: 0010d704-009b1ca5-b0086b0c]
Track    [ CRC    ] Status
01    [59a4d9d4] (06/08) Accurately ripped
02    [321680c1] (06/08) Accurately ripped
03    [1ff59d69] (06/08) Accurately ripped
04    [b19a05ec] (06/08) Accurately ripped
05    [d99e76e7] (06/08) Accurately ripped
06    [43a99553] (06/08) Accurately ripped
07    [5b3c0242] (06/08) Accurately ripped
08    [c03e9291] (06/08) Accurately ripped
09    [99a42171] (06/08) Accurately ripped
10    [044968bb] (06/08) Accurately ripped
11    [59592ac2] (06/08) Accurately ripped
12    [19c671e3] (05/07) Accurately ripped
Offsetted by 550:
01    [59f9f9b0] (02/08) Accurately ripped
02    [6c1eb5c6] (02/08) Accurately ripped
03    [92a84c60] (02/08) Accurately ripped
04    [287cbbe4] (02/08) Accurately ripped
05    [487e1f7b] (02/08) Accurately ripped
06    [e5abb186] (02/08) Accurately ripped
07    [8133187a] (02/08) Accurately ripped
08    [224044da] (02/08) Accurately ripped
09    [8eb6a74b] (02/08) Accurately ripped
10    [78e1d0dd] (02/08) Accurately ripped
11    [1d18095a] (02/08) Accurately ripped
12    [92d952d9] (02/07) Accurately ripped

Track    [ CRC32  ]    [W/O NULL]    [  LOG   ]
--    [DEF8A07C]    [1EA6A421]      CRC32
01    [26881466]    [D922090F]
02    [5F47C81D]    [6218239F]
03    [9D8F2543]    [42C786CB]
04    [694705E5]    [686D8204]
05    [C0649823]    [9274F842]
06    [2E6EFD42]    [1D5BF99B]
07    [BE0C99A1]    [1C3A7EBD]
08    [A01BEB93]    [426A15B8]
09    [D30F0150]    [29EEE371]
10    [18AD46B6]    [D5987613]
11    [A3EA76AD]    [2803B754]

i'm not outright accusing them of ripping code... but if they did use CUETools code (which is available to the public).... come on. Credit is due for peoples' hard work and dedication.

I love both programs and respect both authors very much, and do not want to see this feature removed from foobar's verifier plugin, but I just think that is a little fishy looking to me. There may have been modifications to the code, as the output that glebe has posted, as far as non-accurate results... or the author may have made it purposely have the same output as CUETools for the sake of a standard or universality, so that it could be used with CUETools..

I just have to question, is all...

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.