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

Allow local track / release overrides

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Lookup & Match
    • None

      This is a different solution to the same issue as described in PICARD-2968, ie you have an almost perfectly match of an album with 12 / 12 but realize you locally have an extra (bonus) tracks.

      If you don't know for sure what the source of your release was, then you might want to keep those extra tracks but don't submit a new release to musicbrainz.

      What I do now in those cases is match those files to the last track in the release, then manually overwrite the track number & track title.

      This works for saving the release once, but (I think) because Picard always saves the musicbrainz id's with each track and you cannot stop Picard from adding those id's, it means that when you then load the release in Picard again Picard matches those extra tracks as duplicates of the last track and you potentially loose the track number & title if you dont manually update them again.

      So it would be great if you could add extra tracks to a release which are not changed/removed after importing the release in Picard again. I think this mainly means it should be possible to not write the musicbrainz track id tag?

            Unassigned Unassigned
            zniarbatem zniarbatem
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Version Package