· Some tracks are not available in Qobuz, but not tagged that way in Roon and appear OK. For instance it's the case for ‘‘the kinks - you really got me’’ (from the journey part 1, isrc gb5kw2300167) ; not available in Qobuz, not marked as such in Roon More details and screens in the original thread https://community.roonlabs.com/t/how-to-stop-roon-deleting-qobuz-content/314915/9 (from 4th reply on)
Tell us about your home network
· No VPN, pure Orange (french main provider) router - setup 2 years ago, no change since
Hello @benjamin ,
Thanks for taking care of this issue… Unfortunatly, clearing the cache didn’t change a thing: I have the exact same behaviour
Please note I forgot to tell; but I’m using a NucleusOne and I’m located in France.
I believe it’ll be anyway difficult for Roon to be notified whenever Qobuz changes his tracks (and though I love Qobuz, I’m not sure they’re doing their best work on the matter)… I guess the easiest thing to do would be a control on request of the user (kid of what you have with the 'improve playlist feature - maybe integrate this option to the feature).
I’m right now in the process of replacing the missing tracks with correct versions…
Then, In Qobuz, I created a new playlist (tracks_to_correct, and I’m browsing my favorites + using the send to playlist in the Qobuz app)… Interestingly enough, the playlist in Roon shows the tracks as Unavailable, and the Improve feature does propose me new versions…
So; I guess just being able to have this control performed on request (or a re-set of the tag within the improve feature) would be very helpful
Also, it looks like the isrc didn’t change (I may have mistakenly given another Kinks track, but this is gb5kw2300166)
And Roon identified 13 out of 14 non-available, misssing Travis - Bus (from L.A.Times - Album not found in Roon)
Unfortunately, it’s very difficult to reproduce, and actually depends on Qobuz changing rights !
See below two screen copies, one from Qobuz, showing Sylvie Vartan’s tracks are not available, and one from Roon, with no special indication for Vartan’s tracks.
Note these I added 4 days ago only directly in Qobuz (they were ok at this time).
To be honest, this issue is probably caused by Qobuz, but Roon could remedy it and at least identify these tracks as unavailable.
If you look at this, you can see some clue that may help you spot the issue and offer a parade. I’ll be following this procedue this weekend (unless you tell me not too).
Hope it helps - thanks in advance for looking into this inconvenience.
BR
The fact that this issue started happening over the past few days brings a lot of clarity to the situation.
Here is a bit of technical background on what is happening behind the scenes:
Roon’s Database vs. Live Qobuz Data Roon does not pull a direct, live feed of your library from Qobuz. Instead, Roon maintains its own extensive database that mirrors Qobuz’s catalog but includes our own additional, rich metadata (like advanced credits, bios, and sorting capabilities).
The Synchronization Delay Because of this architecture, Roon’s database is not updated in real-time. It relies on periodic data syncs with Qobuz.
It can sometimes take several days to a week for Roon to fully process and reflect licensing or availability changes made on the streaming service's end.
What to Expect Next: Those specific tracks should automatically show as unavailable in Roon as well, just as soon as our system finishes pulling the latest catalog changes from Qobuz.
Would you like me to keep this support ticket open so you can confirm when the track status finally updates on your end?
Thank you @alex_h : this perfectly explains the issue. Feel free to close the case.
But then, 2 questions.
1/ How frequent is this synchronisation with Qobuz ? It would be helpful to see the last timestamp it occurred somewhere in the setting.
2/ Do you think it’s feasible to have a function to check for Qobuz’s availability in Roon ? It may come useful in case this synchronisation didn’t occur recently
Thanks again for your kind checks
That is a very logical request, but unfortunately, a simple “Last Sync” timestamp wouldn’t actually provide the clarity you are looking for.
Why a Timestamp Wouldn’t Help: Synchronization is not a linear, “all-at-once” process.
Non-Linear Updates: Two albums released on Qobuz on the same day might arrive in Roon at completely different times. One might appear in 24 hours, while the other might take a week depending on how the metadata is processed.
The Data Gap: A timestamp would only tell you when Roon last talked to Qobuz, not what content was included in that conversation. Seeing “Last Sync: 10 minutes ago” wouldn’t tell you if your specific album was in that batch.
Timeframes & Limitations:
Typical Lag: Updates usually reflect within 1 day to a few weeks. It is rare for it to take closer to a month.
No Direct Comparison: Roon knows what is currently in its own local database, but it cannot perform a real-time “diff” (comparison) against the entire Qobuz live catalog on demand.
The Long-Term Solution: Rather than building tools to monitor the delay, our engineering focus is on reducing the latency itself. Our goal is to make these updates happen so quickly that the need for a “check status” button disappears entirely.
