This thread is for general comments and feedback regarding Roon 1.2. If you have a Support issue requiring assistance please open a thread in the Support section.
Now that the devs are sitting on the back porch, sipping whisky and whittling … Thanks guys. There’s a lot of stuff in this release that really colours in the sketch of Roon’s potential that led us to subscribe. A lot of hard work on your part which will forever change not just Roon, but computer audio generally.
Since Roon is built on .net, we use Xamarin tools to target iOS and Android. Their garbage collector doesn’t play well in the same process with CoreAudio because it pauses the entire universe, including unmanaged audio handling components when it runs, and that doesn’t sound very good.
Our usual solution is to move audio handling out of process–which we do on all of the other platforms. Unfortunately, Apple doesn’t allow us to do the same.
Our backup solution would be to run our audio server as a background process outside of our app…but Apple’s rules surrounding background processes don’t accommodate our use case either.
This garbage collector issue is being worked on by the Xamarin guys (well…Microsoft guys now ). They seem to be on track to clear it in the next few months. At that point, we’ll be able to see where things have landed.
I encountered one problem during the upgrade: I have the client running on a laptop and Roon Server running on a headless Windows 10 PC. Running from the laptop, the upgrade appeared to hang. When I remoted into the PC I saw that Windows had popped up a firewall permissions dialog, once I clicked OK the upgrade completed with no problems.
Thanks for mentioning that. I expect you won’t be the only one.
This is the result of moving our audio playback out to a separate process–a big win in terms of flexibility, stability, and better isolation for the audio bits, but a bummer for firewall configuration.