Skip to content

UberFLAC Guide

Nongorilla edited this page Oct 21, 2017 · 1 revision

EAC log requirements

EAC correctness requires that CDs are ripped in secure mode with no C2 and every copied track is error free. If test CRCs are generated they must match their copy CRCs. There must be only one log file per directory. Testing has been performed using EAC version 0.9 beta 4 and version 1.3 (current) with the AccurateRip and CueTools plugins. For more information see:

FLAC correctness requires valid intrinsic CRC-16 checks and that the CRC-32 of the decompressed audio matches the CRC-32 given in the EAC log. Each FLAC file must be structurally correct. There must be no extra FLAC files in the directory.

There are two elevated levels of correctness for rips offered by UberFLAC: Proven rips and Ubertagged rips. Proven rips pass all the tests above but also take advantage of additional capabilities offered by EAC version 1 (or later) with the CUETools and AccurateRip plugins. Ubertagged rips are rips that adhere to a set of tagging rules.

Proven rip requirements

  1. Disc must be ripped with EAC version 1 or later.
  2. EAC log self-hash must exist and pass on-line verification.
  3. CUETools verification must be attempted and no track may fail.
  4. Disc must have at have any of: AcurrateRip confidence 1, CUETools DB confidence 1, or successful test pass.
  5. Tracks must be encoded with FLAC 1.2.1 or greater.
  6. Disc must pass the standard battery of UberFLAC verifications.

Steps 3 and 4 are confirmed by analyzing the EAC log contents. Steps 5 and 6 are confirmed by analyzing the log and FLAC files.

Ubertag requirements

UberFLAC inspects the FLAC tags listed below and, by default, reports issues primarily as warnings. If the /ubertags switch is supplied, egregious warnings are escalated to errors. In addition there are checks for extra white space in several of these tags. With the exception of ALBUMARTISTSORTORDER, no checks are made for multiple entries for the same tag and only the first tag entry will be inspected.

TRACKNUMBER

Required. Must be digits only with no leading zeroes. Must be sequential and the order must match the order of files in the EAC log file by CRC-32.

ALBUM

Required. Must be consistent for all tracks.

DATE

Required. Must be consistent for all tracks. Must be in the form YYYY or YYYY-MM-DD where YYYY between 1900 and 2099.

RELEASE DATE

Optional. If present, must be consistent for all tracks and in the form YYYY or YYYY-MM-DD where YYYY between 1900 and 2099.

ORIGINAL RELEASE DATE

Optional. If present, must be in the form YYYY or YYYY-MM-DD where YYYY between 1900 and 2099.

TRACKTOTAL

Optional. If present, must be digits only with no leading zeroes, consistent for all tracks, and equal to the number of tracks in the EAC log.

DISCNUMBER, DISCTOTAL

Optional. If present, must be digits only with no leading zeroes and consistent for all tracks.

ALBUMARTIST

Required if ARTIST tags are missing or not consistent. If present, must be consistent for all tracks.

ALBUMARTISTSORTORDER

Optional. May contain multiple entries. If present, all entries must be consistent for all tracks.

BARCODE, CATALOGNUMBER, COMPILATION, ORGANIZATION

Optional. If present, must be consistent for all tracks.

Deprecated and nonpreferred tags

TOTALTRACKS, TOTALDISCS

Use TRACKTOTAL and DISCTOTAL instead.

ALBUM ARTIST, PUBLISHER, ALBUMARTISTSORT

Use ALBUMARTIST, ORGANIZATION, ALBUMARTISTSORTORDER instead.

Clone this wiki locally