Roon 1.8 (Build 913) Feedback Thread

Gee must be a 10 year old mainboard
Man wake up get something new lol.

Just FYIā€¦ We have reverted build 913 of Roon Bridge back to the prior production version (880) in order to avoid any confusion. The hotfix we released primarily impacts the core and remotes so the need for Roon Bridge to adopt the update is minor. We will re-release the fix for Roon Bridge when we have resolved the Settings ā†’ About issue.

So was this tested hahaha. Ok Iā€™ll stop
Guys just help us old folks here ok.

What about those who cannot upgrade HQPlayer? I guess that we are peripheral damage. My Roon Core CPU has sse4.2 but not avx2. So hqplayer will not update. I am happy with the sound I now get, and I will try to defend against Roon updating. If I am able to, all will remain well. If the Roon update weasels its way in, I am going to have to give up HQPlayer.

If Jussi sees this, I hope he can advise.

HQPlayer has its own threads and own section on this forum. Thread related to current changes in Roon:

Yes, I (more or less) understand this, but in my system, Windows sounds best, and I will stick with it. I still resent being forced to play defense every time I open Roon.

How do I update?
The settings | about donā€™t show any bridges, and rebooting doesnā€™t help.

Iā€™m seeing no issues with Build 913. When I updated earlier today, it wanted to update my RPi4, but I declined the RPi4 update because I have seen no mention of a RoPieeeXL update being available from Harry. Anyway, the RPi4 update is no longer showing as part of Build 913 and RoPieeeXL 880 is showing as current and all is good.

Just updated 3 IOS devices with no issues except a little jittery, more so on the iPad Mini4. Not a big deal, though.

Just to make one point clear hereā€”Roon never will update RoPieee or RoPieeeXL. Thatā€™s Harryā€™s development effort and his call. But what Roon definitely does update is the Bridge component running on RoPieee. On the new RoPieee 2022.20.2 it isnā€™t even possible anymore to update the Roon Bridge from within RoPieee. It must be updated from a Roon client.

So I did update the Bridge as offered by Roon. Now the RoPieee endpoint isnā€™t visible anymore on Roonā€™s Settingsā€”>About page, so I canā€™t revert to the 880 stable build of the Bridge. And if and when Roon updates the Bridge after resolving this bug, this wonā€™t be possible either, and I guess we will have to install RoPieee from scratch, so that it can download and install the latest Bridge component during its installation process.

As RoPieee is still working fine, even if it isnā€™t visible anymore in Roonā€™s ā€˜Aboutā€™ page, this isnā€™t a big deal, and if in the future Iā€™ll have to reflash and reinstall RoPieee, this also is done in a moment. So, all this only to make things clear for others who read across this thread.

1 Like

Whatever, it wanted to update, I did not allow it and all is still good. I will never allow an update of my RPi4 runnning RoPieeeXL except from Harry.

What a mess this 913 Build. My three RoPieee Displays are having issues showing error screens while playback after updating them to 913. And there is no way to go back to 880 Build because they donā€™t show up in Setting/About ā€¦

1 Like

Enrico, as Roon has already reverted Roon Bridge to the stable build 880, what you could do is reflash and reinstall your three RoPieee devices. During a fresh installation they should download and install the 880 build and so you could revert the devices to the same version as before the 913 release from today.

https://ropieee.org/software/

Download and use Etcher to reflash your SD card.

I know I can reflash but thatā€™s what I donā€™t want to do as involves disassembling my three RoPieee Displays but I guess if there is no other way then Iā€™ll do it ā€¦ā€¦.

1 Like

@spockfish,
For cases as this it would be great if we could have on the new RoPieee a button to reinstall the Roon Bridge component, as there was on the old RoPieeeā€¦

I am very impressed with this build. Responsiveness improved a lot, artist and album images load instantly. There also seems to be less delay when starting a track. The experience feels solid and together. Thanks Roon.

3 Likes

