What happens if you merge two different artists with the same name, though?
I mean, doesn’t that mean you might get bombarded with even more links to even more people, as Roon propagates your collection with information about artists, none of whom are in any way related to the music you’re listening to?
The same name appears twice, but it is the same artist. In this case, merge solve the problem.
The same name appears twice, but they are two different artists. For example, Avishai Cohen: there is a bass player and a trumpet player with the same name. In this case, I renamed them “Avishai Cohen (bassist)” and “Avishai Cohen (trumpeter)”.
These are metadata errors, and Roon doesn’t always catch them. I’ve got the two LSO entries as well. The first is the genuine LSO, the second is of a discography of some sort of weird “with some famous musician” collaborations. They probably should be merged.
The “Orchestra of St. Lukes” entries are subtly different (check the case of “of”). Probably also can be merged.
I generally report these sorts of metadata issues in the #support:metadata category for Roon Labs to be aware of.
Changing the subject slightly, I’m often surprised that Roon will automatically combine, say, a soloist, orchestra & conductor as a single entity, thus potentially creating a new artist in my artist list that may only appear once.
If I had a separate artist consisting of, say, “The Berlin Philharmonic Orchestra + A. N. Other conductor” for every combo that exists in my record library, I’d be forever scrolling through a swamp of BPOs.
As it is, I always search out the individual entities so that the BPO is only there once, as are each of the other soloists or performers involved.
It does make me wonder what other spurious links might be thrown up if the two you mention were merged. Would the “with some famous musician” become part of the “if you like this you might like that” section?