Thanks for the update.
I frankly wouldn’t have expected modifications external to Roon to affect my library. In my mind, my Roon library is the source of truth and should only change when I add or remove albums from Roon itself.
I would appreciate it if in the future we’d at least have an option to have Roon operate as the source of truth.
That would be asking the impossible, with a “rented library” over which you have little or no control.
On the contrary, this is quite possible, and probably not very difficult. I suspect you’re confusing two different concepts: what albums I have chosen to include in my library (I want Roon to be the source of truth for this, past the original import of favourites from a streaming service) vs. what albums are available to play (where the streaming service is obviously the source of truth).
In other words, past the original import, I don’t want alterations to my favourites in the streaming service done outside of Roon (be they voluntary or caused by a service outage) to be reflected into my library, unless I explicitly tell Roon to go and resync itself.
Nothing impossible about this, and in fact quite easy to do.
But therein lies the problem, Roon does not hold the masterdata for albums supplied from a steaming service.
The only way i could see that happening is by decommissioning the regular sync with Qobuz catalogue, and i’m “sure” everyone would be very pleased with that… 
You want the cake and eat it too, i dont see this happening.
It not straightforward as you suggest since Qobuz’ library is continually changing with different versions of the same release coming and going. Whilst Roon has metadata for your library, that will change, and the actual “media” is outside Roon.
Moreover, you may add or remove releases from your library using either Roon or the Qobuz app. And then there’s licensing requirements etc.
Consequently, Roon needs to regularly sync the library.
However, as already pointed out, your library content remains in the database, so long as you do not perform a library cleanup.
That’s an unrealistic expectation as explained. The alternative is to buy not rent your music.
I’m not interested in this functionality, I don’t want to manage by library through Qobuz, I only want to manage it through Roon.
As a programmer, I seriously fail to understand what’s so difficult in not relying on the list of favourites from Qobuz and instead having a separate list locally. What albums are available, sure, that needs to be brought in from Qobuz. What albums I want to see in my Roon library, past the initial import when connecting the account should be decoupled by what Qobuz considers to be my favourites.
It’s not impossible, it doesn’t look difficult (although, never judge what’s difficult in a given code base without seeing the code), and it’s something that, as I said, I’m interested in. As an option. So, if you want to be able to manage your library through Qobuz and have the changes reflected in Roon, that’s not going to affect you if it ever gets done.
Yeah, but you’re not the only one using Roon.
'xactly!
Roon continually updates metadata. Qobuz changes metadata, adds tracks, for example, when teaser tracks are available prior to release, corrects errors etc. Nothing is cast in stone. Sync is essential. How would you get new releases in your library?
It has nothing to do with programming. It’s about usability and design choices.
Which is why I’m asking it as an OPTION. An option that can be off by default, so that everybody can keep the current behaviour if it’s what they want.
So, there are two quite different things that need not be managed the same way. The Qobuz catalog is, of course (I think I’ve already said it myself at least twice), owned by Qobuz and needs to be synced. I’ve never proposed otherwise.
The Qobuz favourites are a separate concept. Roon can have its own list of albums I want to see in my library that doesn’t sync with Qobuz favourites, or only syncs on demand. Roon can stop syncing my favourites without stopping to sync Qobuz catalog, as those are two things quite separate from each other.
It has been suggested that what I ask is impossible or not straightforward, to which I was replying that it’s neither of those things. The usability question is a different matter. If you want to go there, I’d like to hear why you think having the list of favourites be local, optionally, for users who opt in, would be a usability problem.
Personally, that’s something I trusted Roon to do for me, and yet it doesn’t, which has led to the failure mode we experienced here. So, is it a (software) design choice? Of course. But was it a sound design choice? Arguable.
Anyway, I think I conveyed my request to the team for consideration.
Technical support don’t make decisions on the products direction, for that it’s Roon’s product management team.
I’ve split out this discussion to Feedback > Feature Suggestions where they will see it. However, be aware they rarely comment.
Thank you. I thought the support team would forward this kind of requests internally, but I’ll keep in mind to post feature requests in the dedicated section for the future.
Because your library is already local, but for streaming, the media is not. Synchronisation checks for deletions and additions on Qobuz.
Disconnect the service and the albums persist in your library, but are neither playable nor visible—at one time it wasn’t like this, but I suspect legal reasons dictate that synchronisation must occur.
So, I think your proposal to separate parts of synchronisation is unworkable and impractical. How would additions or deletions be handled, even if you never use the native app?
Anyway, if this is important to you, add your vote.
With a slight twist, i kinda like the idea though. Stay with me, while i elaborate.
If Roon was the solid master library for our music, one could actually consider building it based on artist, album, release (and/or track) and make the coupling to your streaming service loose, and drop the hard connection to unique releases.
This would also benefit the issues with releases being replaced at the streaming services.
I still think it’s a major architectural shift, and no quick fix though.
And labels and streaming services really need to fix the media, and label it better and connect each release to either a certificate or some other proof of it’s pedigree and that it’s “unfettled” and “as the artist intended”.
Actually something that MQA promised but never delivered…