RoonBridge and Roon Ready .NET Question

Early Access
1

I was asked a question and I wanted to double check with an official answer.

My friend wanted to know what would happen with older Roon Ready hardware when the .NET 10 update to RoonBridge comes out. Specifically it is an older Auralic which is not receiving support.

2

@Rugby I want to double check on something before giving an “official” answer. I’ll reply as soon as I verify some stuff.

3

Generally speaking, Roon Bridge itself will have the same .net 10 glibc issue as the server and client did. Off the top of my head, I believe that was glibc 2.27?

4

I’m confused. Roon Ready hardware doesn’t use Roon Bridge, I thought? And the RAAT doc says that

In fact, the only reason an upgrade should be required is to fix a low-level bug, or to access more hardware functionality . This is really important. Not all partners/hardware have easy firmware update paths that can be done at home. Our acceptance of this reality has deeply influenced RAAT’s design.
(…)
the majority of the business logic is delivered to the device at run-time as a script. This means that we are capable of completely re-designing the audio streaming and buffering logic without updating device firmware. This is absolutely critical, since most of the bugs + evolution in a system like this relate to networking, not audio.

5

@Suedkiez That’s the area I’m uncertain about.

6

Can I widen this out a bit.

  1. Will there be an equivalent update for Roon Ready devices?
  2. Will there be a download of the Net10 framework, presumably as part of the SDK?
  3. If there is, will it need to be pushed out by the company making the device or could it be pulled down automatically?

Thanks and apologies for hijacking the thread, but I thought it was better than starting a new one.

Paul_Argue (Paul Argue) 7

I love the conversation and questions.

@Rugby and @Suedkiez

The reference Roon Ready code shared with partners to include in their products is written in c and the scripts delivered at run-time run are executed through that c code. It all uses standard networking to communicate with the Roon Server. There are no .net dependencies with it.

The Auralic device will continue to work with future Roon versions regardless of how we build Roon. The Roon Ready devices don’t use Roon Bridge so the .net dependencies don’t apply.

@Alan_Bateman , to answer your questions …

  1. moving Roon to .net 10 doesn’t require any changes to Roon Ready devices.

  2. The Roon Ready code will remain optimized for audio gear that spans from specialized devices to ones with high end processors. Dotnet isn’t supported across all these devices so isn’t part of it.

  3. No changes needed to push to Roon Ready devices. However, generally, if there are improvements to be made, it can be done at runtime on the device.

9 Likes
8

That’s what I was sure would be the case based on the docs and what I always told everyone who asked about RR future-proofing, so thanks for the confirmation :smiley:

9

Thanks for the comprehensive and very helpful reply.