Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-474

Better Handling of Unknown Releases

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Lookup & Match
    • None

      from http://bugs.musicbrainz.org/ticket/6006

      When there are multiple releases of a single album, picard should better handle tagging an album whose specific release is unknown. This covers three aspects:

      1] Scan/AcoustID: When scanning a a cluster, Picard/AcoustID disregards the cluster and splits the album across several different releases, based only on best AcoustID correlation.

      2.1] Lookup: When looking up an cluster lacking release information tags, Picard inaccurately chooses an incorrect release (usually). If the release information is unknown, this generation of unknown data is tantamount to inaccurate tagging.

      2.2] Scanning: When scanning a cluster for an AcoustID match, the results are usually totally random. Picard/AcoustID often applies different release information to the same cluster each new scan.

      3] If the release information is unable to be determined, Picard should not save the release information. There should be an option to automatically strip release tags: "ASIN, Barcode, Catalog Number, MusicBrain*ID, Record Label, Release Country, Release Status", unless the tags are already present or the user adds the appropriate information, in which case a release can be determined.

            Unassigned Unassigned
            nikki nikki
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:

                Version Package