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.

Oh, that's too bad : I have manually splitted hidden tracks in maybe 10 albums over more than 1000, and this seems to be one of them. Apologies ! I have tried rejoining tracks 13 and 14 using foobar, tested again, and the problem remains the same. Maybe I've manually removed the silence between both tracks, so I'd better pick another album.

However, what would be great would be if CUETools could still be able to give an AccurateRip confidence score for tracks 01-12 that have been perfectly ripped... Ideally it should skip track 14, say that tracks 01-12 are accurate, track 13 isn't (since it has been splitted), and track 14 is unknown for this album.

Let's give it another try with "The Eminem Show", with an AR score of 131 a year ago. The good news is that CUETools works. Now here are the results :

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 ?

And one last thing : how can we make the results to be written directly into the file tags ?(e.g. one tag for the CRC, one tag for the "200/229", one tag for the "Accurately ripped as in pressing(s) #1", and so on...

However, what would be great would be if CUETools could still be able to give an AccurateRip confidence score for tracks 01-12 that have been perfectly ripped... Ideally it should skip track 14, say that tracks 01-12 are accurate, track 13 isn't (since it has been splitted), and track 14 is unknown for this album.

Unfortunately, this is impossible. You have to know the id of the disk to be able to compare it to the database, and diskId depends on the number and length of the tracks. So if you split a track, cut out silence - there's no way to tell which disk it is that you have.