Hoping Roon developers can chime in here…I’ve been reading (e.g., Roon on QNAP no longer showing up on my network - #2 by BlackJack ) that recent EA build have presented some challenges in running within the context of Roon on NAS. Is this being addressed in testing and development?
1 Like
on which OS?
Synology DSM 7.3
1 Like
Wasn’t the issue with EA B1643? 
You’re on 1644, so the devs may have fixed the issue.
They said, they had not yet in B1644 in this thread:
I am still on production build, running QTS 5.2.9
1 Like
Yes it was first in B1643 but there was nothing about it in the 1644 release notes. Edit: and of course the reply that @Arindal posted
1 Like
Understood. All I can assert at this point is that 1644 works on DSM. We all know that this doesn’t mean 1645 et. al. will work 
1 Like
It’s just a bit weird is all 
1 Like
Did anyone actually report an issue on Synology?
See here:
1 Like
Thanks.
I thought I would poke around a bit on this - I took a look at the Roon Labs git repos. I got sidetracked when I saw this:
It’s empty. It was created or updated yesterday.
I know I’m biased about this but I would love to see Roon focus on Docker images, instead of NAS packages, going forward. Maybe that’s what they’re up to.
3 Likes
We migrated several Roon pieces over to net10.0 which should bring a handful of immediate performance improvements as well as opening up opportunities for good future improvements.
However, this means that some newer dependencies are required because of net10.0 such as a newer glibc:
glibc 2.27 Arm64, x64 Ubuntu 18.04
glibc 2.35 Arm32 Ubuntu 22.04
For synology, I believe certain versions have newer versions of glibc.
For QNAP, They haven’t updated glibc in over 10 years. They have a beta version of QTuS 6.0 (beta 3) that does bump glibc. This is the hero line and since it is beta I’m not sure what their release timeline is or plans to release QTS 6.0 (non-hero). Also, I’m not sure what versions of their hardware will receive update to the 6.0 line.
2 Likes
On Synology DSM 7.3.2:
/lib/libc.so.6
reports:
GNU C Library (GNU libc) stable release version 2.36.
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 12.2.0.
libc ABIs: UNIQUE IFUNC ABSOLUTE
Minimum supported kernel: 3.2.0
For bug reporting instructions, please see:
<https://www.gnu.org/software/libc/bugs.html>.
Have read something about a future QTS 6.0 being first released as beta and then implemented over the course of 2026. Very unspecific, did not sound like a reliable source.
@Stephen_Shaw1 does it mean, future production builds will keep relying on old glibc variants?
I interpreted it as “The QNAP package will not work. The Synology package might”.
@Stephen_Shaw1 - can you clarify the plan and, if some distribution + platform combinations are expected to break, is there a communications plan and a go-forward plan for the impacted users?
1 Like
I think that breaking Roon Server for most NAS types would be upsetting to people.
Unless there’s going to be a supported migration to Docker or something.
2 Likes
@Stephen_Shaw1 - This would be really, really important to note for people before the upcoming version is released and all the QNAP users are screwed.
And for the love of (G..g)od, please harness the goodwill of this community to test, inquire about approaches, etc. Make it an active and visible discussion, rather than releasing and ticking off even more users.
Or, if your goal is to just say goodbye to NAS-based users, have the courage to bravely call it out and give people some notice.
3 Likes
Exactly.
Roon should be producing Docker images. I’ve said this for years. I wrote the guide on how to set it up on Synology almost 5 years ago: Walkthrough : Roon in a Docker container on Synology DSM 7
I believe it would be better for Roon and for users to move away from the NAS packages, ship a supported Docker image (either one that can auto-update the apps as the one many of us use does or one that gets updated with each release). For most users, the first approach is probably the best.
This is not the way to get there, though. Users are discovering that EA is not working and are getting confusing answers about what this means. The current direction may be “Break it and then explain what happened”.
This is what should be happening in order to fully support users and maintain good will with the community
- Create and release Production and EA docker images. Both at the same time. Announce that the images are available for testing
- Give the community a chance to use and vet them. There are issues that need to be considered and addressed and it may take a bit to iterate. Things like what user/group the Roon app runs as. The community has experience with this - let us help
- Document the use of Docker on Synology and QNAP with walkthroughs. Provide high-level instructions for other platforms - just the docker command and a sample compose
Once everything is stabilized - the images and the documentation - announce their availability to the community. Announce that in 3 months or some reasonable timeframe, the packages will be deprecated. Do this across the relevant forums and on the Roon website.
I understand this means that you possibly can’t ship the improvements and optimizations that are in the EA branch right now and depend on .net 10. That’s just how software development works - sometimes you have to stage things because of larger concerns.
I hope this is helpful.
5 Likes
This is something I wish all Roon employees developed an appreciation for.
Everyone from @Jeff_P to Dave Rogers — who would do well to have an account in here to demonstrate that the leadership really cares about this community — should care about how much certain people in here care.
A product is nothing without a community behind it. Nothing.
4 Likes