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: EAC and CUETools questions (Read 2611 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

EAC and CUETools questions

I used EAC to rip a scratched CD, CUETools to repair it, and have some questions about the information contained in the log files.

One of the ripped tracks had errors. Here is an excerpt from the EAC log file:

Code: [Select]
    Track  3
   
         Filename D:\Music\Agnus Dei\EAC WAV rip\03 - Missa Papae Marcelli- Kyrie.wav
   
         Suspicious position 0:03:49 - 0:04:00
         Suspicious position 0:04:12 - 0:04:15
   
         Peak level 53.7 %
         Extraction speed 0.5 X
         Track quality 95.6 %
         Copy CRC 19B0A8D4
         Cannot be verified as accurate (confidence 86)  [74FB864A], AccurateRip returned [CAB8C6DE]  (AR v2)
         Copy finished
    
Question: does "confidence 86" mean this track has been ripped and reported by 86 other people to the CUETools Database?

The CUETools plugin report section of the EAC log file says the following:

Code: [Select]
    ---- CUETools DB Plugin V2.1.6
   
    [CTDB TOCID: d5HwBKwowk4Nt1TvLjTIVWSUdww-] found
    Submit result: d5HwBKwowk4Nt1TvLjTIVWSUdww- has been submitted
    Track | CTDB Status
      1   | (211/460) Accurately ripped
      2   | (215/460) Accurately ripped
      3   | (182/460) Differs in 14737 samples @03:49:08-03:49:50,03:50:02-03:50:72,03:51:23-03:51:52,03:52:04-04:01:05,04:12:38,04:13:32-04:13:46,04:14:54

Question 1: What are the 2 numbers in the "CTDB Status" column?

Question 2: The CUETools analysis is apparently able to determine that the above ripped track differs from the "reference" by 14737 samples. What is the maximum number of different samples that can be detected? I assume the CTDB doesn't contain *all* samples for a track, as that would simply allow someone to download all samples and create the file without owning an original copy, which would be a copyright violation. Is that correct?


After seeing the EAC report, I was able to repair the incorrect track above using CUETools (instructions taken from tij's post in this thread: https://yabb.jriver.com/interact/index.php?topic=122218.0). When I reviewed that log file, I found the following:

Code: [Select]
    [CUETools log; Date: 5/19/2022 6:40:24 PM; Version: 2.1.6]
    [CTDB TOCID: d5HwBKwowk4Nt1TvLjTIVWSUdww-] found.
    Track | CTDB Status
      1   | (212/461) Accurately ripped
      2   | (216/461) Accurately ripped
      3   | (  1/461) Accurately ripped, or (182/461) differs in 14737 samples @03:49:08,03:49:22-03:49:23,03:49:36,03:49:49-03:49:50,03:50:02,03:50:16,03:50:29-03:50:30,03:50:43-03:50:44,03:50:58,03:50:72,03:51:23,03:51:37-03:51:38,03:51:52,03:52:04,03:52:17-03:52:18,03:52:31-03:52:32,03:52:45,03:52:59,03:52:73,03:53:11-03:53:12,03:53:25-03:53:26,03:53:39-03:53:40,03:53:53,03:53:66-03:53:67,03:54:05-03:54:06,03:54:19-03:54:20,03:54:33-03:54:34,03:54:47,03:54:60-03:54:61,03:54:74-03:55:00,03:55:13-03:55:14,03:55:27-03:55:28,03:55:41-03:55:42,03:55:54-03:55:55,03:55:68-03:55:69,03:56:07-03:56:08,03:56:21-03:56:22,03:56:35-03:56:36,03:56:48-03:56:49,03:56:62-03:56:63,03:57:01-03:57:02,03:57:14-03:57:16,03:57:28-03:57:30,03:57:42-03:57:43,03:57:56-03:57:57,03:57:70-03:57:71,03:58:08-03:58:10,03:58:22-03:58:24,03:58:36-03:58:37,03:58:50-03:58:51,03:58:64-03:58:65,03:59:03-03:59:04,03:59:16-03:59:18,03:59:30-03:59:31,03:59:44-03:59:45,03:59:58-03:59:59,03:59:72-03:59:73,04:00:11-04:00:12,04:00:24-04:00:25,04:00:38,04:00:52-04:00:53,04:00:66-04:00:67,04:01:05,04:12:38,04:13:32,04:13:46,04:14:54

  What do the (  1/461) and (182/461) mean, and why are two sets of numbers reported here whereas EAC only reported one set (182/460)?
 
  Then there is this section of the CUETools log file:

Code: [Select]
  
      [AccurateRip ID: 001cc1f0-010db171-a111040c] found.
    Track   [  CRC   |   V2   ] Status
     01     [b814ac93|8e116edc] (029+086/284) Accurately ripped
     02     [e725059b|b75982e5] (030+087/287) Accurately ripped
     03     [0ff7ab70|74fb864a] (000+000/284) No match
     04     [d51d88df|06ab9363] (029+087/286) Accurately ripped
     05     [38801f06|34f92f34] (030+087/287) Accurately ripped
     06     [c8341b9e|d5327f85] (030+087/285) Accurately ripped
     07     [7c57a53d|96b730e2] (029+086/284) Accurately ripped
     08     [74c2bd1f|156e1f81] (030+087/285) Accurately ripped
     09     [4f8fadf2|7b241bed] (030+086/283) Accurately ripped
     10     [b1a501ed|219bf5c7] (031+085/284) Accurately ripped
     11     [78017f49|12a0f07a] (030+086/285) Accurately ripped
     12     [f225a879|c2c1d336] (030+081/263) Accurately ripped
    Offsetted by -1493:
     01     [8c6ca905] (000/284) No match (V2 was not tested)
     02     [6cf4699a] (000/287) No match (V2 was not tested)
     03     [8a510af6] (000/284) No match (V2 was not tested)
     04     [7ff31864] (000/286) No match (V2 was not tested)
     05     [4e1a8a0d] (000/287) No match (V2 was not tested)
     06     [6b6933d7] (000/285) No match (V2 was not tested)
     07     [294e0b13] (000/284) No match (V2 was not tested)
     08     [9aae344f] (000/285) No match (V2 was not tested)
     09     [de44e7ab] (000/283) No match (V2 was not tested)
     10     [4b0bd34c] (000/284) No match (V2 was not tested)
     11     [f840aa00] (000/285) No match (V2 was not tested)
     12     [8667202b] (000/263) No match (V2 was not tested)
    Offsetted by -900:
     01     [6f40cde5] (008/284) Accurately ripped
     02     [15daa729] (008/287) Accurately ripped
     03     [e5ebbd81] (000/284) No match (V2 was not tested)
     04     [465488d0] (008/286) Accurately ripped
     05     [b4f5a6d8] (008/287) Accurately ripped
     06     [fc741457] (008/285) Accurately ripped
     07     [38b7c9e1] (008/284) Accurately ripped
     08     [50a6bd61] (008/285) Accurately ripped
     09     [e58a244c] (008/283) Accurately ripped
     10     [d3be8321] (008/284) Accurately ripped
     11     [729e3f63] (008/285) Accurately ripped
     12     [1fbe4cc4] (007/263) Accurately ripped
    Offsetted by -829:
     01     [80e97854] (000/284) No match (V2 was not tested)
     02     [7a650fcd] (000/287) No match (V2 was not tested)
     03     [33c0e562] (000/284) No match (V2 was not tested)
     04     [63135e2a] (000/286) No match (V2 was not tested)
     05     [a2133317] (000/287) No match (V2 was not tested)
     06     [2258df01] (000/285) No match (V2 was not tested)
     07     [7c89ff3c] (000/284) No match (V2 was not tested)
     08     [b34440fe] (000/285) No match (V2 was not tested)
     09     [8aa10e4c] (000/283) No match (V2 was not tested)
     10     [e71a1cfb] (000/284) No match (V2 was not tested)
     11     [9670dd85] (000/285) No match (V2 was not tested)
     12     [8f780ce7] (030/263) Accurately ripped
    Offsetted by -823:
     01     [32811b8b] (000/284) No match (V2 was not tested)
     02     [ba44394a] (000/287) No match (V2 was not tested)
     03     [0ce3b406] (000/284) No match (V2 was not tested)
     04     [9b6102a3] (000/286) No match (V2 was not tested)
     05     [ddd2fea8] (000/287) No match (V2 was not tested)
     06     [bddfb022] (000/285) No match (V2 was not tested)
     07     [c92499c1] (000/284) No match (V2 was not tested)
     08     [cbb4dbe2] (000/285) No match (V2 was not tested)
     09     [9acb32a1] (000/283) No match (V2 was not tested)
     10     [79e04b4d] (000/284) No match (V2 was not tested)
     11     [3fea4357] (000/285) No match (V2 was not tested)
     12     [4dcf89c6] (000/263) No match (V2 was not tested)
    Offsetted by -748:
     01     [aa47cb31] (000/284) No match (V2 was not tested)
     02     [06104c53] (000/287) No match (V2 was not tested)
     03     [2d3cbc3f] (000/284) No match (V2 was not tested)
     04     [ad5d4f7a] (000/286) No match (V2 was not tested)
     05     [69588cae] (000/287) No match (V2 was not tested)
     06     [2081b83e] (000/285) No match (V2 was not tested)
     07     [a2b44902] (000/284) No match (V2 was not tested)
     08     [ccc01e7e] (000/285) No match (V2 was not tested)
     09     [1955f1ab] (000/283) No match (V2 was not tested)
     10     [9a33a69a] (000/284) No match (V2 was not tested)
     11     [ae1cbdb5] (000/285) No match (V2 was not tested)
     12     [1767eecf] (000/263) No match (V2 was not tested)
    Offsetted by -268:
     01     [7550697e] (002/284) Accurately ripped
     02     [3ec1af99] (002/287) Accurately ripped
     03     [01fe5e55] (000/284) No match (V2 was not tested)
     04     [63a70998] (002/286) Accurately ripped
     05     [0ca84170] (002/287) Accurately ripped
     06     [75beaedb] (002/285) Accurately ripped
     07     [2a4dc2e4] (002/284) Accurately ripped
     08     [1574cc4f] (002/285) Accurately ripped
     09     [deee3352] (000/283) No match (V2 was not tested)
     10     [f4c0a176] (000/284) No match
     11     [e26faec5] (000/285) No match
     12     [47e423f7] (000/263) No match
    Offsetted by 48:
     01     [4f842db5] (000/284) No match (V2 was not tested)
     02     [27a94059] (000/287) No match (V2 was not tested)
     03     [58965277] (000/284) No match (V2 was not tested)
     04     [f0291370] (000/286) No match (V2 was not tested)
     05     [9dd8e982] (000/287) No match (V2 was not tested)
     06     [3fac2fa2] (000/285) No match (V2 was not tested)
     07     [e81b0b61] (000/284) No match (V2 was not tested)
     08     [679e4e05] (000/285) No match (V2 was not tested)
     09     [1e374aca] (000/283) No match (V2 was not tested)
     10     [9f78d356] (000/284) No match (V2 was not tested)
     11     [a8cd0655] (000/285) No match (V2 was not tested)
     12     [e7d6e296] (000/263) No match
    Offsetted by 320:
     01     [5d84cba0] (000/284) No match
     02     [b6dc5be1] (000/287) No match
     03     [44db3847] (000/284) No match
     04     [b2388478] (000/286) No match
     05     [521c7d86] (000/287) No match
     06     [cb338746] (000/285) No match
     07     [a94365ef] (000/284) No match
     08     [978ee6ea] (000/285) No match
     09     [f5c3b9d7] (000/283) No match
     10     [57cc959c] (002/284) Accurately ripped
     11     [3df40e8a] (002/285) Accurately ripped
     12     [ad29138c] (002/263) Accurately ripped

What exactly is going on here? It looks like CUETools is trying a lot of different offsets to all tracks to see if one particular offset causes all tracks to match the "consensus" found in the CTDB. Is that correct?

Re: EAC and CUETools questions

Reply #1
Question: does "confidence 86" mean this track has been ripped and reported by 86 other people to the CUETools Database?
The AccurateRip database. They are two distinct ones.


Question 1: What are the 2 numbers in the "CTDB Status" column?

You mean, "211/460", "215/460" and the 182/460"? It means it has checked 460 rips, and that
* For the first two tracks, it knows that 211 resp 215 of them match yours. (Why not more? There could be two CDs with the same table-of-contents. For example if two pressings of the same CD were created and dither applied on one of them, making for a technically different signal.)
* For the third: it doesn't know any that matches yours, and it knows that 182 of them "agree that yours is 14737 samples off".

I actually don't know the max number of samples it can fix (IIRC the database makes a larger correction file when the rip is popular, is that right @korth ?). You are absolutely right the correction file is just a correction file, not the entire rip.



  What do the (  1/461) and (182/461) mean, and why are two sets of numbers reported here whereas EAC only reported one set (182/460)?

Probably because the "1/461" is your the 461th rip - which is yours. A faulty one. Sorry ...

If you try to repair it, are you then given the choice between two rips for repair?


   
  Then there is this section of the CUETools log file:
[...]
What exactly is going on here? It looks like CUETools is trying a lot of different offsets to all tracks to see if one particular offset causes all tracks to match the "consensus" found in the CTDB. Is that correct?
Almost. Now wer are at the AccurateRip database again, not the CTDB.
Once upon a time, AccurateRip changed checksum algorithm. CUETools does not do cross-pressing checks for the version 2 checksum.


 

Re: EAC and CUETools questions

Reply #2
I also had to repair my first CD with CUETools a few weeks ago and had similar confusion. As soon as you finish ripping, your results are submitted to CUETools, unlike AccurateRip, which requires you to manually submit your results from the menu. This means that once you rip a CD, all the tracks that you ripped successfully are added to the database, and the confidence increases by one. The next time you try to verify, the confidence numbers will have incremented by one, since your results are now in the database.

As Porcus said, the 1/461 is the bad result for that track you submitted earlier, so it doesn't match anybody else's. The 182/461 means CUETools has matched your rip to a different result that 182 other people got. When CUETools says this, it means you have the option to repair your rip to match the rips of those 182 other people.

Also note that in the EAC window right after you finish a rip, the CUETools information is at the very top, followed by all the AR information. In the actual log file, though, the CUETools information is at the very bottom, instead.

The logs can be kind of confusing if you're repairing a rip. If you want to be sure everything is OK, copy the WAV files to a separate folder with no log files in it and then verify that folder. You should see normal CUETools and AR results if the repair worked. Take notice of the disc TOC in the EAC log, though. If the first track doesn't start at LBA 0, you'll need to manually put the LBA into the "Offset" field in CUETools before you try to verify the rip. If you don't, CUETools may not be able to find the right match for your disc.

Re: EAC and CUETools questions

Reply #3
I actually don't know the max number of samples it can fix (IIRC the database makes a larger correction file when the rip is popular, is that right @korth ?). You are absolutely right the correction file is just a correction file, not the entire rip.
I'm working with information provided by the developer. I too do not have direct knowledge as to exactly how many continuous samples can be repaired. As I understand, the recovery record can only repair blocks of samples (not individual samples) so the actual number would depend on whether or not the damage is continuous of spread out over several locations.
Quote
How many errors can a rip contain and still be repairable?
    That depends. The best case scenario is when there's one continuous damaged area up to 30-40 sectors (about half a second) long for most discs. As of CTDB 2.0, one continuous damaged area up to about 75 sectors (a second) on popular discs.
    The worst case scenario is 4 non-continuous damaged sectors in (very) unlucky positions.
Quote
What information does the database contain per each CD?
[...]
    180KB recovery record (about twice that for more popular CD's), which is stored separately and accessed only when verifying a broken rip or repairing it.

ref: http://cue.tools/wiki/CUETools_Database
http://cue.tools/wiki/CUETools_log
korth

Re: EAC and CUETools questions

Reply #4
(IIRC the database makes a larger correction file when the rip is popular, is that right @korth ?)
A late confirmation that the recovery record is doubled in size for popular CD rips (≈360KB vs the usual ≈180KB)
korth