Roon 1.7 / 537 Working?

A post was split to a new topic: Issue with the queue on latest update

I don’t understand why some have these nagging issues and others do not. I didn’t have any issues with the 536 or 537 updates and am grateful for that but also worried about the possibility of it happening.

1 Like

Very happy with my Sonic.

Working on a system with Sonos and Bluesound devices.

I can confirm this is happening to me as well. It seems like a bug to me. Very annoying.

1 Like

Consider how many different configurations exist among the entire user base. There are hundreds of different computers, with all sorts of graphics cards, versions of different OS’s, etc. Then you have all the different sorts of networking configurations people have and a heavy need to draw from them. On top of this you get many/most of the user base all upgrading at once. Any corruptions of an individual configuration/database can goof them up and it’s going to show up after the upgrade.
So it’s something of a minefield and not surprising problems arise. Then of course, you can’t go back to what was a stable previous version of Roon. So I can understand the trepidation.
The good news is a lot of these upgrades are things being done to more universally render pages. They are also doing things to speed up processing/networking efficiencies. It looks like a march to a more stable place, but some folks are going to get dinged along the way.

1 Like

Back in my Cable TV days we assumed 2% of all set top boxes updated would trigger a service call. That was despite extensive testing by staff.

A post was split to a new topic: Android app connection issue on update

Updated this morning. No problems at all (which was a relief after reading a lot of horror stories on here). Core on a 2018 i5 Mac Mini, remote on 2018 13" MacBook Pro.

Yep, constantly disconnects here. Even my core constantly disconnects from my endpoints (chromecasts).

How do I roll back?

Can’t. Roon doesn’t support falling off releases.

Strange question! Of course, it does.

If you are having issues you should post in support. Roll back achieves nothing as you are stuck there as everyone else moves on. Fixing the problem improves Roon for all

1 Like

I’m not goîng to roll back because I can’t.

I understand you pointing me towards posting a support thread but I believe general threads like this one are more useful.

They keep bug reports together so support can just follow the thread and investigate.

1 Like

I can confirm that. Another bug, it seems, in this build, I’d like to see that fixed too.

Marc

1 Like

If you are referring to this exchange -

The only way to fall off a release is to restore from a machine backup of both the Roon software and the associated Roon database. That will work for the Core machine, but not for an updated Remote or Endpoint device.

Without these things, there is no Roon way to revert back to a previous release, as Roon doesn’t make prior versions available once a new version has been put in the wild.

1 Like

5 posts were split to a new topic: Unable to Connect to Nucleus

A post was split to a new topic: Update not working for me

Yes, Mac Mini (late 2014), 10.14, USB DAC

Core on Windows 10: All is well. End points and android remote all connected without issue.