[dgas]

I have issues with many MusicBrainz artist IDs showing up in artist lists.  From looking around the forums, I gather that the scanner attempts to match up the MusicBrainz artist IDs to the album artist tags, and if it fails to do so, uses the MBIDs as artist names.  Here is my problem.  While I retain all MBIDs written by Picard, I will edit my artist and album artist tags to suit my own needs and preferences.  I believe that's where things are running afoul.  I'd like to disable this artist "fall back" behavior.  I have all the library settings set to local metadata only, and I don't intend to use any online metadata.  So, I don't need the artist MBIDs for that purpose.

Alternatively, I'd like to know if there's a way to tell the scanner to ignore all the MBID tags.  I'd prefer keep the release MBIDs for the sake of release merging and splitting, but the artist IDs are such a problem, that I'd give this a try.

[DaveBlake]

You are seeing MusicBrainz artist IDs showing up in artist lists because you have manually edited the ARTIST, ARTISTS, ALBUMARTIST and ALBUMARTISTS tag values but not edited the corresponding MUSICBRAINZ_ARTISTID and MUSICBRAINZ_ALBUMARTISTID to match. My advise is either to not add Musicbrainz ID tags at all, or if you feel you have to edit artist values then also take care to edit the mbid values to match.

BTW scraping metadata and artwork online is not the only reason to used mbids, it also provides a way to handle multiple releases of an album (say a basic and deluxe edition) or different individual artists with the same name (name is not unique). Have have a mix of music files tagged with and without mbids in my music library (mostly because of my tagging history), Musicbrainz is not mandatory but can be useful.

Kodi is designed to use Musicbrainz ID values when they are present and assumes that if a file has some Musicbrainz ID values then it has a complete set and that they match the other tag values consistently.  There is no option to ignore them.

I will edit my artist and album artist tags to suit my own needs and preferences.

My guess is that mostly you are removing artists, but not removing the matching artist mbid value. Kodi still knows about that artists from the mbid but not the name. If you start to use different artists and don't change the mbid values too then things will get very knotted indeed. Do you really need to edit what Picard does? If you do then edit the mbid values too.

[dgas]

You are seeing MusicBrainz artist IDs showing up in artist lists because you have manually edited the ARTIST, ARTISTS, ALBUMARTIST and ALBUMARTISTS tag values but not edited the corresponding MUSICBRAINZ_ARTISTID and MUSICBRAINZ_ALBUMARTISTID to match. My advise is either to not add Musicbrainz ID tags at all, or if you feel you have to edit artist values then also take care to edit the mbid values to match.

Yes, this is what I figured out on my own.  I'm not going to remove the MBIDs, because they are still useful to me.  It's not that I'm changing the artists to different artists, I'm just removing aritsts that I don't find useful in the artist tags.  I still want the artist MBIDs in my tags, just not in Kodi.
 

BTW scraping metadata and artwork online is not the only reason to used mbids, it also provides a way to handle multiple releases of an album (say a basic and deluxe edition) or different individual artists with the same name (name is not unique). Have have a mix of music files tagged with and without mbids in my music library (mostly because of my tagging history), Musicbrainz is not mandatory but can be useful.

Yes, as I said, I still would like the release MBIDs for release merging/splitting.  I don't have a need for same with the artist MBIDs.
 

Kodi is designed to use Musicbrainz ID values when they are present and assumes that if a file has some Musicbrainz ID values then it has a complete set and that they match the other tag values consistently. There is no option to ignore them.

In my opinion, that's not a same assumption to make, but I understand the default behavior, and I won't call it a bug.  I think there's an opportunity for improvement, however.  Anyway, barring that, I was asking if there is some general way to ignore selected tags.  Where I could list certain tags for the scanner to ignore, be they MBIDs or anything else I could care to exclude form the Kodi DB.

[DaveBlake]

Kodi is designed to use Musicbrainz ID values when they are present and assumes that if a file has some Musicbrainz ID values then it has a complete set and that they match the other tag values consistently. There is no option to ignore them.

In my opinion, that's not a same assumption to make, but I understand the default behavior, and I won't call it a bug.  I think there's an opportunity for improvement, however.  Anyway, barring that, I was asking if there is some general way to ignore selected tags.  Where I could list certain tags for the scanner to ignore, be they MBIDs or anything else I could care to exclude form the Kodi DB.

There are plenty of possible areas of Kodi to improve and lots of innovations to make, and frankly I don't think anyone cares whether YOU call it a bug or not that Kodi is reading and applying the tag values from your music files.

Anyway as I said - no there is no way to tell Kodi to ignore certain tags.

Since you are manually editing your tagging the power is completely in your own hands to resolve your own problem. When you edit the
ARTIST, ARTISTS, ALBUMARTIST and ALBUMARTISTS tag values and remove an artist also edit the corresponding MUSICBRAINZ_ARTISTID and MUSICBRAINZ_ALBUMARTISTID values to remove the matching mbid value. I am not saying remove the Musicbrainz tags, but edit your tag values in a consistent way.

