CUETools versions 1.9.5 through 2.1.4 (current), AccurateRip support & more Options

[korth]

I chose the cue for input, "encode and verify", "lossless" and so on, and a output directory (different from input dir).

Sounds like an older version.

But when I click on go I instantly get an exception, that the access to the directory is denied (Windows 7 x64).

I'm still using XP but I know Windows 7 has very strict access rights inside the "Program Files" directories. If you are running CUETools from there, you might try running from something like C:\CUETools instead.

[sts78]

Don't remember the exact version (currently not sitting in front of the concerning machine), but the current installation is from a build I downloaded just two to three weeks ago from the official site.
Well, I mistyped the set options I made (tried it from memory). It's actually "encode", "tracks", "losless"...
I installed it outside the program files directory, actually on another drive.

[philaphonic]

I need some advice. Perhaps this question relates more to AccurateRip than CUETools, but here goes...

I verified a Frank Zappa CD this morning with CUETools 2.12a that came up with the following verification results:

C:\...\Hot Rats flac.cue: AR: rip accurate (231/260), CTDB: verified OK, confidence 209, or differs in 170 samples, confidence 1.

I am inclined to think this is a good rip, matching 231 samples of 260 using the AccurateRip database. However, the CTDB "differs in 170 samples" has me thinking my CD rip may have defects.

Is this a good rip of "Hot Rats"?

Thank you.

[korth]

I am inclined to think this is a good rip, matching 231 samples of 260 using the AccurateRip database

Not samples, database entries.

However, the CTDB "differs in 170 samples" has me thinking my CD rip may have defects.
Is this a good rip of "Hot Rats"?

Yes
CTDB: says
verified OK, confidence 209
or
differs in 170 samples, confidence 1

You match 209/210, that's good.

This post has been edited by korth: Nov 5 2011, 18:30

[philaphonic]

You match 209/210, that's good.

Thanks for educating me, Korth!

[philaphonic]

Hello, all.

I have a .CUE and an associated .APE image for an album and need to convert them into separate tracks. What is the best way to this with the most recent version of CUETools and still retain the correct offsets and AccurateRIP data that CUETools says are proper? I do know there is one HTOA.

Thank you.

[Tigerman]

@Gregory

In post #1321 I had some trouble with fixing a bad rip because CTDB had 2 entries and I didn't get the pop-up for choosing which one CT should use. In post #1525 Korth has the same problem.
You mentioned you would look into it. Any news on that?

P.S. I'm using also win7 64bit.

[korth]

I have a .CUE and an associated .APE image for an album and need to convert them into separate tracks. What is the best way to this with the most recent version of CUETools and still retain the correct offsets and AccurateRIP data that CUETools says are proper? I do know there is one HTOA.

Advanced Settings-CUETools-Gaps Handling: Gaps Appended + HTOA
Input mode shouldn't matter. I use Multiselect Browser and select the cue file.
(main window)
Action: Encode (default)
Mode: Tracks
Audio Output: Lossless (you can convert or keep APE)
Extra:
Pregap: 00:00:00
Data Track: 00:00:00
Offset: 0
Verify your output to check for changes. Unless this disc is an exception, there shouldn't be any.

[philaphonic]

I have a .CUE and an associated .APE image for an album and need to convert them into separate tracks. What is the best way to this with the most recent version of CUETools and still retain the correct offsets and AccurateRIP data that CUETools says are proper? I do know there is one HTOA.

Advanced Settings-CUETools-Gaps Handling: Gaps Appended + HTOA
Input mode shouldn't matter. I use Multiselect Browser and select the cue file.
(main window)
Action: Encode (default)
Mode: Tracks
Audio Output: Lossless (you can convert or keep APE)
Extra:
Pregap: 00:00:00
Data Track: 00:00:00
Offset: 0
Verify your output to check for changes. Unless this disc is an exception, there shouldn't be any.

Thanks, korth. I figured this all out tonight... The pregaps were giving me problems matching AccurateRip but once I added those back into to my makeshift .CUEs, everything is matching up and working well.

[Gregory S. Chudo...]

You mentioned you would look into it. Any news on that?

Unfortunately, i was not able to reproduce it... Works for me using the same disc.

If this happens again, please provide more details - a copy of your settings etc.

I'm currently working on an update to CTDB. One of the things i wanted to address is the readability of the log.
How about replacing this:

CODE

        [ CTDBID ] Status
        [fbead10c] (05/10) Differs in 104 samples @00:00:21
        [93e09601] (02/10) Accurately ripped
        [0697adde] (02/10) No match
        [f101c3d3] (01/10) No match

with this:

CODE

Track  | CTDB Status
   1   | ( 2/10) Accurately ripped, or (5/10) differs in 104 samples @00:00:21
   2   | ( 9/10) Accurately ripped
   3   | (10/10) Accurately ripped
   4   | (10/10) Accurately ripped
   5   | (10/10) Accurately ripped
   6   | ( 8/10) Accurately ripped
   7   | ( 8/10) Accurately ripped
   8   | (10/10) Accurately ripped
   9   | (10/10) Accurately ripped
  10   | (10/10) Accurately ripped
  11   | (10/10) Accurately ripped
  12   | (10/10) Accurately ripped
  13   | (10/10) Accurately ripped

The new format doesn't contain the detailed entry-per-entry analysis, but should be easier to read when there are many entries.
What do you think, should there be an option to keep the old format or to display both?

Also, wanted to let you know that now there's a Google+ page for CUETools, where i will try to post news etc, but no promises. So now you can follow CUETools on Google+, and type +CUETools to mention it in your posts.

[sauvage78]

Personnaly, as long as CTDB is not meant to be a verification database, I prefer the old way. I like seeing the CTDBID.
If readability is the issue, I think the new look is confusing as it is too close to the AR displaying.

I think I also had the Tigerman/Korth problem. I'll post if I encounter it again.

This post has been edited by sauvage78: Nov 10 2011, 15:20

[korth]

Unfortunately, i was not able to reproduce it... Works for me using the same disc.
If this happens again, please provide more details - a copy of your settings etc.

I assume this popup comes after the verify stage. If I try to repair a disc like the example given, the operation just stops after the verify. It will only repair if there is one (and only one) database entry.
Note: I also do not have 'hover' text in the right center of the GUI which includes Action, Mode, Audio Output, and Extra. If there's supposed to be 'hover' text anywhere in there, I don't have it.
I'll PM a copy of my 'settings.txt'

I'm currently working on an update to CTDB. One of the things i wanted to address is the readability of the log.

I'm fine with the old way.

This post has been edited by korth: Nov 10 2011, 15:53

[sauvage78]

Another issue I encountered, when checking an ECD without a log, applying automatically the datatrack length from CTDB doesn't always work if there is several possibilities.

Exemple:

CODE

