Why can't I stay with 1.6 if it is stable and I like it? Why I'm obliged to migrate to 1.7 if I don't want?

[Paolo_C]

@support Good morning,

After very bad audio quality experience after update to version 1.7 (I have openend a ticket in “support” one week ago and still waiting for help/reply) I got another SSD and installed again the version 1.6 as I still had the file I used in September for my first installation…

Everything worked fine and I got this result

Then I tried to lock the update to remain with the 1.6 using this option here

Unfortunately when I established a connection with the Core via web interface I got this bad surprise

With NO POSSIBILITY TO ACCESS THE MENU TO DISABLE UPDATE… why can’t I decide to stay with what I like? Why we are all obliged to accept it when for some of us the 1.6 was nice enough and stable? What are those UPDATE SETTINGS for if, in praxis, can’t be used to decide about?

Please reply (or, better, help!)
Thanks

[evand]

The answer is pretty simple. Roon is not solely comprised of the app on your desktop. It leverages cloud based infrastructure and functionality to do its thing. The front end and back end need to remain in sync for things to work.

[Paolo_C]

so if the day after tomorrow people in Roon decide to end the “cloud base infrastructure” we all remain with nothing? I mean… it will be even impossible to use the Core installed in my house with the software (music I mean) in my hdd because no cloud available service/connection? it is obvious the new A.I. can’t work if is not online… but why no use of what I have already scanned and results saved locally? … DSP is not cluod based but running locally, why can’t I use it if I’m offline, or they are offline, or I’m not updated? library is in my hdd and Tidal is another account/service… why can’t I use it? … just to better understand how this product/service works

[Martin_Webster]

so if the day after tomorrow people in Roon decide to end the “cloud base infrastructure” we all remain with nothing?

You’re subscribing to a service, so it’s no different to any other service provider in that regard.

[garym]

Roon requires an internet connection to “call home” at least once every 3 or 4 weeks. See below what they say would happen if Roon shuts down.

What happens with the lifetime subscribers if the company folds or is sold?

Yah, I get it. So right now, the application obviously logs in to our cloud services, for both metadata and membership checking. In the unlikely event that we could not maintain those services, we would release one last build that would kill those dependencies, so you could continue to use the application without our infrastructure as a requirement. Obviously the functionality would be reduced, but it would work.

[Paolo_C]

ok, that’s positive… I like it