Skip to content

"MusicBrainz-ID contributor merging propagates bad ARTIST tags from mistagged compilations onto unrelated, correctly-tagged artists" #1654

Description

@wachris702
No description provided.

Activity

  1. michaelherger commented on Sep 7, 2026

    @michaelherger
    Member

    Isn't the answer in the title already?

    bad ARTIST tags from mistagged compilations

    Fix the tags?

  2. michaelherger commented on Sep 7, 2026

    @michaelherger
    Member

    BTW: what has happened to the lengthy description? I appreciate keeping it short. But NO description is a bit too much of an optimisation 😂

  3. mikeysas commented on Sep 7, 2026

    @mikeysas

    @wachris702 - there is extensive discussion about this across multiple threads on the forum that I would encourage you to check out with a quick search on "musicbrainz_artistid"

    This is also a frequently duplicated issue with the most recent ones being:
    #1545
    #1555
    #1578

    There is a work in process PR to address this more broadly with support for single value display artist tags and multi value contributor tags similar to the way ARTIST vs ARTISTS works with most taggers that import from MusicBrainz.
    PR #1576
    Please be aware that there is much effort being made there to ensure this change will not adversely impact the significant number of long standing LMS users that do not use MusicBrainz IDs in their tags so this is not a simple effort and there is no guarantee that the volunteers working on this will complete the enhancement. If you are familiar with how to, you are welcome to test it and provide feedback. You can find more details on @darrell-k GitHub fork.

  4. wachris702 commented on Sep 7, 2026

    @wachris702
    Author

    Being honest here, I was using AI to help me and it found this bug. I started to submit it knowing I'm not smart enough to post on these boards but smart enough toi know that the bug issue may help someone. Still trying to figure out if it's a genuine issue on my end or lms. Sorry about the confusion.

  5. mikeysas commented on Sep 7, 2026

    @mikeysas

    Being honest here, I was using AI to help me and it found this bug. I started to submit it knowing I'm not smart enough to post on these boards but smart enough toi know that the bug issue may help someone. Still trying to figure out if it's a genuine issue on my end or lms. Sorry about the confusion.

    Take a look at https://forums.lyrion.org/forum/user-forums/ripping-encoding-transcoding-tagging/1816764-lms-metadata-scaan-overrides-local-tags

    I believe this was the thread that led to the current work in process, but there are several others out there.

    The real issue which AI will not easily understand is that LMS predates the significant level of adoption of MusicBrainz as a source of authoritative tagging. The way LMS and MusicBrainz handle contributors and is not quite aligned. When MBID's were introduced to LMS this difference was not well understood or factored IMHO (and for plenty of folks it is still not well understood).

    There is a simple script work around that is used by most LMS Picard users to replace ARTIST/ALBUMARTIST with the values from ARTISTS/ALBUMARTISTS. The issue is there are a growing number of LMS users now that use other software which relies on both tags from Picard and don't want to use that script. If you can use the script, that will be your easiest interim solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions