@Bozon , I certainly benefited from others help and advice. After getting my eight RPi Endpoints up and running with Trixie, I’m good to go.
Hopefully Roon will give more consideration to RoPieee, DietPi, and Volumio users in the future.
For those who opt for the DIY solution rather than using either Ropieee or a commercial streamer, the expectation is for a little tinkering and familiarity with the underlying OS.
3 Likes
Jeez, my system broken again within space of a few months.
First I come back from travel to find the whole setup down and have to spend ages messing about with OCLP to get a previously stable roon server setup running again.
Now, without warning, my dietpi zones just disappear and nothing works again.
Jeez, thanks Roon team!
Roon used to be so reliable, and the team seemed to actually care about their users and their system reliability. Seemingly now it’s just - BAM - here’s an update, new minimal requirements, sort yourself out if it doesnt work.
Doesn’t bode well for Roons longer-term success if this is the ‘new normal’ attitude..
Fortunately there are at least a few decent options now and the streamers apps are better in many respects, but still, as a long term lifetime user, this kind of sucks.
You choose to take an update or not. So, check here first if you are uncertain. Why would anyone blindly update every endpoint rather than one at a time? People have got to take some responsibility for their kit, too. That means running up-to-date software rather than milking old kit or software.
Fixing DietPi is straightforward and the steps were documented by the community promptly. If it is too much hassle then maybe run Ropieee is a more suitable alternative?
But let’s put this into context: How often is Roon Bridge updated? This really isn’t a big deal, and the benefits of running .NET 10 are worth a little pain.
1 Like
I understand where you are coming from regarding personal due diligence, but I don’t think it’s reasonable to place the burden of troubleshooting back onto the end user here.
Roon is a premium, consumer-facing product, and the expectation with any paid ecosystem is that software updates have been thoroughly vetted so they just work. While checking community forums and staggering endpoint updates makes sense for technically minded hobbyists, software vendors shouldn’t make the assumption that every customer has the skills, knowledge, or desire to pop open a terminal or diagnose broken dependencies.
The DietPi community deserves credit for documenting the fix so quickly, but having a simple workaround doesn’t excuse the fact that the update broke working endpoints in the first place. Whether someone runs DietPi, RoPieee, or off-the-shelf hardware, nobody should have to accept software breakage as the price of admission for a background framework update. End users buy into Roon for a seamless listening experience, and the vendor ultimately needs to take responsibility for delivering proven, stable releases that don’t rely on community triage to keep the music playing.
2 Likes
I generally agree with your conviction that commercial software must be supported on the platforms the software was intended to officially run on.
Roon encourages open source hardware, software, and DIY integration with their products.
After reading the following, it’s my understanding that supporting Raspberry PI Roon usage is best effort. It’s not an officially supported platform. Have I got this wrong?
I agree. But Roon also provides Roon Bridge and ROCK for those of us who choose to build a streamer or server. That flexibility gives us lots of freedom, and with this comes some personal responsibility. It seems improper to castigate Roon when one or two configurations get missed by their Devs and the EA testers.
If we want an out-of-the-box experience then we should buy a commercial streamer or a Nucleus. You can’t have your cake and eat it.
@mjw , by default Roon has updates set to “Automatically install all updates”. That’s why.
“Why would anyone blindly update every endpoint rather than one at a time?”? Perhaps because they trust Roon not to hose their Endpoints?
Take it easy on subscribers. They pay for well designed software…
1 Like
This personal responsibility involves reading the release notes and checking, wheter one’s system meets the minimum requirements and dependencies published by Roon.
Within hours after release, it has been demonstrated by the community, that the information published by Roon has been incomplete (missing out on the libicu depency) and wrong (minimum glibc version required on ARM-Systems, e.g. Raspberry Pi).
Yet within 3 days Roon still hasn’t managed to at least correct this information both in the forum posted release notes and the Help center to give users late to the party a chance to avoid the pitfalls created by Roon.
Plus: Roon hasn’t missed the differing minimum requirements for glibc. It’s actually in the install scripts written by Roon. They just missed out on publishing this information.
1 Like
But this net 10 update does not affect roon “ready” streamers right ? Let’s say a holo audio Red ?
No. Roon Ready and Roon Bridge are entirely different things, and Roon Ready assumes by design that streamers don’t always have simple ways to be updated. And RR is made for streamers with limited computing resources that usually can’t run large frameworks like .NET
2 Likes