Possibility to set the rock in sleep mode…
A post was split to a new topic: Backup on startup?
I am running a few Hifiberry, Volumio and dietpi instances and I am aware that RoonBridge tells me when an update is available through the Roon Desktop interface.
What does not get updated is the OS stack in these instances. So I have to open the HifiBerry UI and then check if a HifiBerry Update is available and update manually. Same for the others.
With Roon ROCK everything including the OS stack gets updated at once. That’s what I would be looking for in ROCK 2.0 Roon Endpoint Edition.
I don’t know if that’s Roon OS, but I suspect it is. Installing HQ Player on my NUC alongside ROCK would be huge. Main problem now is that streaming endpoints have to support HQ Player’s NAA protocol. If HQ Player running parallel or within Roon OS would enable me to send the upscaled audio via RAAT, that would be totally amazing.
My vote goes to:
UI on HDMI
YES! Importing music files from MacOS to internal Nucleus drive currently results in all music files in folders containing accented/special characters being unplayable in Roon (despite RoonOS being able to see those directories and files). Not clear whether this is a Roon or a RoonOS bug, but extremely vexing.
The focus should be 100% on improving sound quality to meet exceed that of AudioLinux, Euphony, etc. Related to this:
ability to boot the OS to RAM rather than from disk ( operate 100% from RAM with no read/write from disk other than to grab audio files
minimize system utilization not directly related to playback
minimize network chatter, especially during music playback
any and all other levers you all can pull to get ROCK sound quality on par with other dedicated music playback OS’s
Like allways, comparisons like this are meaningless without any reference to how you use the computer running ROCK, directly to a USB dac or ethernet connected to an endpoint.
What metric would you suggest, to compare the two and measure progress in this regard?
Processor latency test can be a metric.
In my case. Network Bridging is the most relevant wishlist.
I was an user of ROCK. But after I tested connecting the streamer straight to the Intel NUC (Roon Core). I couldn’t think of rolling back…
With Rpi3 I could set up a fixed IP adress and it was isolated and working fine. But with opticalRendu only with DHCP assigned IP address.
That’s why I had to go with Audio-Linux instead of ROCK due to network bridging support.
How would you connect that to sound quality, though?
From what I’ve seen, one of the points that audio operating systems emphasize is latency. So does the Fidelizer audio optimization software. Latency seems to be an important parameter for optimizing a digital audio system.
I’m sure there are other metrics, but I don’t know them: I’m not a specialist…
I don’t know if this is relevant to Roon OS but I would really like to be able to Reboot or shut down my ROCK Core from within Roon, I know that going to the ROCK webUI is a minor annoyance but it is an annoyance none the less.
Overall I am for keeping ROCK as small and process free as possible.
Also having to expose/open up the storage folder to gain acess to your music files is a bit cumbersome, each time I do this I have to go through several steps to connect to the music folder over my network. Is it possible to have a link in the ROCK WebUI that once clicked on will open up your internal or attached music folder so that you can easily add albums, or even from within Roon itself.
Its even more cumbersome doing it from my iPad.
Well, we need something more than “everybody else who claims they’re better is doing this.” Like some evidence, and a theory, and a study, perhaps.
If “we” need something more, then “we” need to research and document ourselves more.
Regarding the Roon Labs team, I am sure that they have already documented themselves: their products (Roon OS and Roon) already contain optimizations for audio and this can be seen in the quality of the sound they provide.
But it is you and others who need something more yet you’re not offering any reasonable explanation that can be taken forward.
If you perceive Audio Linux to be better use that. If you prefer the convenience and simplicity of Roon OS / ROCK use this instead.
Why do I have to provide a “reasonable explanation”? Do Roon R&D team implementations depend on my explanations?..
Yes, I use AudioLinux, and the only reason I switched from ROCK to AuduoLinux was the sound quality.
Both have convenience and simplicity, that’s not a reason for me.
Because extraordinary claims require extraordinary evidence, and you can’t expect a company to invest significant ressources into entertaining what very much sounds like delusions unless you’re able to demonstrate that they are not delusions.
Oh, and just in case you wondered, anecdotal evidence (“my wife / [Moderated] hears it as well”) doesn’t apply.