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: Cuetools report, not quite clear (Read 191 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Cuetools report, not quite clear

Hello, verifying one of my rip i got sth like below:
 (1769/1976) Differs in 1 samples @03:31:05, or (26/1976) differs in 1 samples @03:31:05, or (7/1976) differs in 1 samples @03:31:05

There is no Accurately ripped mention anywhere like here:
(825/838) Accurately ripped, or (4/838) differs in 179 samples @03:03:03

What does it mean? 1976 persons ripped it and no rip is treated as accurate?

And second thing CueTools says in CTDB status that my rip is accurate but then below there is
[AccurateRip ID: xyz] found.
Track   [  CRC   |   V2   ] Status
 01     [96b94955|96bdef3c] (0+3/3) Accurately ripped
or there is
[AccurateRip ID: xyz] found.
Track   [  CRC   |   V2   ] Status
 01     [a7602396|6299a2b9] (0+0/5) No match

If rip is accurate why there is no match here?

 

Re: Cuetools report, not quite clear

Reply #1
see first http://cue.tools/wiki/CUETools_log

(1769/1976) Differs in 1 samples @03:31:05, or (26/1976) differs in 1 samples @03:31:05, or (7/1976) differs in 1 samples @03:31:05
[...]
What does it mean? 1976 persons ripped it and no rip is treated as accurate?
One record (CTDBID) contains 1769 rips that match each other (out of 1976 total under the TOCID) but do not match your rip by 1 sample. Another record (CTDBID) contains 26 rips that match each other (out of 1976 total for the TOCID) but do not match your rip by 1 sample. And another record (CTDBID) contains 7 rips that match each other (out of 1976 total for the TOCID) but do not match your rip by 1 sample.
Your rip doesn't completely match anything listed. (off by 1 sample)

Quote
And second thing CueTools says in CTDB status that my rip is accurate but then below there is
[AccurateRip ID: xyz] found.
Track   [  CRC   |   V2   ] Status
 01     [96b94955|96bdef3c] (0+3/3) Accurately ripped
or there is
[AccurateRip ID: xyz] found.
Track   [  CRC   |   V2   ] Status
 01     [a7602396|6299a2b9] (0+0/5) No match

If rip is accurate why there is no match here?

The first example is Accurate with 3/3 ARv2 matches (0/3 ARv1 matches but there were only 3 rips total)
The second example shows not Accurate for that pressing. There may be matches below this section for alternate pressing offsets or the rip may not exist (yet) in the AccurateRip DB.
AccurateRip stores hashes separately for each pressing where CTDB stores all pressings (within range) under the same CTDBID.

http://www.accuraterip.com/
http://cue.tools/wiki/CUETools_Database
korth

 
SimplePortal 1.0.0 RC1 © 2008-2021