Since suffering from multple of such issues Mike informed me about roon has choosen allmusic and musicbrainz. And I was adivced to read kb articles which I did this morning.
Found some limited info about UPC and I’m aware Product Code in the settings might be the intersting one for deeper investigation.
Lets try to find out at which stage the misery arises from. Could be me, roon or even the metadata service provider, let’s see.
Quick test using one artist/album roon failed, better said provided completely wrong information
9399603025222 (GTIN number, eg. a pretty unique number you could scan from the tray using a smartphone if you fancy)
open up a web browser, and try some metadata providers asking what they do return if being queried with that number.
allmusic … nothing. I already wonder they are still alive. from being the best they turned into final follower.
musicbrainz … had to provide additional info that I want to look for releases. 1 match 100% accurate. good.
discogs … the number on it’s own works, 100% match. They seem to have some AI implemented.
conclusion: it’s dead easy to get the correct entry from metadata service providers this way, which doesn’t impress me at all, such numbers were invented for that purpose, that simple.
The big point I’m after is something differnt in the end.
The linkage between artists and releases is quite good at the metadata providers, incl. allmusic. if you know which exact release you’re looking for the linked artist (even if 20 have an identical name) gets found nex to 100% accurate. This then means … bio, date,s location, artwork … all matches as expected.
Conclusion (back to my initial question who’s responsible for wrong info.
a) the metadata provider?
Definately not. All do serve correct release<->artist linkage even allmusic which is a bit more tricky to handle since not allow for such sinple queries such as a tradenumber.
b) me since just learning how roon works, and I might have either made a mistake in the settings for the import stage or missed the information about which name the import expects the metadataframe got which does hold the tradenumber information in the files embedded data.
c) less likely, since the programmers at roon surely have no spare time
Trade number/product codes were invented to ensure that global trading allows to identify each single product with 100% accuracy. Thus no need for re-inventing it. There surely must be some clever code in case no unique identifer is available, but that’s a differnt story on how to solve that.
Comments appreciated, especially since I still would vote that I did run into the conclusion b) issue.