[scott967]

I think both issues are examples of the problem of "song artist" being different from "artist". I think two things are going on. First is what you are using as an artist "separator" in Kodi and also in Piccard. Second is that when your song file is scanned, the scrape will use the MBIDs it finds and create a new artist entry for each, using as the artist name whatever is the preferred name from MusicBrainz (because you use the "override tag "option). But the music library (database) also stores a different entry for "song artist" and this one does not go through the scraping or override process. So when you open a view that shows the "song artist" you see the song artist entry, not the artist entry. I don't know why it works this way, other than attempt to accommodate a join phrase of "feat." in addition to the normal separator.

scott s.
.

[mhdebokx]

I have been testing around.
There is no difference between ID3v2.3 and ID3v2.4 tags (with the correct seperator in the Advanced settings and the Picard config).

Set the Kodi Music setting "Download additional info during updates" OFF. So first scan your complete music collection, and the Kodi music database is filled with the info from the ID3 tags.

Set the Kodi Music setting "Override song tags with online information" ON. Browse to the music Library, go to the Artists view, select context menu, and then do the action "Query info" for all artists. Do the same action for Abums: "Query info for all albums" .

In both cases use the Universal scraper. Now all MBID's are available and the database song titles, album titles and artist information is updates from the MusicBrainz database.

When playing the music, and show the full music window, the artist information is almost correct. Now first is the Albumartist shown and then the Artist tag. This is also valid info for the Artist Slideshow addon, because the first element (the Albumartist) is seperated by a dash "/".

See the result I'm happy now

[scott967]

Have to admit I've never experimented like that. Will have to play around and see if I can figure out what that process does.

scott s.
.

[steve1977]

Thanks. I am facing the same issue and the solution of scanning twice (with online override OFF and then OFF) does not appear to be sustainable to me. Is there a way in advancedsettings to disable Kodi reading any MBIDs from the tags? I believe this is the main issue and leads to duplicate display of albumartists and artists with the same name. Thanks in advance!

[TomFreeloader]

Now, after all this time, I know the reason WHY! Thank you for sharing that helta and others.
I don't know how it was I wound up on this thread, today? But a year ago, around this time, I REALLY could have used this post because of a few annoying multi-disc sets I had that looked like the same album. I remember trying Picard MusicBrainz with all three OS'es and either all three version hated me or I was too stooooopid to use Picard correctly. Even iTunes didn't work and mp3info told me that the v1 tag was missing. I don't know much about audio tags, but you know how I solved it? Amarok for Linux under the KDE desktop. It has a built in semi-interactive interface for dealing with MusicBrainz and tagging. Also by default does the v2.4 tags. Just wanted to put this info on here in the event that anyone else might find it useful.

[wpbpete]

Now, after all this time, I know the reason WHY! Thank you for sharing that helta and others.
I don't know how it was I wound up on this thread, today? But a year ago, around this time, I REALLY could have used this post

Sticky