It would be dead by now. That’s arguably simpler.
2 Likes
Much earlier 
1 Like
FWIW I think they are going as far as reasonably possible, but they can’t fix the code in other manufacturer’s devices. If the bug is not in Roon and they provided the extensive analysis results to Meridian like they said, I agree it’s up to the OEM.
1 Like
That’s absolutely right. And this is one RL consequence.
And for roon’s future it’s very important that third party manufacturers still believe that this technology is more than just nice to have.
Most Roon customers have no significant problems. I have none running three servers ((Dell XPS 15, upgraded Mac Mini (late 2014), and Nucleus)). If someone has chronic problems, it’s one (or more) of three issues, ie. hardware, software, network.
So, you can change your hardware, change your software, or change your network. If your network is not the problem and you like Roon, I would change the hardware to something that works.
And yes, Roon has changed over the past 7 years. So has everything else. What worked 7 years ago seldom works now.
Geoffrey Chaucer : “Time and Tide wait for no man”
2 Likes
That’s fine but I reiterate, if there is the possibility of an issue, the option to refuse the update or the ability to roll back must be given.
To be forced to update and then be told “your equipment’s got a bug in it, tough luck” is not on. If my system was stable I would refuse any subsequent updates on the basis that most of these [moderated] things appear to be designed not to improve Roon as such, just make it different or include more functions which some of us neither want nor need.
To draw an analogy, I use Photoshop CS6 because it does what I need it to do. I don’t want or need more and I have the option not to go further. Roon ought to give me the same!
4 Likes
It would be interesting to know where we are with the RAAT element of the endpoint that is dropping off the network. How old is the firmware?
I did. It refused to find my audio files and told me I had no permission to access my own NAS. At the same time, logging in via the usual shortcut worked perfectly well.
I understand the wish, but it would put an unsustainable burden on Roon in the same way as Microsoft won’t update Office 2003 anymore to keep up with changes in the environment. The required work would grow exponentially across all versions.
1 Like
1.1, build 235.
I’m sure how old that makes it. All I can say is I’ve not updated it since I bought it seven years ago because I’ve not found new firmware in all that time.
But if you want to use Office 2003 you can. I did until about a year ago. If, however, I want to use an old but stable version of Roon, I can’t.
I’m not so sure about that. There are still roon users running 1.8. If you want so, keep the roon install files.
But that’s only because it has little connection to the outside world. It won’t get bugfixes or security fixes, if it can’t read a file that someone sends you, then it just can’t and end-of. If it had any online component’s, it wouldn’t get updates for changes to those. If you want to integrate any third-party components (like add-ins) then it only works with those from 20 years ago. If the underlying OS changes and becomes incompatible, then that’s it.
I think they are up to and beyond 1.1 build 248. That build was around 12 months ago. I think you have to run Meridian Device manager on a PC on the same network and it will identify and auto update the 218. If there is still an issue then it is something else.
2 Likes
Unfortunately, the part of the Roon system that you download to run as your Server is only part of the ecosystem. There are also remote services feeding data to your Server, and both the locations and APIs of those servers also change. Roon has committed to keeping two sets of services for now, the 1.8 set and the current set, but that state of affairs may not last forever.
1 Like
I don’t know that device but if that’s the case then perhaps a temporary fix is a Ropieee endpoint that streams audio to the device?
1 Like
Actually, you had to choose to update. You were not forced to update. You always can elect to refuse an update and continue to do so for the foreseeable future.
AJ
6 Likes
I’ve used Audirvana Studio for 2 years before switching to Roon.
It’s a nice piece of software if you’re only using a single endpoint. Preferably connected straight to the computer that you are running Audirvana on.
However network connected equipment are a hit or miss. Audirvana supports UPnP and Chromecast. Which means my Cambridge CXN V2 worked, but my Bluesound Node X didn’t.
Also Audirvana not supporting multiple endpoints. A clunky interface. A remote app that really is just like a TV remote and no Roon ARC functionality really drove me towards Roon.
So much so that after 2 annual subscriptions I’ve went lifetime in late 2022.
I am using JRiver next to Roon. As it has far superior tagging options and it acts as server for my movies and shows.
3 Likes
And if you did it would be very unwise to do so, like most legacy, unsupported software. (security)
1 Like
It seems like a sensible solution would be to allow the rollback of one version. The rollback process could ask for a reason which could then add a trouble ticket to the system. This would at least give the Roon devs a version before a failure is permanent to fix any issues.
1 Like