Thanks @Carl, I know and I have read every single post in this thread carefully, but the real answer still escapes me.
Being a curious man myself, and I am pretty sure that you know - so what is the root cause of this issue?
In the other post that I referenced from memory but couldn’t find again when writing this, they IIRC had said something along the lines of „we could fix it on the backend“ which really tells us not much. That’s why I wrote by one of the parties or together. Who cares, anyway. Could still be caused by a Qobuz API change that could be worked around on the Roon cloud, or whatever. Most likely these things are often not simple.
Ok, but I still feel that we don’t get transparency here.
However, some explanations may be acceptable.
Btw, is @danny still with Roon? He is very open minded, and technically very good,