CUETools

From CUETools wiki
Jump to: navigation, search
Cuetools214.png

Contents

CUETools

CUETools is a tool for lossless audio/CUE sheet format conversion. The goal is to make sure the album image is preserved accurately. A lossless disc image must be lossless not only in preserving contents of the audio tracks, but also in preserving gaps and CUE sheet contents. Many applications lose vital information upon conversion, and don't support all possible CUE sheet styles. For example, foobar2000 loses disc pre-gap information when converting an album image, and doesn't support gaps appended (noncompliant) CUE sheets.

Download

Download links for CUETools binaries, source code and prerequisites can be found here.

Supported formats

Supports WAV, FLAC, APE, LossyWAV, ALAC, TTA, and WavPack audio input/output. Audio must be 16-bit, 44.1kHz samples stereo (i.e. CD PCM). Supports every CUE sheet style (embedded, single file, gaps appended/prepended/left out). It is also possible to process a set of audio files in a directory without a CUE sheet, or use a RAR archive as an input without unpacking it.

Use cases

* Convert a single-file album image with CUE sheet to a file-per-track album image
* Convert a single-file album image with CUE-sheet-per-album to a single-file album image with CUE-sheet-per-track album image (feature request)
* Convert a file-per-track album image with CUE sheet to a single file album image
* Convert a file-per-track album image without a CUE sheet to a single file album image with simple CUE sheet
* Convert an album image from one lossless codec to another, preserving CUE sheet structure
* Verify a (possibly non offset-corrected) album image against AccurateRip database
* Apply offset correction to a rip made without offset correction
* Prepare an album image for burning with software, which does not handle drive write offsets, by applying offset
* Extract an album image directly from a RAR archive without unpacking it, and save it in a different format
* Fix filenames in a CUE sheet, if the files were renamed or converted to a different format.
* Compress to LossyWav, creating a lossy output + correction file.
* Convert a HDCD image to 24-bit / 20-bit / LossyWav 16-bit audio files (irreversible).
* Convert an album image with minor audio errors to one without errors, using correction files in the CUETools Database.

AccurateRip support

Since version 1.9.2, CUETools can verify album images using AccurateRip database. ARCue and TripleFLAC were an inspiration. The unique feature of CUETools AccurateRip verification is offset detection. Rip that was made without offset correction can still be verified against the database, offset can be found and corrected.

Sample log:

[AccurateRip ID: 000a800a-00305be0-3e0c9905] found.
Track   [  CRC   |   V2   ] Status
 01     [6cc4879f|f78bc58b] (00+00/11) No match
 02     [fa12db35|5667d128] (00+00/11) No match
 03     [602a5adc|4e7f35bf] (00+00/11) No match
 04     [ea072e18|65b2f081] (00+00/11) No match
 05     [d152bb74|908e8e26] (00+00/11) No match
Offsetted by -6:
 01     [c9dde5d4] (02/11) Accurately ripped
 02     [5e163745] (02/11) Accurately ripped
 03     [ab6e75ee] (02/11) Accurately ripped
 04     [6a44c49e] (02/11) Accurately ripped
 05     [35705594] (02/11) Accurately ripped
Offsetted by 42:
 01     [d8ff4b37] (07/11) Accurately ripped
 02     [08ef0a3a] (07/11) Accurately ripped
 03     [f3d2920f] (07/11) Accurately ripped
 04     [eabd6e74] (07/11) Accurately ripped
 05     [b617c805] (07/11) Accurately ripped

More information about the log can be found here.

What's wrong if i'm sure the CD is present in the database, but CUETools doesn't find it

CDs in the AccurateRip database are identified by the track lengths. Pregap and data track included. If you rip to separate tracks without a .cue sheet, this information is lost. If the CD had a pregap and/or data track, you won't find it in the database without a .cue sheet (or using dummy .cue sheet, or using foobar2k-generated .cue sheet). Sometimes you will find a wrong set, e.g. if the disc was released in two versions - with and without data track. You rip a version with data track, and verify it without a .cue sheet, and your files look like the version without a data track. Or you rip a CD which has a pregap, and try verify it without a .cue sheet, your files look like a CD-R which someone made from such a rip, and then ripped it.


So make sure you have original .cue sheet and EAC .log available. Keeping original .cue insures that you don't loose the pregap length. Data track length is not stored in .cue sheet, but if you have an EAC log made by the recent versions of EAC, CUETools can find the data track length from it. For this to work, .log file should have the same filename as a .cue file, except for extension. If you don't have a .log file, but your .cue sheet contains original DISCID (like all .cue sheets made by recent EAC versions), CUETools can detect that the datatrack was present and hint for a possible data track length range. You can try to enter 75 different values in that range manualy to find an exact length.

Command line options

 * CUETools.exe /verify <filename> - verify an image using AccurateRip database.
 * CUETools.exe /convert <filename> - convert an image using the settings of the "convert" profile in the GUI.
 * CUETools.exe <filename> - open CUETools dialog, with input file set to <filename>.
 * ArCueDotNet.exe <filename> - console version of AccurateRip verification.
 * LossyWAVSharp.exe <filename> - console lossyWAV compression utility

Builtin encoders

 * flac: libFLAC, libFlake, FLACCL (former FlaCuda) (CUETools FLAC encoders comparison)
 * wv (WavPack): libwapkack
 * ape (Monkey Audio): MAC_SDK
 * tta (True Audio): ttalib
 * m4a (ALAC): libALAC

Path formatting

CUETools uses output path templates similar to foobar2000 title formatting syntax.

Supported platforms

CUETools is a .NET application, written in C#. Processor dependent plugins are included for 32 bit (x86) and 64 bit (x64) Windows versions. .NET Framework 2.0 SP2 and Visual C++ 2008 runtimes are required.

Users report they have been able to use it under linux, using

  • Mono, but in this scenario only WAV audio is supported, as other codecs are not yet ported to C#.
  • Wine, using Winetricks or PlayOnLinux to install the .NET Framework and Visual C++ 2008 runtime files in a wineprefix.

Known issues

  • On discs with multiple entries, Repair function needs to display a window asking confirmation and presenting you with a choice of available repair targets. This window is currently only visible when Input: is set to Folder browser mode with a single file (or file grouping) selected. Batch modes (Multiselect Browser mode, Drag'n'drop mode or selecting an entire folder in Folder Browser mode) not supported.
  • In Multiselect Browser mode, Local DB won't expand using mouse after F5 refresh. Temporary solution: Select then use right arrow key on keyboard to expand.

More bugs might be mentioned in the development thread and bug tracker, both of which are linked below

Links

External links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox