I really love Roon OS. I cannot remind a single issue, super stable.
I would like to be able to configure folder, naming structure and metadata tagging for the ripped albums.
These are my two favorites from your list.
A BIOS update tool built into the installer GUI - that was the worst part of the install experience here. Not RoonLabs’ fault, but on your plate if you want it done properly.
Want a neat trick with HDMI ? Use it for Device integrity monitoring. And please implement integrity monitoring in general.
Not sure if that’s ROCK, but cloud backup for the files, not just the database.
My vote:
- extensions for example pre-installed Extension Manager, incl. ablility to install Entrypoints / Bluetooth
- ability to install HQPlayer embedded (or preinstalled)
- ability to reboot OS or relaunch roon server from a Roon remote
Hmm, since it is not on the “Things not on the table” list, and they are all similar:
- Some way of monitoring the system thermals and memory usage
- Some way of running memory or drive diagnostics. Currently users are asked to boot into a live linux or Windows environment to run such things. If you are in RoonOS you shouldn’t be asked to load a different OS to test the hardware.
Interesting question, as at present RoonOS as part of ROCK running on a NUC does everything I want of it, as a place to run Roon Core to serve my endpoints & zones.
As such I want RoonOS to run as light and fast as possible, with as little resource usage. Additional functionality normally means additional resource usage, so for me “less is definitely more”.
Out of interest I would like a load monitor, with lightweight probes, something like istat with CPU utilisation, load, memory/cache usage and network throughput. I have istat running on my ReadyNAS units, have ported to a RPi and a legacy Linksys NSLU2. I view the statistics on a iOS app. This means the chart rendering is performed off-server, with just the probes running in a thread caching a limited level of data.
On the subject of “something shown on the HDMI (chromecast UI?)”, just get a Chromecast dongle for the display! As to run on RoonOS you would have to envoke GPU processing in the OS, and drive a display - taking away from the headless server focus of RoonOS. Stick to what it is intended as, an embedded server-side headless applicance.
If more is needed, the user can install a general purpose OS and install the Core+Remote product, is my view.
what does this mean?
Is this even possible on NUCs? I didn’t think so…
This is an interesting idea… I’ll split it this out here:
This already works to some degree. Just add a second interface (usually via usb). You won’t get DHCP on the subnet, but you can put your audio endpoints and/or NAS there if you’d like, with a static IP.
It’s an extension allowing to send audio to Roon via Bluetooth. Entrypoints, the audio entrance to Roon [NEW: Bluetooth support]

Things on the table (but not yet committed to):
- extensions
I’d really like this if it were possible - there’s a few extensions I’d like to try but I don’t really want to setup and maintain yet another device to make this work.
Keep it lean and lightweight.
- UEFI support - Yes
- network bridging - Yes
- better exFAT support - Yes
- fixing cd ripper issue - Yes
Additional monitoring as suggested by some other commenters.
Definitely UEFI boot, so as to make ROCK useable on non legacy boot device es (such as Pentium NUCs).
Not sure if you would count the following as being part of ROCK 2.0 or part of Roon. I would be looking for a ROCK implementation that contains Roon Bridge in order to build a Roon Endpoint based on low power (Pentium or Celeron) NUC or NUC like devices. I can do this without major issues using say diet, but dietpi does not maintain itself automatically as does ROCK. I would definitely prefer a Roon supplied one shop solution for a NUC based endpoint.
Alternatively or additionally a ROCK based Roon Bridge endpoint for RP4.

Not sure if you would count the following as being part of ROCK 2.0 or part of Roon. I would be looking for a ROCK implementation that contains Roon Bridge in order to build a Roon Endpoint based on low power (Pentium or Celeron) NUC or NUC like devices. I can do this without major issues using say diet, but dietpi does not maintain itself automatically as does ROCK. I would definitely prefer a Roon supplied one shop solution for a NUC based endpoint.
I think you are suggesting we have a way to disable the Roon Core and replace it with Roon Bridge.
This would be more interesting on lighter weight machines, like Raspberry Pis and so, yah? But with Roipeee and DietPi, is there a need for this? Both are approved by us.
I’m guessing this won’t fit, since it’s not strictly Roon OS, but database validation/verification/integrity, including backups.
Hi - guess I am not clear on OS vs Roon. Assumed that a dashboard change would be part of the OS…

NFS
May I ask why? It’s probably the one thing that keeps me from using Rock.
I hope Roon OS 2.0 to have full compatibility with macOS (or Windows) for European accented characters and 2-byte characters including Japanese.
My wishlist:
- Retaining WiFi support
- Receive audio via Bluetooth and AirPlay
- Power Management
- Wake on LAN/WiFi
- Faster SMB
- Complete Backups including media files (with restore from Dashboard)
- Show some system parameters like temperature sensors and fan speed on dashboard

Assumed that a dashboard change would be part of the OS…
I don’t think I understand what you mean by “dashboard”

May I ask why [not NFS]?
I posted a good overview in a topic you started a while ago:
I think you are grossly missing the point of ROCK (or Nucleus). ROCK is highly opinionated to do things that we feel will lead to success for most users. It was a no-brainer for us to not include NFS support in ROCK. You may run into many opinions with ROCK that you may disagree with, but because it’s not a general-purpose/flexible operating system, you are free to install your own favorite distribution and use RoonServer on that. Now, to address this outrageous claim about a “stupid decision”. …

Wake on LAN/WiFi
Wake on lan over Ethernet is already supported, and given the lack of Wi-Fi support in Roon OS (besides that one NUC), that part isn’t going to happen. I saw you post about Wi-Fi in the other thread, but indeed I do think it’s getting dropped. Roon will continue to work with 1.x.

Faster SMB
Explain…

Power Management
Is this just auto-sleep?

Receive audio via Bluetooth and AirPlay
Where are you rebroadcasting it to? What kinds of latencies are you okay with?

Complete Backups including media files (with restore from Dashboard)
I created another thread recently asking if people are interested in this, be sure to post there.