Agreed, hopefully learn from it 
Not sure that there is any 3rd party beta testing these day’s and it was never really long enough to gain any benefit from it.
Hopefully as the team build more automation into the build/test suite things will get better and build 952 will be more than an embarrassing footnote in the Roon history.
Let’s take it sportingly, each of us has missed a penalty kick and then still won the game.
So true. Roon needs a fallback plan to rectify this sort of situation quickly. But I also have a fallback plan, which is iTunes and my own lossless library of 2500 albums. It does highlight the fact that I can do pretty well for free.
Sheldon
… or one could just set Roon and one’s mobile devices to not auto update and hold out until the dust has settled …
True, but sometimes things happen that are not related to an update. For instance, your core machine might crash.
That’s what I did after having issues with 952. I tuned off auto updates in my Roon ROCK Core and all my remotes. I would not update any of them until reading the new version feedback thread.
BTW, this is the second release in the last 3 months having big issues. I think it was 918 that made disappear all Roon bridges for everyone….
Not everyone - the only problem after an update I ever had for the last 2 1/2 years is, that the remote closes on trying to open settings the regular way!
Definitely not everyone…
Yep, I understand people getting aggravated by things not working for them, but exaggerating for the sake of making their point more stringent without having proof just aggravates me…
This build happened along just as I’d finished putting together a new NUC 10 platform to host my ROCK installation. I’ve experienced remote freezing issues on Windows and Android, as well as an odd Roon Radio problem on iOS, Android, and Windows where after a few Radio-selected tracks the controller would go out of sync with what was actually playing.
I have not requested the special magic fairy dust that other users have received as a hot-fix, but strangely enough, after a few ROCK reboots in response to controller freezes, the problems have subsided…so far.
Roon is the frontend to my mulit-room Sonos system, and I have been mostly happy with it over the years, but I am experiencing update fatigue, particularly when the update breaks stuff that was working just fine, which creates the impression that I have a subscription to partially baked beta software.
I suspect many problems can be attributed to accommodating MacOS-iOS-Android-Windows platforms with one flavor of the Roon application.
It was 913 and it affected all Ropieee Bridges to the point that @spockfish had to bring back the Reinstall Roon Bridge option. So you are right, not all Roon Bridges, only those running Ropieee!!
Your lucky, last 4 have brought with it bugs for me two of which have been more impactful than others. It leaves a nasty taste in the mouth. All of the issues have been confirmed bugs. Everyone might not get affected by them but they are there. I think the way we all use Roon in different ways shows up some more than others in people’s environment. I only noticed this memory leak as I was doing a lot of editing of my library and it ate away at it very quickly going back and forth through album section then to each album edit, back and do next one. It ground to a halt and it’s done this on Andorid and Windows remotes. The more I use it the more sluggish it all becomes. Audio playback hasn’t been affected by this one until today when core just killed itself out of the blue. It all became snappier again after the reboot but it will go again if this isn’t fixed.
I think we should wait a couple of days.
I am back to JRiver and HDConnect atm. My fallback solution works satisfactory.
I retired Roon until the fix is ready. Simply too many crashes.
yeah, I think for the most part folks are trying to be patient or finding another source or temporary solution that works within their setup. For me, and obviously not ideal, I’ve been controlling Roon only from the NUC that the core is actually on - for the meantime, that seems to be working well enough. Just opening the controller on the IPAD can hose things up, and the phone controllers (Android and Apple) have been hit and miss.
If they are not careful this will lead to loss of customers for those on the pay and you go or coming to a new yearly sub. Having to revert to other software because of bad q&a when you pay a high sub for is not a a good customer relationship.
That’s how things got into this state, methinks. I’m knocking on wood that my radio streaming seems to be working OK.
