Updated firmware and Qnap Hero OS this morning. Upon the first attempt it still did not work, but stopped/started the Roon app on the QNAP and surprise, it is back up and running.
I will say the playback, track scrolling and play / stop function is MUCH slower but I’ll take a slower, working ROON vs non-functional Roon. At least for now =)
Generally reports have been that it’s faster (at least initially, there is a known memory leak that’s been identified and Roon are working on).
It may be that Roon is rescanning your music library, check for a spinning blue circle (and CPU usage).
Library appears to be fully scanned (just forced a new one). Did a quick stopwatch test from clicking start to music. It’s about 4 seconds for me. My QNAP is quite “beefy” for a NAS and there was no issue on the previous software version.
At least with playing to Sonos speakers (non-airplay - hardwires - local & streaming services)
Thanks @Sean_Agnew for trying QuTs hero!
Fully scanned, identified and audio analysis completed, does not necessarily mean all the metadata background work is done. The latter can slow down roon significantly.
Did you try to run roon under Container Station, and does it behave in a similar way?
It’s the same library that I have always had, but maybe the OS update could have triggered additional background work / scanning to occur. I have not come across something like a spinning wheels, or progress bar. Is there a way that I could check?
The CPU currently shows almost no usage :
I did not try running it under Container Station. Prior to the Roon update, I believed that controlling my local files (play, stop, pause, track skip) was faster than any streaming service.
Fwiw, both the mobile and desktop version’s of Roon software controller are currently presenting the same delay issue with both local files and streaming services.