Canā€™t you ssh into Ropiee and reinstall Roon Bridge like you would any other RPi?

No you canā€™t with the new RoPieee NG. Harry @spockfish took out that functionality from the new RoPieee NG.

My error log for rge roonbridge helper in 913 is under Ubuntu Server:

Mar  3 00:00:02 roonserver start.sh[13719]: #033[0;37;1m#033[0;0m02:41:49.519 #033[0;37;1mInfo:  Starting /opt/RoonBridge/Bridge/RoonBridgeHelper#033[0;0m
Mar  3 00:00:02 roonserver start.sh[13719]: Running
Mar  3 00:00:02 roonserver start.sh[61742]: Unhandled Exception:
Mar  3 00:00:02 roonserver start.sh[61742]: System.TypeInitializationException: The type initializer for 'Sooloos.RoonPush' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Sooloos.Bits' threw an exception. ---> System.ArgumentNullException: Value cannot be null.
Mar  3 00:00:02 roonserver start.sh[61742]: Parameter name: path2
Mar  3 00:00:02 roonserver start.sh[61742]:   at System.IO.Path.Combine (System.String path1, System.String path2) [0x00011] in <e64204cdf72f439c9aca786ac688b49a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Base.Utils.GetLocalApplicationDataDirectory (System.String appname, System.String appdir_dir) [0x0000e] in <53ec9c3beabc4c4c8105202f891620cb>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Base.Utils.GetLocalApplicationDataDirectory () [0x00005] in <53ec9c3beabc4c4c8105202f891620cb>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.SooloosRegistry.get_DefaultRoot () [0x00007] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.SooloosRegistry..ctor (System.String product, System.String key) [0x0003a] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.SooloosRegistry.Get (System.String product, System.String key) [0x00000] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.Bits..cctor () [0x0004a] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:    --- End of inner exception stack trace ---
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.RoonPush..cctor () [0x00000] in <cf047651ff2c46868428c633254705a8>:0
Mar  3 00:00:02 roonserver start.sh[61742]:    --- End of inner exception stack trace ---
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.App.Main (System.String[] argv) [0x00000] in <574ba35c72434ebf8509fce512b2b27f>:0
Mar  3 00:00:02 roonserver start.sh[61742]: [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Sooloos.RoonPush' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Sooloos.Bits' threw an exception. ---> System.ArgumentNullException: Value cannot be null.
Mar  3 00:00:02 roonserver start.sh[61742]: Parameter name: path2
Mar  3 00:00:02 roonserver start.sh[61742]:   at System.IO.Path.Combine (System.String path1, System.String path2) [0x00011] in <e64204cdf72f439c9aca786ac688b49a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Base.Utils.GetLocalApplicationDataDirectory (System.String appname, System.String appdir_dir) [0x0000e] in <53ec9c3beabc4c4c8105202f891620cb>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Base.Utils.GetLocalApplicationDataDirectory () [0x00005] in <53ec9c3beabc4c4c8105202f891620cb>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.SooloosRegistry.get_DefaultRoot () [0x00007] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.SooloosRegistry..ctor (System.String product, System.String key) [0x0003a] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.SooloosRegistry.Get (System.String product, System.String key) [0x00000] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.Bits..cctor () [0x0004a] in <2eea627833db4a29803e2a52c47a559a>:0
Mar  3 00:00:02 roonserver start.sh[61742]:    --- End of inner exception stack trace ---
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.RoonPush..cctor () [0x00000] in <cf047651ff2c46868428c633254705a8>:0
Mar  3 00:00:02 roonserver start.sh[61742]:    --- End of inner exception stack trace ---
Mar  3 00:00:02 roonserver start.sh[61742]:   at Sooloos.App.Main (System.String[] argv) [0x00000] in <574ba35c72434ebf8509fce512b2b27f>:0
Mar  3 00:00:02 roonserver start.sh[13719]: Not Running (o.)

1 Like

Nice to see a little ray of happiness in this thread.

4 Likes