CUETools does not output new encoded files

Topic: CUETools does not output new encoded files (Read 5346 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

CUETools does not output new encoded files

2014-06-20 21:57:54

I want to repair my erroneous CD Rips with CUETools.
So I choosed ENCODE and REPAIR.

Well now sometimes it works and sometimes not.
For some Albums the programme writes new (corrected) files.
In other cases it just stops after the "verification" process ! And no files are created.

Why?

---------------------------------------------------------------------------------------
By the way,
I search for a good manual or guidance for CUETools at best in german language, but can´t find. About all what the programme is able to manage!

I often got problem reports for example: When verifying with accurate rip database: "Cannot locate" the files or such a thing - but the files are there!
----------------------------------------------------------------------------------------

Thanks!

CUETools does not output new encoded files

Reply #1 – 2014-06-21 00:30:13

This can happen when all files already match the recovery record found.
This can also happen because more than one recovery record is available and popup windows are disabled in batch modes.
See Known issues.
In 2.1.4 you must use Folder Browser input mode and must select a single disc (not a folder) to prevent disabling popup windows during repair.
In 2.1.5 you can use any input mode but the selection must contain only one disc for popup windows to work during repair.

CUETools does not output new encoded files

Reply #2 – 2014-06-21 07:35:40

@ korth

1)
I repair files that have no match in the accurate rip database.
How can a rip that is not bit identical with the CD, cos acurate rip db gives back no confidence, match with the CTDB record?
I thought CTDB is similar with acurate rip.
?

--------------------------------------------

2)
In one example there comes a pop up window asking me:
chose the best result:
1) differs in 33 samples, confidence 1
2) verified OK, confidence 1

I choosed the second, then - nothing more happened, CUETools did not write new files.
-------------------
by the way what does that mean - differs in 33 samples. Does one track differ, or the whole rip??
Or is ts this the case you mentioned, where more than one recovery record is availabe, and I can choose between two?

CUETools does not output new encoded files

Reply #3 – 2014-06-21 10:05:07

Quote from: OliP on 2014-06-21 07:35:40

2) verified OK, confidence 1

I choosed the second, then - nothing more happened, CUETools did not write new files.

You told to the program that your rip is OK -- why should it write repaired files if there's nothing to repair?

CUETools does not output new encoded files

Reply #4 – 2014-06-21 14:14:45

OliP,
1) The CUETools Database (CTDB) is an independent database and not part of AccurateRip.
Some reasons why CTDB may have track entries and AccurateRip does not.

The AccurateRip results in the ripping program (like EAC) does not show matches for different pressings. CTDB is free of this problem.
Entries go into the CTDB immediately where discs might take 30 days or more to get entered into the AccurateRip database.
CTDB ignors disc pregap [HTOA]. If you are using CUETools to verify this type of disc without a CUE or EAC log*, this info may be required to properly identify the disc for AccurateRip results.
CTDB stores info about data tracks differently and is not needed for track verification. If you are using CUETools to verify this type of disc without a CUE or EAC log*, this info may be required to properly identify the disc for AccurateRip results.

2) differs in 33 samples means 33 samples are different in this recovery record than the ones on your disc so you can use that recovery record for repair. verified OK (as lvqcl already said) means the recovery record already matches your disc so nothing will be repaired.

confidence 1 There is a known issue and you really shouldn't use confidence 1 recovery records for repair without AccurateRip matches to verify against.

edit: *in addition to the CUE and EAC log, the required info may be stored in the tags.

CUETools does not output new encoded files

Reply #5 – 2014-06-21 16:47:31

Quote from: korth on 2014-06-21 00:30:13

This can happen when all files already match the recovery record found.

CUETools does not output new encoded files

Reply #6 – 2014-06-21 17:07:51

There's a limit to how many samples the recovery record can repair. If you see No Match instead of differs in xx samples it is saying that too many samples differ to do a repair.

CUETools does not output new encoded files

Reply #7 – 2014-06-21 17:40:21

Ok now I got everything.
------------------------------------

One question else:
I heard that CTDB should be used to repair and Accurate Rip to verify.

So when a rip matches with CUETools DB it does not mean that i have a correct, that means bit identical copy of the original CD ?
Only matches with Acurate Rip DB can say that my rip is bit identical, right?

CUETools does not output new encoded files

Reply #8 – 2014-06-21 23:05:17

I'm going to assume your questions refer to verifying repaired rips only.
Once repaired (using a recovery record with a confidence higher than one) the rip should verify using the CTDB to an original CD. It is certainly helpful if you can verify a CTDB repair using AccurateRip to make sure the recovery record used was the correct one to match your original CD. It is possible to have more than one version of a CD stored under the same TOCID.

CUETools does not output new encoded files

Reply #9 – 2014-07-04 00:44:43

Quote from: korth on 2014-06-21 23:05:17

