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

[Gregory S. Chudo...]

Please welcome, CUETools v2.1.4. (CUETools download page) or direct link: http://www.cuetools.net/install/CUETools_2.1.4.rar

16.04.2012: CUETools 2.1.4:
* CTDB 2.0: now ignoring pregap in parity calculations
* CTDB 2.0: popular CDs can have twice larger correction files
* CTDB 2.0: confidence values no longer include AccurateRip data
* CTDB 2.0: simplified (per-track) verification log
* CTDB 2.0: faster verification process with less network traffic
* CUERipper: support for some older drives, like PLEXTOR W1210A
* CUERipper: support for cover art
* CUERipper: main window resizable
* CUERipper: real test&copy mode
* CUERipper: options dialog
* Tagging: support for release date, release country, disc subtitle, label, catalog number, comment
* Local DB: can now refresh folder, removing missing files from database and adding new files.
* Codecs: LAME encoder updated to use libmp3lame.dll, which is now included in CUETools download (version 3.98.4)
* Various bug fixes

14.06.2011: CUETools 2.1.2:
* AccurateRip v2 support (without cross-pressing verification)
* EAC CTDB plugin
* CTDB now supports musicbrainz Next Generation Schema (NGS) metadata. Old musicbrainz library removed. New musicbrainz NGS metadata can now be used in filename templates, including %discname%, %label%, %releasedate%, %country%, %releasedateandlabel%, %discnumberandname%
* CTDB submissions are now based on the same data that was used when verifying, so 'submit' script was removed, and data is submitted after verification, after showing confirmation dialog
* CTDB verification is now much faster
* Local DB: option to purge records
* Local DB: now shown in the same window as folder browser
* metadata editing window size is now saved in settings
* CUERipper now sends CD barcode and rip quality when submitting
* support for wierd CDs with two data tracks before audio

IMPORTANT: .NET Framework 2.0 (SP2) required. If you get a "could not load file or assembly" error message for CUETools.Codecs.TTA/APE/WavPack/FLAC, make sure the recent version of Visual C++ 2008 runtime files (x86,x64) is installed.

You can always download the latest source code from project's SVN repository at SourceForge.
Instructions for svn access can be found here.

This post has been edited by Gregory S. Chudov: Apr 17 2012, 03:55

[Fandango]

WAV output is greyed out<edit>
Ah I didn't see the "embed cue sheet" was selected! But still, if the configuration file of the 1.9.1 version had WAV output, 1.9.2 will still output a WAV file... the greyed out radio button is selected 1.9.2 needs at least an error box before conversion begins or automatically change to FLAC or (best solution IMHO) default to "Single File + CUE" if is was "Single File" in 1.9.1.
</edit>when I want to add a cue sheet via drag & drop into the "Input:" box, the cue sheet is not added.

But apart from that... embed cue sheet, add AR CRC tags, and so on... great job!

The status report is a nice feature, too. Make it so that the log can be written to the output dir (using the name scheme) for each conversion, would be useful for batch conversion.
<edit>...I'm going blind I guess.</edit>

This post has been edited by Fandango: Oct 3 2008, 17:35

[Gregory S. Chudo...]

WAV output is greyed out<edit>
Ah I didn't see the "embed cue sheet" was selected! But still, if the configuration file of the 1.9.1 version had WAV output, 1.9.2 will still output a WAV file... the greyed out radio button is selected 1.9.2 needs at least an error box before conversion begins or automatically change to FLAC or (best solution IMHO) default to "Single File + CUE" if is was "Single File" in 1.9.1.
</edit>when I want to add a cue sheet via drag & drop into the "Input:" box, the cue sheet is not added.

But apart from that... embed cue sheet, add AR CRC tags, and so on... great job!

The status report is a nice feature, too. Make it so that the log can be written to the output dir (using the name scheme) for each conversion, would be useful for batch conversion.
<edit>...I'm going blind I guess.</edit>

Wierd, drag&drop works for me.

Hi, Gregory sent me to this thread from this one : http://www.hydrogenaudio.org/forums/index....showtopic=56531

What I don't understand is that my need is to be able to analyze a whole album made of single-track files in lossless form (FLAC, etc.) put inside the same album folder. I may be blind too Fandango , but I don't see CUETools doing that yet. Am I wrong ?

This functionality is mandatory for me since I have thousands of single-FLAC files and not a single cuesheet.

No, it's me who is blind, i didn't notice you didn't have cuesheets.
I'll think about automating the process, but for now i would recomend to write a script whch would create cuesheets for each directory. This would be very easy if your files have gaps appended. If they have gaps prepended or left out, there's nothing really that can be done - you have to know the size of gaps to be able to compare the disc to the database. Also if the first track had index 00, you're out of luck.

Here is a a template for your cuesheet:

CODE

PERFORMER "Performer"
TITLE "Title"
FILE "first_filename.flac" WAVE
  TRACK 01 AUDIO
    TITLE "title 01"
    INDEX 01 00:00:00
FILE "second_filename.flac" WAVE
  TRACK 02 AUDIO
    TITLE "title 02"
    INDEX 01 00:00:00
...

In fact, you don't even have to specify correct file names - you can use an option "Preprocess with filename corrector if unable to locate audio files".
You just have to have the correct number of tracks.
So you can create those dummy cuesheets by hand, and then just copy into each folder a .cue sheet which has the same number of tracks as this folder.

This post has been edited by Gregory S. Chudov: Oct 4 2008, 03:33

[foorious]

No, it's me who is blind, i didn't notice you didn't have cuesheets.
I'll think about automating the process, but for now i would recomend to write a script whch would create cuesheets for each directory. This would be very easy if your files have gaps appended. If they have gaps prepended or left out, there's nothing really that can be done - you have to know the size of gaps to be able to compare the disc to the database. Also if the first track had index 00, you're out of luck.

Well, I believe there must already be some utility that can batch-create cuesheets from single-track files. I'm talking about simply selecting a start folder, and then the utility would scan all the subfolders, find all tracks within a given subfolder, then create a cuesheet from them. Am I wrong ?

I am not a programmer, but I guess if such utility doesn't exist yet, it should be quite easy to create, and also to implement in CUETools. So Gregory, I hope you'll have the time to automate such process in the future. Thank you.

So you can create those dummy cuesheets by hand, and then just copy into each folder a .cue sheet which has the same number of tracks as this folder.

Um, yes, sure, but I have several thousand folders, so by hand is not a solution...

[No Fun]

Strange...
Can it be that CUE Tools cannot find right offset for a set of FLACs linked up with a dummy cuesheet?
In my case it gives only "(00/01) No matches.", while TripleFlac! easily found offset to be -1501 (with "LeadIn: 0") and verification in CT with that value showed "Accurately ripped as in pressing(s) #1". Also when I converted "tracks + dummy cuesheet" to WAV "Single File + CUE", ARcue found -1501 as well.
At the same time with another rip (in the form of "flac-image + cuesheet") verification, as it should, showed two results: one without offset correction ("No matches") and another, "offsetted".

Command line parameters is the feature I missed so much! Very nice verification mode & awesome new log!
Now I wish only CT could directly handle a set of FLAC files (or folder containing them) - I'd throw away TripleFlac!
As for usability I can suggest hotkeys (Alt+letter) and Write Offset box right in the main window (yeah, it was there already some time ago, and IMHO so it were much more convenient). Also an option to set up filename for AccurateRip report would be nice to have. And to be completely a bore… maybe you can remove those points at the end of almost every line of AR report to save a few bytes on HDD?