Another Update, Another Bunch of Problems

It’s time for some tough love. For years I’ve cringed when Roon offers up an update to their software. Almost ever time it breaks just as many thing as it fixes and the latest update is yet another in a long line of examples.

This latest update, as so many before it, breaks the iPhone app where the phone can’t find the server. I’ve tried all the tricks form the past. Restart the app. Power down the phone and restart it. Sometimes the phone can find the server, sometimes not. This has happened so many times over so many updates I want to cry. Eventually you’ll provide an update a week or two later that fixes it and I’ve gotten used to holding my breath waiting for you to figure out the bug and get it right.

Now all the icons that used to be in place are all set to a generic speaker. The Chromecast puck icon is gone. My iPhone icon is gone. On the phone there is not a name label under the icon and if all my icons are a generic speaker, I now can’t tell which zone I’m paying in. I went into settings and there is no way to fix this! Ugh!

Please, please, please, figure out what you’re doing with beta testing and make sure the stuff is ready for release. I love Roon, but I absolutely hate your updates. For way too long this has been par for the course. Very frustrating.

2 Likes

Agreed! It is not good that I dread software updates to the most expensive purchase/subscription that I have ever made.

Roon staff do not watch this thread, so you’re wasting your breath here - better vent in category FEEDBACK where they’ll at least skim over your gripes without responding!

Roon’s “development” has ultimately driven me away, although due to everlasting quirks in RAAT’s implementation.

Good luck…

@Steven_Hansen - I’ve moved the thread to Feedback so that the Roon Labs team will read it.

1 Like

This is not new that it happens in rare cases and it’s usually fixed by rebooting the server and restarting the apps

Clearly not widespread, so open a Support ticket to get it looked at

This points at it being an issue in your setup and probably unrelated to the update as such

None of this happened to anyone in Early Access so there is little to be done there

To add to what is said, don’t suffer in silence. Open a Support request–your last was in 2024.

I know, I know! I have such a complicated Roon environment: Server on Mac, Remotes on Mac and iPhone, playing on Wiim Pro….

Over the past 12 years, Roon is working 80% of the time. CLEARLY the 20% downtime must be my fault. Not enough GOLDEN TICKETS I suppose. :slightly_smiling_face:

1 Like

Thank you!

I rebooted the server once. I’ll do it again and I’ll try restarting the apps. Why it is necessary to do this is the question of the decade.

None have had this happen, yet two people here in this thread it has happened to. Early Access seems to be someone insulated from the real world. And curious how you are access to that specific stat?

I don’t know. My wild guess would be a cache issue, but who knows.

If you read the forum consistently (or search for it) you will find that there are always occasional (and rather rare) instances of this.

I didn’t say „none have had this happen“, I said that it’s not widespread.

People with the same symptoms tend to say “me too” if they come across a related thread. Nothing wrong with this as such. But if you take note of the large amounts of posts that are created in a short time if there is a widespread issue, I guess it is safe to say that this isn’t one.

If you have this often or it doesn’t go away with a reboot, I’d suggest opening a support ticket in Support > Get Help to get it investigated.

Early Access users have the same software as everyone else, just a few weeks earlier, and otherwise they are forum members/posters just like everyone else. How would this lead to isolation?

Early Access users tend to say something in Early Access if they experience a problem. Nobody did. (If Early Access users don’t say something if they experience a problem, it would be their fault, but I don’t see much that can be done about it. However, if you think you can do better than those who currently donate their own time, Early Access is open to everyone and every additional feedback would be appreciated)

1 Like

Nobody is saying that. But if you don’t give support the opportunity to investigate these 20% cases, it’s more difficult to find the cause and improve it. Only those who experience issues can do that. It wouldn’t help much if I, for one, opened a ticket to say, „I have no problem, please take a look“

Here’s my final post to this thread.

First off thanks for the discussions. Many people added to the conversation and I appreciate that.

For those of you who mentioned to let Support know about this or they can’t fix if. You need to know I joined the Roon family in 2018 when they still had lifetime subscriptions. Can’t thank you enough for that, Roon. Gonna celebrate a decade with Roon in a couple of years. Yeah!

So first of all, I used to get Support involved with these things when they happened. Time intensive and I learned that if I leave them alone, then knew what issues they had and would fix them soon enough. I don’t have the time to reach out to support with each of their update when they go bad, and sure enough they fix them in good time so I hold my breath and wait for the updates to come that fix all my problems.

Now, for the expert that knows that most Roon users don’t have issues. I’m not sure about how much inside knowledge you have about Roon user user statistics. Since I’ve had a few stats classes (hardest thing I tackled in grad school), I don’t have a lot of “confidence” in that data you are throwing out. Maybe, most users don’t have issues with Roon updates, and I have no way to verify how may Roon users have issues, but what I do know with my eight year of experience with Roon, is the updates make me hold my breath. Statistically, if one user over eight years, continually has issues with updates, then there is an issue. There could be a lot of reasons for that. Roon is a complicate congloermation of input and output devices. To be continued…

Some people run Roon on a Roon made device, Some use Roon Certified devices. Others use custom built devices running some form of NUC device, and me, I use a Synology NAS. I’m sure that makes it tough for the developers. But in the world of tough love, why should I care? I just want Roon to work. Tonight I restarted my server, and that fixed my issues with the zone icons. But I am still having issues with running things on my phone and there being a big delay from one song ending and the next song starting. All I as is for Roon to take their time with updates to make sure they are ready to go, or let your users know the things they need to do to restart things to reduce the issues. Bottom line, Love Roon, don’t love the updates. Good Bye.

Practical significance, maybe, but statistical significance, no.

The only takeaway here is this: those who are reluctant to seek support are less likely to get help and resolve their issue.

1 Like

this is a funny comment that I see all the time. I guarantee Roon staff read the threads. They also often respond.

Not often in Roon Software Discussion where this was originally

1 Like

You can’t because you don’t know.

Technical support only monitor Support. Roon staff read Feedback. Whilst they may dip into other discussions, this is not the norm.

The moderators regularly move posts to the correct category as is the case here.

1 Like

I highly doubt they don’t read it. You also see responses from Roon staff.