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

Picard picks Release and Tracks other than what Release and Track MBIDs point to

XMLWordPrintable

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

      I just ripped https://musicbrainz.org/release/b1449406-45d0-4384-8eb2-7f7dcc572979 with whipper which supplies them with MBIDs. I have Picard set to ignore MBIDs when loading files, but even then, when using the magic wand "Look up" button, shouldn’t it utilise the MBIDs to realise exactly which Release to pull based on the existing Release MBID? I’ve tried to untick the "Ignore MBIDs when loading new files" option and using both "Look up" and "Scan" on the (non-clustered) files, it’s completely arbitrary which of the releases in the release group it decides to pull in, even though all files have MBID tags for both release, release group, recording, track, work, artist, release artist… so it should be able to uniquely pin‐point which exact track on which exact release the files are.

            Unassigned Unassigned
            freso Freso
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:

                Version Package