It is possible to have more than one version of a CD stored under the same TOCID.

You mean different pressings with version ?

CUETools does not output new encoded files

Reply #10 – 2014-07-04 04:49:40

One example might be when they normalize a CD on a later release but keep the same TOC structure. These would have too many samples that differ to use a recovery record from one to repair the other. Such as
http://db.cuetools.net/top.php?tocid=ZYX_3CFBpbc1gORqnP6h9aPPlVY-
CTDBID 8712C022 and CTDBID 6BDAE992 are different versions of the same CD title with too many samples that differ.

Ignore the CTDBIDs with confidence 1 (Cf=1).

Another example would be a different pressing with a minor flaw (or difference of several samples introduced between pressings). You can use the recovery record from one version to repair the other. Such as
http://db.cuetools.net/top.php?tocid=KtYa2YHzFiAwwY.OHxFTELYGUpc-
CTDBID C3043318 and CTDBID B167A80B only differ by 6 samples near the middle of Track 1 (excluding pressing offset).

My rip log shows Track 1 is fine but Track 10 has errors.

Code: [Select]

Track  1

     Filename C:\Music\RIPS\FLAC\Bee Gees\[1997] Still Waters\01 Alone.wav

     Pre-gap length  0:00:02.00

     Peak level 98.0 %
     Track quality 100.0 %
     Copy CRC 3D2FBECD
     Accurately ripped (confidence 48)  [9A384003]
     Copy OK
...
Track 10

     Filename C:\Music\RIPS\FLAC\Bee Gees\[1997] Still Waters\10 Obsessions.wav

     Suspicious position 0:00:50 - 0:00:52
     Suspicious position 0:00:57 - 0:01:00
     Suspicious position 0:01:04 - 0:01:08

     Peak level 97.9 %
     Track quality 100.0 %
     Copy CRC 9D2EF47D
     Cannot be verified as accurate (confidence 162)  [A484AC22], AccurateRip returned [62C3853A]
...
Track 12

     Filename C:\Music\RIPS\FLAC\Bee Gees\[1997] Still Waters\12 Smoke And Mirrors.wav

     Peak level 97.9 %
     Track quality 100.0 %
     Copy CRC 64490448
     Accurately ripped (confidence 42)  [B7873B70]
     Copy OK


11 track(s) accurately ripped

Some tracks could not be verified as accurate

There were errors

End of status report

CTDB shows I can repair Track 1 plus Track 10 (2079 samples [6+2073] confidence 58) or just Track 10 by itself (2073 samples confidence 17). The confidence 1 for Track 10 is my rip with errors.

Code: [Select]

Note: this is an older log so the confidence levels won't match the current numbers.

Track | CTDB Status
  1   | (22/84) Accurately ripped, or (58/84) differs in 6 samples @02:48:18
  2   | (83/84) Accurately ripped
  3   | (84/84) Accurately ripped
  4   | (83/84) Accurately ripped
  5   | (83/84) Accurately ripped
  6   | (82/84) Accurately ripped
  7   | (82/84) Accurately ripped
  8   | (82/84) Accurately ripped
  9   | (79/84) Accurately ripped
 10   | ( 1/84) Accurately ripped, or (17/84) differs in 2073 samples
@00:50:58,00:51:65,00:52:06-00:52:07,00:52:22-00:52:23,00:52:39,00:52:55,00:52:72,00:57:57-00:57:58,
00:57:73-00:57:74,00:58:14-00:58:15,00:58:31-00:58:32,00:58:47-00:58:48,00:58:64-00:58:65,
00:59:05-00:59:06,00:59:21-00:59:22,00:59:38-00:59:39,00:59:54-00:59:55,00:59:71-00:59:72,
01:00:12-01:00:13,01:05:47-01:05:48,01:06:05,01:06:21-01:06:22,01:06:70-01:06:71,01:08:03,
or (58/84) differs in 2073 samples
@00:50:58,00:51:65,00:52:06-00:52:07,00:52:22-00:52:23,00:52:39,00:52:55,00:52:72,00:57:57-00:57:58,
00:57:73-00:57:74,00:58:14-00:58:15,00:58:31-00:58:32,00:58:47-00:58:48,00:58:64-00:58:65,
00:59:05-00:59:06,00:59:21-00:59:22,00:59:38-00:59:39,00:59:54-00:59:55,00:59:71-00:59:72,
01:00:12-01:00:13,01:05:47-01:05:48,01:06:05,01:06:21-01:06:22,01:06:70-01:06:71,01:08:03
 11   | (82/84) Accurately ripped
 12   | (82/84) Accurately ripped

During repair, I need to select the recovery record that differs by 2073 samples to repair my rip. If I select the recovery record that differs by 2079 samples, Track 1 of my rip will no longer match AccurateRip for the pressing of my CD.

Notice