@brian aliases: \o/ \o/
I am also not 100% sure that we are pulling all mbz credits at the moment.
If you mean: is the MB dataset in the Roon webservice? I do not think it is (this for example)
Also, track level relationships are rarely there as far as I can tell.
If you mean, “data out of files tagged by Picard”, there are some issues indeed. The most glaring one is probably that picard tags instruments performers as PERFORMER=Somebody (some instrument) which does not fly well into Roon, which expects PERSONNEL=Somebody - some instrument instead.
It is fairly easy to script this out and rewrite / convert all these tags, but if Roon could be smarter on the PERFORMERS tags, that would be awesome.
In my scenario, I maintain my metadata using MB + Picard (prefer file), and having an extra processing step before adding the files to Roon is a minor annoyance.
What I will probably do myself is write a tagger that relies on the Musicbrainz service and stuff tags in a way that works well with Roon.
I would love it of course if Roon was playing better with MB (read: use more of / only the MB dataset) - but then I understand why it’s complicated and that your core business is not “specialist” metadata.
Thanks for Roon by the way! This is a fantastic piece of software.