[CUETools log; Date: 26/10/11 08:21:54; Version: 2.1.2a]
CD-Extra data track length 00:55:03.
Using preserved id, actual id is 001f1774-010de601-bb12690c.
[CTDB TOCID: 3cZV0hFEMfSJ5v5.YmEtrkFlT8c-] found.
[ CTDBID ] Status
[91454d22] (021/602) Has no data track, No match
[72fa996c] (039/602) Has no data track, Accurately ripped
[a049b78f] (003/602) Accurately ripped
[61e8ba89] (003/602) CD-Extra data track length 01:50:54, No match
[bef8a9b2] (246/602) CD-Extra data track length 02:08:32, Accurately ripped
[72fa996c] (290/602) CD-Extra data track length 02:12:34, Accurately ripped
[AccurateRip ID: 001f2e22-010ef629-bb12b60c] found.
Track [ CRC ] Status
01 [0b3270a2] (067/354) Accurately ripped
02 [7fbb059e] (066/353) Accurately ripped
03 [f1b71f96] (067/354) Accurately ripped
04 [4a362c1b] (067/357) Accurately ripped
05 [b8493eaa] (065/355) Accurately ripped
06 [0587536a] (066/354) Accurately ripped
07 [78ae310b] (065/353) Accurately ripped
08 [9c82d743] (066/355) Accurately ripped
09 [e8bd9afa] (062/343) Accurately ripped
10 [33fc3e5b] (067/350) Accurately ripped
11 [dc0d9566] (061/347) Accurately ripped
AccurateRip v2:
01 [1f98acd2] (012/354) Accurately ripped
02 [5591883d] (012/353) Accurately ripped
03 [9a1d3727] (012/354) Accurately ripped
04 [662982d6] (012/357) Accurately ripped
05 [9dd61b33] (012/355) Accurately ripped
06 [a01b623f] (012/354) Accurately ripped
07 [26a199e2] (012/353) Accurately ripped
08 [80056969] (012/355) Accurately ripped
09 [a2f4a11c] (010/343) Accurately ripped
10 [55db3a11] (012/350) Accurately ripped
11 [8cd34ee7] (012/347) Accurately ripped
Offsetted by -744:
01 [8484299c] (002/354) Accurately ripped
02 [20cecef4] (002/353) Accurately ripped
03 [0b1999b1] (002/354) Accurately ripped
04 [69968dbb] (002/357) Accurately ripped
05 [ebcffd5a] (002/355) Accurately ripped
06 [5076b767] (002/354) Accurately ripped
07 [40df9ad1] (002/353) Accurately ripped
08 [6cd27da9] (002/355) Accurately ripped
09 [f212e76e] (002/343) Accurately ripped
10 [8679d066] (003/350) Accurately ripped
11 [1a89cf73] (002/347) Accurately ripped
Offsetted by -664:
01 [6ef70c74] (003/354) Accurately ripped
02 [1a10532c] (003/353) Accurately ripped
03 [164377ba] (003/354) Accurately ripped
04 [2924162e] (003/357) Accurately ripped
05 [5e511a33] (003/355) Accurately ripped
06 [ce67d895] (003/354) Accurately ripped
07 [66eba9d8] (003/353) Accurately ripped
08 [9ae30ac3] (003/355) Accurately ripped
09 [efaacd52] (003/343) Accurately ripped
10 [4070d51f] (003/350) Accurately ripped
11 [2af27d37] (003/347) Accurately ripped
Offsetted by -12:
01 [ef56a602] (002/354) Accurately ripped
02 [72d87bf5] (002/353) Accurately ripped
03 [582744c0] (002/354) Accurately ripped
04 [82b7e123] (002/357) Accurately ripped
05 [2ffd4efd] (002/355) Accurately ripped
06 [55e3d4aa] (002/354) Accurately ripped
07 [ac1f41ed] (002/353) Accurately ripped
08 [bd454d6b] (002/355) Accurately ripped
09 [5a91189c] (002/343) Accurately ripped
10 [adb30fbe] (002/350) Accurately ripped
11 [f2e0b697] (002/347) Accurately ripped
Offsetted by -3:
01 [15c5f7d8] (002/354) Accurately ripped
02 [ab86f188] (002/353) Accurately ripped
03 [0cb07666] (002/354) Accurately ripped
04 [97bf9169] (002/357) Accurately ripped
05 [689a3142] (002/355) Accurately ripped
06 [49f91bfe] (002/354) Accurately ripped
07 [95f82373] (002/353) Accurately ripped
08 [5ae5f948] (002/355) Accurately ripped
09 [c551b9bc] (002/343) Accurately ripped
10 [c144e3e9] (002/350) Accurately ripped
11 [21f85c96] (002/347) Accurately ripped
Offsetted by 15:
01 [b7850cf7] (015/354) Accurately ripped
02 [616a1db3] (015/353) Accurately ripped
03 [356c8512] (015/354) Accurately ripped
04 [2f6af999] (015/357) Accurately ripped
05 [9229bb94] (015/355) Accurately ripped
06 [4fbfc1a3] (015/354) Accurately ripped
07 [46e5736c] (014/353) Accurately ripped
08 [94bba455] (015/355) Accurately ripped
09 [98d5088b] (014/343) Accurately ripped
10 [91a4fb7d] (014/350) Accurately ripped
11 [7cadbbae] (014/347) Accurately ripped
Offsetted by 18:
01 [cbcb084c] (012/354) Accurately ripped
02 [c2411c23] (013/353) Accurately ripped
03 [5c5f401e] (014/354) Accurately ripped
04 [8c7e02b9] (014/357) Accurately ripped
05 [a6124619] (013/355) Accurately ripped
06 [e79bfad9] (014/354) Accurately ripped
07 [686e0fcd] (014/353) Accurately ripped
08 [90623ff8] (014/355) Accurately ripped
09 [bbceecbe] (013/343) Accurately ripped
10 [c621d1a8] (013/350) Accurately ripped
11 [3617f89d] (013/347) Accurately ripped
Offsetted by 611:
01 [282a7b2d] (003/354) Accurately ripped
02 [5c1a3c1e] (002/353) Accurately ripped
03 [f15d09fe] (002/354) Accurately ripped
04 [2cc66866] (002/357) Accurately ripped
05 [45861809] (003/355) Accurately ripped
06 [24393c5c] (003/354) Accurately ripped
07 [620cddb6] (003/353) Accurately ripped
08 [892e903d] (003/355) Accurately ripped
09 [86c3d761] (003/343) Accurately ripped
10 [b74797b9] (003/350) Accurately ripped
11 [7c77cd9a] (003/347) Accurately ripped
Offsetted by 652:
01 [9575c594] (002/354) Accurately ripped
02 [2aaa54de] (002/353) Accurately ripped
03 [0712a742] (002/354) Accurately ripped
04 [2afe7385] (002/357) Accurately ripped
05 [7225183d] (002/355) Accurately ripped
06 [ceeb29ee] (002/354) Accurately ripped
07 [f0299be3] (002/353) Accurately ripped
08 [e9c9eed0] (002/355) Accurately ripped
09 [b1c542ae] (002/343) Accurately ripped
10 [55f49a47] (002/350) Accurately ripped
11 [a087881a] (002/347) Accurately ripped
Offsetted by 664:
01 [732a9f99] (200/354) Accurately ripped
02 [4b01fc6b] (200/353) Accurately ripped
03 [63b397a5] (200/354) Accurately ripped
04 [7a2802b3] (200/357) Accurately ripped
05 [4ae7f527] (200/355) Accurately ripped
06 [13e096e1] (200/354) Accurately ripped
07 [806eb128] (200/353) Accurately ripped
08 [bc92de3e] (200/355) Accurately ripped
09 [07229deb] (200/343) Accurately ripped
10 [a9d7bd59] (200/350) Accurately ripped
11 [610ff51c] (200/347) Accurately ripped
Offsetted by -676:
01 [cf1d5d3e] (003/354) Accurately ripped
02 [4c2289ae] (003/353) Accurately ripped
03 [c17c5a02] (002/354) Accurately ripped
04 [6c54b9d0] (003/357) Accurately ripped
05 [7969eb8d] (003/355) Accurately ripped
06 [94c2f12d] (003/354) Accurately ripped
07 [07698a87] (003/353) Accurately ripped
08 [2c3bd852] (003/355) Accurately ripped
09 [354f484c] (003/343) Accurately ripped
10 [9ef87c08] (002/350) Accurately ripped
11 [0a144b26] (000/347) No match but offset
Offsetted by -24:
01 [68d42047] (000/354) No match but offset
02 [f353bbf8] (000/353) No match but offset
03 [1a81f539] (000/354) No match but offset
04 [a3f3a12d] (002/357) Accurately ripped
05 [fd73917d] (002/355) Accurately ripped
06 [8767a515] (002/354) Accurately ripped
07 [a0e2c57c] (002/353) Accurately ripped
08 [3ce855fe] (002/355) Accurately ripped
09 [cb069e14] (000/343) No match but offset
10 [812dd39f] (000/350) No match but offset
11 [0796e31a] (002/347) Accurately ripped
Offsetted by 639:
01 [6a33dc36] (002/354) Accurately ripped
02 [621610d4] (002/353) Accurately ripped
03 [d5e7c3a6] (002/354) Accurately ripped
04 [b6d1de8d] (002/357) Accurately ripped
05 [9ab25ac1] (002/355) Accurately ripped
06 [8b81efb9] (002/354) Accurately ripped
07 [6dbc9dc3] (002/353) Accurately ripped
08 [146558ba] (002/355) Accurately ripped
09 [541bd364] (000/343) No match but offset
10 [d94b0393] (000/350) No match
11 [4ca1333c] (000/347) No match
Offsetted by 658:
01 [f24d5c19] (002/354) Accurately ripped
02 [5d9b64c1] (002/353) Accurately ripped
03 [5ba98d47] (002/354) Accurately ripped
04 [d64d7593] (002/357) Accurately ripped
05 [65b2c353] (002/355) Accurately ripped
06 [cbf6783d] (000/354) No match but offset
07 [d57434fe] (000/353) No match but offset
08 [a10564e8] (000/355) No match but offset
09 [dc8fef55] (000/343) No match
10 [00bd8cfd] (000/350) No match
11 [01313d50] (000/347) No match

