Anybody else experiencing an issue where Qobuz playlists and favourites aren’t updating into Roon? …I’ve reconnected Qobuz in Roon, restarted Roon generally, still the same.
A bit of chatter that it may be an issue Roon are aware of and working on with Qobuz, but if so it doesn’t build confidence in Roons ability to test their software prior to releasing it.
Qobuz connect working fine, and (heresy) I do think there is a sonic improvement from using it. Won’t replace Roon for me, as I’ve so much stored locally, so those guys need to get their act together.
Checking the Roon community forum Roon are saying that the problem is caused by changes made by Qobuz to the API. Roon engineers are working on this and the solution should form part of the next Roon update. It isn’t really a failure to verify on their part as the issue has not been caused by them.
So I am afraid that there seems nothing that can be done at the dCS end of things and you will need to await Roon’s update. I the meantime you should be able to play your playlists and favourites using Qobuz Connect or Mosaic but I think that you are already ware of this.
Probably about a week ago. Had another incident yesterday…more troubling.
One of my big playlists has tracks consistently added to it over the period - in an effort to resolve these tracks being visible in Qobuz, but not in Roon, i removed the qobuz connector and re-added it.
This made no difference to the tracks being visible, but did have the unexpected consequence of the playlist reverting back to a previous version (around a week old) which i presume was done by the relatively new Roon functionality of flowing changes made to a Qobuz playlist in the Roon App back into the Roon playlist, as Roon was holding what it thought was the latest version of the Playlist and considering that it was the master copy, and overwriting what was ACTUALLY the master copy (the Qobuz copy!)
…upshot, i lost around 50 tracks from a playlist. Fortunately i had a back up copy so could add them back in, but there is definitely some unexpected consequnces type stuff happening here!
Sounds like the same problem that is hitting Airable on their new API which isn’t used by Mosaic but is used by Mosaic ACTUS … there was an issue that has been in place since Wednesday last week and our information is that it is being sorted out but it isn’t a dCS or (I presume) a Roon issue.
Absolutely nothing! …i think there is definitely something screwy going on in Qobuz/Roon and the API between them… We are still some way from these services being utility (like dialtone used to be!) but we learn to live with it and it keeps life (kinda) interesting!
Interesting that dCS are seeing this manefest in Actus but not Mosaic… Can we take a moment to feel superior to the Actus users out there??
Can’t see my favourite Tidal tracks in Mosaic for some time now and my favourite qobuz tracks in Roon for about a week. Must be patient. Just be patient.
I am not sure from your post if you are saying that the test fix from Roon linked in the earlier post from @Ermos does not work for you or if you haven’t tried it and are awaiting the final version?
The test has only been available for a week. Tests ( beta versions) need time to be adopted and represent a realistic sample and tor the issuer to analyse respones from users and, if necessary make amendments.
I appreciate that this must be frustrating for you but the time frame of a week so far is pretty brief for this kind of thing.
I guess I ned to emphasise for the record that the cause of this issue is not related to dCS but to Roon and/or Qobuz.
