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

[foorious]

I think I have the same problem as "No Fun", or at least a similar problem.

I've tried CUETools (latest version available in this topic - "Update 4") on one album I'm totally certain of : Alanis Morissette - Jagged Little Pill. This album was my absolute personal AccurateRip record a year and a half ago, with a confidence score of 181. So I'm quite certain it's a perfect rip, and a well-known one from AccurateRip's point of view.

So we start from 14 separate FLAC files, with no cuesheet at all. With CUETools "CUE Sheet Creator" button, I create a dummy cuesheet. Here it is :

CODE

REM COMMENT "CUETools generated dummy CUE sheet"
FILE "01 - All I Really Want.flac" WAVE
TRACK 01 AUDIO
INDEX 01 00:00:00
FILE "02 - You Oughta Know.flac" WAVE
TRACK 02 AUDIO
INDEX 01 00:00:00
FILE "03 - Perfect.flac" WAVE
TRACK 03 AUDIO
INDEX 01 00:00:00
FILE "04 - Hand In My Pocket.flac" WAVE
TRACK 04 AUDIO
INDEX 01 00:00:00
FILE "05 - Right Through You.flac" WAVE
TRACK 05 AUDIO
INDEX 01 00:00:00
FILE "06 - Forgiven.flac" WAVE
TRACK 06 AUDIO
INDEX 01 00:00:00
FILE "07 - You Learn.flac" WAVE
TRACK 07 AUDIO
INDEX 01 00:00:00
FILE "08 - Head Over Feet.flac" WAVE
TRACK 08 AUDIO
INDEX 01 00:00:00
FILE "09 - Mary Jane.flac" WAVE
TRACK 09 AUDIO
INDEX 01 00:00:00
FILE "10 - Ironic.flac" WAVE
TRACK 10 AUDIO
INDEX 01 00:00:00
FILE "11 - Not The Doctor.flac" WAVE
TRACK 11 AUDIO
INDEX 01 00:00:00
FILE "12 - Wake Up.flac" WAVE
TRACK 12 AUDIO
INDEX 01 00:00:00
FILE "13 - You Oughta Know (Alternate Take).flac" WAVE
TRACK 13 AUDIO
INDEX 01 00:00:00
FILE "14 - Hidden Track.flac" WAVE
TRACK 14 AUDIO
INDEX 01 00:00:00

Then I set the Audio Output to "none", AccurateRip to "Verify", and I click on "Convert" (maybe "Analyze" would be better in this case IMHO). Here are the results in the dialog box :

CODE

[Disc ID: 001d2cdc-0137a6e5-bc0d410e]
Track [ CRC ] Status
01 [00000000] Disk not present in database.
02 [00000000] Disk not present in database.
03 [00000000] Disk not present in database.
04 [00000000] Disk not present in database.
05 [00000000] Disk not present in database.
06 [00000000] Disk not present in database.
07 [00000000] Disk not present in database.
08 [00000000] Disk not present in database.
09 [00000000] Disk not present in database.
10 [00000000] Disk not present in database.
11 [00000000] Disk not present in database.
12 [00000000] Disk not present in database.
13 [00000000] Disk not present in database.
14 [00000000] Disk not present in database.

Same thing if I set AccurateRip to "Fix Offset" (although I'm certain my offset is good here)

Obviously there's something wrong here...


EDIT - Gregory, regarding the "Fix Offset" mode, personally I am interested in CUETools mainly for verification purposes. I'd like a tool that will help me batch-analyze all my CDs and write relevant AccurateRip info : AR info(accurate rip, different pressing, not present, not accurate), AR confidence score, etc... directly to the file tags, all in a single operation.
E.g. : AR info tag = "Accurate Rip" and AR confidence tag = "181".
Then with foobar I will easily locate all suspicious CDs and decide myself what to do with them (or not). What I want to say is that I too don't want CUETools to automatically perform conversions. I'd like it to only test the files, and then I'll decide what I want to do or not.
An idea could be to include the "Verify Offset" feature into the "Verify" option. So with "Verify" we could (1) verify against the AR database with no offset correction, and (2) try other offsets if necessary then verify again. All this without conversion.

Thank you again for all your work.

This post has been edited by greynol: Oct 14 2008, 03:31

[Gregory S. Chudo...]

Gregory, regarding the "Fix Offset" mode, personally I am interested in CUETools mainly for verification purposes. I'd like a tool that will help me batch-analyze all my CDs and write relevant AccurateRip info : AR info(accurate rip, different pressing, not present, not accurate), AR confidence score, etc... directly to the file tags, all in a single operation.
E.g. : AR info tag = "Accurate Rip" and AR confidence tag = "181".
Then with foobar I will easily locate all suspicious CDs and decide myself what to do with them (or not). What I want to say is that I too don't want CUETools to automatically perform conversions. I'd like it to only test the files, and then I'll decide what I want to do or not.
An idea could be to include the "Verify Offset" feature into the "Verify" option. So with "Verify" we could (1) verify against the AR database with no offset correction, and (2) try other offsets if necessary then verify again. All this without conversion.

First of all, "Verify" option does verify offsets also. "Fix" option on the first pass does exactly the same as Verify, only it then procedes with conversion (possibly using the offset found in first pass).

"Verify" also writes AR tags in source file on success, but currently only flac album image (with embedded cue) is supported for this.

So as i see it, two features are missing: writing AccurateRip tags in image that is split into tracks, and special tags for non-offset corrected rips - because right now they are tagged as inaccurate.

However, forgive me but I'm not sure to understand the results.
E.g. : "01 [4e72a4c7] (200/229) Accurately ripped as in pressing(s) #1"
- What does the "200/229" mean ?
- What does the "#1" mean ?

200/229 is the confidence level, i.e. 200 of 229 people who ripped this disc got the same results as you.

#1 means the first database entry. There are several entries for each disc in database. Is it #1 or #10, doesn't really matter.

Anyway, only confidence level is important.

This post has been edited by Gregory S. Chudov: Oct 10 2008, 11:02