Track Peak [ CRC32 ] [W/O NULL]
-- 100,0 [5988DCC8] [11CC6B60]
01 100,0 [71053267] [D93FF8CD]
02 98,8 [A800B530] [3A3869FA]
03 100,0 [589734A2] [DA6FB712]
04 98,8 [76472EEB] [ACF46D0E]
05 98,8 [2042AC87] [E51D69B3]
06 98,8 [23E4F17E] [64598088]
07 98,8 [C4E556FB] [1BC239EB]
08 98,8 [60E17B61] [76FA42C7]
09 98,8 [22507E2E] [889DE0B7]
10 100,0 [D910C174] [43655FB8]
11 100,0 [6866F161] [00ECC872]

The interesting part is:

CODE

CD-Extra data track length 00:55:03.
Using preserved id, actual id is 001f1774-010de601-bb12690c.

The real length is:
CD-Extra data track length 02:12:34.

I noticed this as I have deleted the log but I kept the data track length in an .nfo. (Hoping that at some point you would support a way to check ECD without LOG)

It seems you should tie an ID to each data length to guess which one is correct (if possible) or use a pop up to let the user select (unpractical).

This issue appeared with the recent CTDB boost due to the EAC plugin, it only happens on a handfull very popular CD so far. (This one is by Metallica)

This post has been edited by sauvage78: Nov 10 2011, 15:45

[korth]

Note: I also do not have 'hover' text in the right center of the GUI which includes Action, Mode, Audio Output, and Extra. If there's supposed to be 'hover' text anywhere in there, I don't have it.

Correction: I do have 'hover' text under 'Action: Correct filenames' in the following two locations.
Mode: Locate files
Mode: Change extension

[Gregory S. Chudo...]

Ok, i think i got it. You are using mutiselect file browser mode, and in batch modes the popup windows are disabled. When repairing, you have to use Folder browser, and select the actual .cue, not the folder.

And why tooltips aren't showing on your system, i have no idea

This post has been edited by Gregory S. Chudov: Nov 10 2011, 18:10

[korth]

Ok, i think i got it. You are using mutiselect file browser mode, and in batch modes the popup windows are disabled. When repairing, you have to use Folder browser, and select the actual .cue, not the folder.

Confirmed. Works in Folder browser.

And why tooltips aren't showing on your system, i have no idea

Just gave you that info in case it was 'code' related.

[Gregory S. Chudo...]

Personnaly, as long as CTDB is not meant to be a verification database, I prefer the old way. I like seeing the CTDBID.
If readability is the issue, I think the new look is confusing as it is too close to the AR displaying.

CTDB will also be a verification database when it's large enough, and it rapidly becomes large enough.

What do you need to see CTDBID for?

The new look is supposed to look close to AR. That's the point. That's what makes it easier to interpret, because people already know how to read this.

[sauvage78]

I don't really need CTDBID for anything I just like to see the mechanics (I like knowing how to split the total matches sum even if not very usefull). If the new look is supposed to look like AR, then yes it does.

I always thought the data within CTDB was too incomplete for verification, like there was not information for each samples/frames but only for selected ones in order to maximize the correction probability versus the needed space to store the audio correction. Was I wrong from start ? Or maybe CTDB store both enought data for a full cheksum verification & partial data for correction ? I need your insight here to understand why CTDB will suddenly become a verification database ? And if really so, why do you still need AR at all ?

This post has been edited by sauvage78: Nov 11 2011, 08:17

[Gregory S. Chudo...]

The only thing CTDB didn't have compared to AR was track crcs, and it has them now.
Thanks to Andre, the number of submissions grows very fast, so quite soon CTDB will be able to rely on it's own confidence values and will become completely independent from AR.

[sauvage78]

Be scared Sp n ! It's revolution !

[philaphonic]

Gregory, in case you do not hear it enough, thank you for CUETools! It is an excellent, well-done music tool.

[acmodeu]

Why does CT ignore manually edited tags and leaves them as the were found via internet databases?

[spoon]

Be scared Sp n ! It's revolution !

Nice colors

To answer - not scared, AccurateRip is soon to be 10 years old (from first concept), and has around 1 billion track submissions in the database, I would like to think that what differentiates AccurateRip from others (there have been 2 which have come and gone over the years) is the effort put in on the backend to keep the crap out, the front end (as you find in EAC or dBpoweramp) is 100x less complex, even with checking across pressings than the backend.

We are giving AccurateRip a push, to be able to verify tracks ripped from any ripper, so the iTunes crowd can quantify what iTunes is really putting out and possibly to do small scale corrections from what will be one of the largest stores of lossless tracks online.

[korth]

I would like to think that what differentiates AccurateRip from others (there have been 2 which have come and gone over the years) is the effort put in on the backend to keep the crap out

I do agree that the CTDB could do a better job at keeping the crap out.
I had no control over which rips EAC submitted. Yes I ripped an ISO with EAC. It was the way I stored backups before using EAC. My original was damaged so I had to go to the backup. Yes, I could have deleted the bin file from the AccurateRip folder, but I didn't. Now I submit my rips to the CTDB. Due of your backend, I can't submit to AR anymore.

[korth]

Sorry, called away before I could edit.
My point was that all my rips are now considered crap by AR regardless of whether or not they actually are. Your backend is a little too unforgiving.

This post has been edited by korth: Nov 11 2011, 19:13