Batch compare AccurateRip CRCs later (upon later submissions?)

[Porcus]

Idea:

* AccurateRip IDs and CRCs stored in tags.
* Scan my music library and build a list over not accurate rips
* Connect to the database and see if there are any changes
* Report to user that
- "The following files are now verified as accurate"
and more interesting:
- "For the following albums, some (but not all) tracks are verified as accurate"
* Update metadata if user accepts.

Purpose: Offer the user a "red flag" of discs where -- later -- someone else has only a partial match, and where there could be errors and need for re-ripping.

[LtData]

Re: Batch compare AccurateRip CRCs later (upon later submissions?)

I believe an after-ripping AR tool is planned, but nothing more has been said of it. Do note that it will require dMC to write the AR result to a tag.

[Porcus]

Re: Batch compare AccurateRip CRCs later (upon later submissions?)

Do note that it will require dMC to write the AR result to a tag.

Which it can. But is it necessary, as long as the track is identified in the tag?

[EliC]

Re: Batch compare AccurateRip CRCs later (upon later submissions?)

It has also been said that the tool will require the raw CD TOC.

[LtData]

Re: Batch compare AccurateRip CRCs later (upon later submissions?)

No, just track identification is not enough. You need the CD TOC and the AR checksum, as this is calculated when the track is ripped. You cannot examine an encoded file for a checksum of the audio that was ripped with 100% certainty.

[Porcus]

Re: Batch compare AccurateRip CRCs later (upon later submissions?)

Is CD TOC unique from the AccurateRipDiscID tag?

As for CDDB_ID, yes I know it does not determine the CD uniquely, but if there are two CDs with the same CDDB_ID and the same AccurateRip checksum for each track, then they are most probably not the same release. No bigger problem than different pressings, I would assume.