SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Incorrect MBID assignment

#1

Yesterday I ran a few albums through SongKong, including this one:
https://music.apple.com/us/album/if-im-being-honest/6785619524 by https://music.apple.com/us/artist/malia/1145302173

The correct artist in musicbrainz is:
https://musicbrainz.org/artist/3ca8d046-4aa1-4304-8601-e73f324c5265 and the release does not currently exist in MusicBrainz, yet, SK suggests the following:

image
image2385×147 69.2 KB

which is this namesake:
https://musicbrainz.org/artist/888dbdc7-fbaa-4ea0-818a-b2cf8708e1c5

and the underlying tags in the files are as follows:
image

I’m curious to understand how SK handles namesakes when a release is not present in MB. Here’s the list of possibilities in MB:

image
image3354×352 61.5 KB

#2

When we get to save stage if we have songs that have failed to match to MusicBrainz or Discogs but have artist/albumartist metadata we do a search on the Albunack Artist index. If we get a single case-insensitive exact match then we update the artist fields.

However, in this case there are multiple artists with name Malia not just one so looking at the code it should not attempt match. Could you upload the album with me, if I can replicate the issue it is easier for me to work out what is going on.

#3

pw is SongK0ng_, check your PM.

#4

Sorry I can’t get password to work I tried both

SongK0ng_,

and

SongK0ng_

#5

I see now that discourse is stripping the leading underscore, so it’s got a leading underscore and two trailing underscores.

#6

okay got it, thanks.

#7

Okay found issue there was a flaw in my logic, now fixed for next release so that in this case would not attempt to add MusicBrainz Artist Id and MusicBrainz Release Artist Id as their are multiple artists with same case-insensitive name in the MusicBrainz database.

#8

Great, how does it handle namesakes when MusicBrainz Artist Id and MusicBrainz Release Artist Id are already populated in tags, but SK doesn’t know the album because it’s not in MusicBrainz?

#9

Had a look at the code, currently it tries to find a match unless MB Artist Id or MB Release Artist Id is included in the Never modify or add these fields or Only modify if these fields if empty options and so could overwrite existing value, and also the Artist sorts fields can be updated as well.

But seeing as with the fix I have done it would only update value if there was only one artist name that matched it seems unlikely it could update with wrong match.

#10

Will test as soon as it’s released. Tagging is a complex undertaking with so many combinations and permutations of what’s out in the wild. Glad I picked this one up, its implications would not be pretty across a large library containing many namesakes where releases are not present in MB.

I think I’ll create a few synthetic albums for this to test different scenarios. SK has become central to where I’m headed with metadata enrichment.