970 won’t install.
I’m on Synology 216+ II. I get the usual “an update is ready to be downloaded”. The update process runs normally (click here to install … Downloading… Installing… Click here to relaunch…) and when the core is back online, settings > about returns build 952 as if nothing happened.
Is there an install log that I check for errors?
This build, as with everything else in the last few months, is shockingly unreliable:
This is getting to the stage of Roon being unusable. Which, given that I’ve paid for a lifetime license, is fecking annoying.
There may be a fundamental lesson here, one that I’ve seen many companies fall flat on their faces over, many times: DO NOT USE A MICROSOFT FRAMEWORK FOR CROSS-PLATFORM DEVELOPMENT.
Core: M1 Mac Mini/OS X 12.4
Desktop Clients: M1 & Intel MacBook Pros/OS X 12.4
Mobile Clients: iOS 15.5
Other endpoints: 3xRaspberry Pi/DietPi/RoonBridge, 1x Roon Ready AVR
FWIW: Smooth sailing; installed with ease and works problem free.
FYI: Core on Ubuntu 20.04.4 LTS and clients on iPad, iPhone, appleTV and intel MAC
All fine on both setups for us - each on NUC 8i5 and ROCK, with various iOS based remotes (and one Win11 one).
Michael
Again a flawless update on my NUC10i7!
The fact that SOME users have problems does not necessarily mean that this is a bad release. For my part, I have no problems (so far) whatsoever with build 970; build 952 indeed had memory leaks which caused my Mac client(s) to become slow and/or crash. Not so with 970.
Core: Intel NUC7i7BNH
Clients: iMac i9, using MacOS Big Sur
iMac i5, High Sierra
MacBook Air M1, Monterey
iPad Pro 12.1" (2nd gen)
I’m actually very cheesed off with update 970. Ever since the update all my “Roon Ready” devices will not show. If I turn them off and on again they’ll stay up for about 30 seconds before disappearing again.
Given my Soundaware D300REF is a rather expensive unit aim seething at having to use its USB interface via the media PC which sounds nowhere near as good. The same deal with my Soundaware A1X.
I’m an active member over on Stereonet and it seems other members are experiencing the same issues with their dCS and other gear. Please sort this out as a matter of priority l.
Well, my dCS Rossini is rock-solid on my installation of Roon; so no generalisations please.
It’s not a generalisation, merely that a Stereonet member running a dCS “Roon Ready” device is experiencing exactly the same problems I am. There are other members with devices I can’t recall with the same issues. It’s a statement of fact, I did not state ALL users.
The fact that it does not affect ALL users (let alone all dCS users) implies that Roon quite possibly don’t see that problem in their labs; therefore, to get this solved affected users should open up individual support tickets. Otherwise, no chance that this gets resolved any time soon.
If you’re experiencing problems specific to your set up, please open a support thread.
There really aught to be a rollback function given the oftentimes unreliability of updates.
So, how do you start a support thread?
Go to the top of this Roon community, click “New Topic”, select category “Support”.
As @Paul_Bemelmans states, but don’t forget to fill in all system details, including network set up,
Exactly… sigh!
Support thread created
I started having troubles with both qobuz and tidal last nitght. I logged out and back in to both. I rebooted this morning. Not sure if it’s fixed or not, but so far so good. I’m not a big fan of needing to perform a bunch of rituals every time I install a new version.
I totally agree with this. I get that they don’t want to go “backward” but when an update renders the service/app unusable for a swath of users, I can’t see how letting users temporarily roll back is worse than a bunch of apoplectic posts on the support site.
In Roon’s defense (or maybe its fatal flaw), it must be a nightmare trying to develop for and support countless platforms and installation scenarios. Web development is one thing, but this must be hell. But, they better figure it out quick!
It would be really interesting to see exactly what type of Core people are using with these issues. Like, did 952 affect mostly folks with Mac OS cores? And then now 970 is affecting ROCK/NUCs?
For what it’s worth, my core is on a 2012 Mac Mini. I had countless issues with 952. None with 970.
I have rock and last build affected me just the same and had issue with all remotes on Andorid and Windows and iOs. This version so far not one problem other than ones that have been around for ages and not been sorted.