[dgas]

There are plenty of possible areas of Kodi to improve and lots of innovations to make, and frankly I don't think anyone cares whether YOU call it a bug or not that Kodi is reading and applying the tag values from your music files.

Clearly, I left the wrong impression with those comments.  I was trying to say that I agree with how it currently works by default, and offering ideas that could add some flexibility.
 

Anyway as I said - no there is no way to tell Kodi to ignore certain tags.

Apologies, I interpreted your earlier response as saying there was no way to ignore MBID tags, specifically (as in, not some global "Ignore MusicBrainz ID tags" option).

Since you are manually editing your tagging the power is completely in your own hands to resolve your own problem. When you edit the
ARTIST, ARTISTS, ALBUMARTIST and ALBUMARTISTS tag values and remove an artist also edit the corresponding MUSICBRAINZ_ARTISTID and MUSICBRAINZ_ALBUMARTISTID values to remove the matching mbid value. I am not saying remove the Musicbrainz tags, but edit your tag values in a consistent way.

Yes, I understand. As I tried to explain, the MBID tags for the artists that I remove from ARTISTS and ALBUMARTISTS are still useful to me. Clearly, there is no nothing to be done at this time. Thanks, anyway.

[DaveBlake]

@dgas over 6 years I have probably seen 1 or 2 users ask about making which tags are scanned optional in some way, each had some specific reason with their music files, but I don't think it is a good idea generally. The problem comes with library updates and rescanning - what set of parameters were used to scan which files? Do users want these files scanned with X read but those other files with it ignored? We could solve that by storing tag option "sets" and which were used for the song etc. , but it just gets more and more complex for something that 99.9% of users do not need. There would also be those users that turned off a tag, and then later wonder why they can't see or use certain library features.

Hence the simple approach: if Kodi can read tag data from a music file then it will try to use it, tag your music files consistenly and fully (and there are plenty of great free tools to help users do that in ways that suit them and their needs).

As I tried to explain, the MBID tags for the artists that I remove from ARTISTS and ALBUMARTISTS are still useful to me.

Can you explain more, I'm always curious about user needs and how they use Kodi (even if I'm not going to implement anything). How can keeping an extraneous mbid tag frame value be useful in any way?

Let's make an example, say using Picard to tag a collaboration album has resulted in the following tag values.

ARTIST = "artistA and artistB feat. artistX"
ARTISTS = "artistA", "artistB", "artistX"
ALBUMARTIST = "artistA and artistB"
ALBUMARTISTS = "artistA", "artistB"
MUSICBRAINZ_ARTISTID = "mbidA", "mbidB", "mbidX"
MUSICBRAINZ_ALBUMARTISTID = "mbidA", "mbidB"

You then edit ARTIST, ARTISTS, ALBUMARTIST and ALBUMARTISTS removing "artistB", but eave value "mbidB" in MUSICBRAINZ_ARTISTID and MUSICBRAINZ_ALBUMARTISTID? Kodi sees the 3 mbid values, but only has 2 artist names so knows that something is inconsistent about your tagging and so adds an artist with mbid as name to make it obvious there is an inconsistency that needs to be fixed.

I am suggesting that if you have edited such that
ARTIST = "artistA feat. artistX"
ARTISTS = "artistA", "artistX"
ALBUMARTIST = "artistA"
ALBUMARTISTS = "artistA"

Then you also edit
MUSICBRAINZ_ARTISTID = "mbidA", "mbidX"
MUSICBRAINZ_ALBUMARTISTID = "mbidA"

Perhaps you can give an example of why you want to remving the name but leave the mbid.

[dgas]

The problem comes with library updates and rescanning - what set of parameters were used to scan which files? Do users want these files scanned with X read but those other files with it ignored? We could solve that by storing tag option "sets" and which were used for the song etc. , but it just gets more and more complex for something that 99.9% of users do not need. There would also be those users that turned off a tag, and then later wonder why they can't see or use certain library features.

I wouldn't advocate for anything like that, either.  I think you're talking about a per-source option.  The only thing I had in mind was a global option (likely with an edit to advancedsettings.xml) that would apply going forward, and one would usually be expected to scan from scratch after such a change.  Nothing about that addresses your last concern, of course.
 

Can you explain more, I'm always curious about user needs and how they use Kodi (even if I'm not going to implement anything). How can keeping an extraneous mbid
tag frame value be useful in any way?

Most importantly, my custom tagging tools use them for MB API lookups.  I may not use these artists for ARTISTS and ALBUMARTISTS, but I may want them for PERFORMER, COMPOSER, CONDUCTOR, ARRANGER, etc.  Having the IDs present means means name and sort name can be grabbed from the API and used for other purposes.  I also use them for things like the Run services component in foobar2000.