thanks a lot for your research. There is a simple reason why one of the composition names are in german in my example: I have maintained the WORK tag in german and Roon seems to first pick the WORK tag and then obviously tries to match to an existing record for the composer.
So when you change the composer this match can’t happen.
At least that’s my explanation for it. Having said that, I think that there is a little bit too much “wizardry” at work here and I’m not sure it’s for the best.
I do understand the strategy behind it, but I also beg the Roon team to understand the position of users who have groomed their collection with custom tags and now come into an environment where the system applies its own rules… For my collection of about 8000 albums, a quarter is not identified. But all albums have WORK, PART and COMPOSER tags properly maintained. Since it’s not possible to switch off Roons identification algorithm I end up with data inconsistencies I did not have before. And even with un-identified albums I’m ending with a mix of my tags vs. Roons.
I know that you can do composition merging, but honestly: why should I do that for more than a quarter of my collection (considering that even the identified albums will have some errors) if I have already spent years to maintain my tags???
Why not give the user the freedom to decide like with the preference of album tags and others? I’d really like to set “prefer file” for WORK and PART and switch off the magic. Let the users who want it or buy into Roon for exactly this reason have it but give us some control about it.
Additionally the whole Roon metadata environment is based on the assumption that we are all english speaking and reading… Maybe I’d prefer to have my artist biographies and work descriptions in german, french or spanish? Now I have a strange mix of my german tags together with english ones that I often not like :).
Thanks for thinking about it!