I use Lyrion as my music server. It’s highly metadata aware and driven in terms of its UI, so the richer the metadata the more immersive the experience, and the richer the ways in which one can navigate your music collection. As a result whenever I tag music with multiple artists contributing on a track or collaborating on a jointly billed album I write each artist’s name as a distinct tag, like so:

I’m looking at the changes SK would make to my metadata.From what I see it would transform the above-mentioned into the following:
From the screenshot of the spreadsheet it’s clear that SK would replace my two distinct artist and albumartist tags and replace it with artist=“Aerosmith & YUNGBLUD” and albumartist=“Aerosmith & YUNGBLUD”. It’d do the same with 38 Special & Train, replacing artist=“38 Special” and artist=“Train” with artist=“38 Special & Train”.
This would cause Lyrion to create two new new contributors called “Aerosmith & YUNGBLUD” and “38 Special & Train” respectively. The end result of this is that I would not be able to navigate from Aerosmith & YUNGBLUD to either Aerosmith or YUNGBLUD and visa versa and that release will not appear under either artist, appearing only as a release by albumartist “Aerosmith & YUNGBLUD”.
The same would be the case with “38 Special & Train” - I would not be able to navigate to either entity from this track.
Not sure whether or not there’s an option I overlooked, but seeing as SK clearly knows in both instances that we are talking about distinct persons/performers/artists (the “MB Artist Id” and “MB Release Artist Id” carry multiple mbid’s where appropriate), is there an option to have SK delimit rather than combine the artist names .e.g “Aerosmith;YUNGBLUD” and “38 Special;Train” instead of “Aerosmith & YUNGBLUD” and “38 Special & Train” respectively?
Without that option SK would do more harm than good to how things show up in Lyrion (and probably most music servers that don’t to their own metadata mastering like a certain server that shall remain unnamed…).
I’ve not raised the differing representation of YUNGBLUD vs Yungblud because I raised it elsewhere when discussing canonical names.



