Qobuz favorites missing from Roon Library after resync on Roon Titan (ref#CQC7BF)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· My Qobuz favorites disappeared from the Roon Library. I know this happened several years ago and was attributed to the way Qobuz was syncing with Roon, but it happened to me yesterday. I can see if them I click on My Qobuz, but they are only in the order of the date I added them, regardless of how I have Qobuz set on my PC (I use a Roon Titan to stream/play local files). I've tried resyncing Qobuz on my Titan, but that doesn't help. Is this the same issue as before or, is it a new one? If the latter, any idea when it will be fixed?

Tell us about your home network

· Xfinity router (model unknown) connected via ethernet CAT 8 to my Titan.

It seems to be slowly correcting the issue on its own.

Hey @John_Oster,

Thanks for writing in and sharing your report! I’m glad to hear your Qobuz library is auto-correcting on its own.

Our development team is also taking a closer look into these reports as well, as we still have some lingering Qobuz-related issues that we’re working on actively alongside Qobuz.

Let us know if things on your end fully correct, or if you continue to have issues over the next day or so. :folded_hands:

Hey @John_Oster,

Just checking in on this, since our last note mentioned that your Qobuz library was correcting itself and that our team is still looking into the lingering Qobuz-related reports with Qobuz. Have you seen everything settle down on your side over the past day or so, or are you still running into any of the same issues? If it is still acting up, let us know what you are seeing and we can keep digging.

Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.