How to verify FLAC files against the AccurateRip database

accurateripaudiocompact-discflacripping

I've been ripping my CD's to CUE+FLAC so that I get image files that allow me to replicate the actual CD. This serves me as a backup and as an easy access to the "media" if I need to re-rip the CD's (in case of an improvement in the AAC/MP3 encoder, or a new format).

Some CD's were ripped using EAC, others using XLD and more recently I've been using Rip. All of them support AccurateRip, but some of my CD's weren't found in the database and for others AccurateRip wasn't used at all.

I would like to verify the FLAC files against the AccurateRip database so that I can find if the CD appeared there, and if matches my ripped image. If it doesn't, I could try again at a later time or try re-ripping with a different tool and verify the AccurateRip hash against that of my first rip.

Is it possible to verify existing FLAC files against the AccurateRip database? If so, how would I do that?

Best Answer

CueTools is supposed to be able to do that.

http://www.cuetools.net/doku.php/cuetools:download

Reference:

http://forum.dbpoweramp.com/showthread.php?t=17770

Cuetools will now process batches of flac files and verify them again accurate rip. You no longer have to create the cue file.

Related Solutions

How to interpret the output from Accuraterip verification

The above rip is an example of one performed without sample offset correction. Here is another example of an accuraterip assessment for a rip performed with the correct sample offset (96 in this case) applied:

Calculated CRCv1    : B75C614C
Calculated CRCv2    : DEB788B6
------------------------------
Accurately ripped (confidence 105+101/307)
Accurately ripped with offset -29 (confidence 18+18/307)
Accurately ripped with offset -628 (confidence 20+20/307)
Accurately ripped with offset -947 (confidence 18+18/307)
Possibly accurately ripped with offset -29 (confidence 101+101/307)
Possibly accurately ripped with offset -628 (confidence 20+20/307)
Possibly accurately ripped with offset -947 (confidence 20+20/307)
================================================================================
11/11 Accurately ripped (confidence 213)
11/11 Accurately ripped with offset -29 (confidence 40)
11/11 Accurately ripped with offset -628 (confidence 42)
11/11 Accurately ripped with offset -947 (confidence 38)
11/11 Possibly accurately ripped with offset -947 (confidence 42)
11/11 Possibly accurately ripped with offset -628 (confidence 40)

The main difference is the presence of the line

11/11 Accurately ripped (confidence 213)

which reflects accuraterip matches with the same offset as the rip (which is 96 in this case, but not shown). This is the line which reports the overall accuracy of the rip and that, in this case, 213 other checksum reports match ours.

Here is an example of the same disc ripped by the same software (abcde in this case) but without a sample offset:

Calculated CRCv1    : AF3854B4
Calculated CRCv2    : F5401F9C
------------------------------
Accurately ripped with offset 96 (confidence 101+101/307)
Accurately ripped with offset 67 (confidence 18+18/307)
Accurately ripped with offset -532 (confidence 20+20/307)
Accurately ripped with offset -851 (confidence 18+18/307)
Possibly accurately ripped with offset 96 (confidence 105+105/307)
Possibly accurately ripped with offset 67 (confidence 101+101/307)
Possibly accurately ripped with offset -532 (confidence 20+20/307)
Possibly accurately ripped with offset -851 (confidence 20+20/307)
================================================================================
11/11 Accurately ripped with offset 67 (confidence 40)
11/11 Accurately ripped with offset 96 (confidence 210)
11/11 Accurately ripped with offset -532 (confidence 42)
11/11 Accurately ripped with offset -851 (confidence 38)
11/11 Possibly accurately ripped with offset -851 (confidence 42)
11/11 Possibly accurately ripped with offset -532 (confidence 40)
11/11 Possibly accurately ripped with offset 67 (confidence 210)
11/11 Possibly accurately ripped with offset 96 (confidence 216)

Here there is no line without an offset. You will also notice that the two calculated CRC values (there are two because Accuraterip has two versions of its CRC) differ from those above.

The reported offsets are different to those used for the rip and, because no offset was applied, all of them are different. This is showing us accurate rips for this disc at various offsets (these don't match our rip but are shown for information).

To get an accurate rip it is necessary to rip with a specific offset.

Offsets are reproducible using different software (such as abcde or Whipper on Linux) as long as the correct sample offset is used.

Best Answer

Related Solutions

How to interpret the output from Accuraterip verification

Related Question