Roon Bridge on Nuc with HDMI - will it work?

I have no experience with and hardly any knowledge about the Roon Bridge software - but it should be possible to make a Roon endpoint this way, right?

As I am now going to replace my first NUC for the ROCk with a bigger model, I can use that “old” NUC11-i3 with 16 GB memory and a 1 TB SSD for something else, and I thought about putting a Bridge on it and use it with an AV amplifier through an HDMI port.

Will that be possible?

Any experience or thoughts about this?

How would that measure up compared to, say, a WiiM Pro? (perhaps with a different cable than the HDMI)

I believe that this should work without issue. 16GByte RAM and 1TB SSD is considerably over the top if all you are going to do is run the NUC as a Roon Bridge.

Your ROCK install could work as a bridge as it is - just de-authorise the server and authorise the server on the new NUC.

Alternaltively, you could install the operating system of your choice (Linux or Windows) and then install Roon Bridge. For my part, I would find this option simpler in the long run as the Bridge NUC will not present as a server when connecting Roon (desktop) or Roon Remote devices.

One very easy way that this can be achieved is by installing DietPi on your NUC11-i3. Look for the “Native PC for UEFI” image under PC/VM in DietPi Downloads

DietPi also has the ability to run other software packages which may or may not be of interest:

The install procedure for DietPi is essentially the same as for ROCK.

1 Like

You can use ROCK as a bridge, without a roon core license.

So you can use as it without installing new os / software.

1 Like

As I said :wink:

1 Like

Clever! So the ROCK contains all of the Bridge software as well?

That makes me think about the purpose for Roon to even make that separate Bridge software… Any explanation on that?

See:

1 Like

Effectively yes.

The Roon Server, Roon Bridge and Roon (and even Roon Remote) applications are different combinations of three areas of functionality offering Server, GUI and endpoint presentation functionality.

Roon Server gives server and endpoint presentation functionality.
Roon (and Roon Remote) give GUI and endpoint presentation functionality.
Roon Bridge gives only endpoint presentation functionality.

Just as the endpoints created by Roon and Roon Bridge can be used, if configured to be public, from any remote, so the the endpoints created by the Roon Server application can be used by any Roon Server. They are just another set of endpoints.

The purpose of the the separate Roon Bridge software package is two-fold:

  1. It provides endpoint functionality on SBC’s running linux (for which there is no official GUI) that are not capable of running Roon Server (like Raspberry Pis). Roon Bridge is what makes Ropieee, to name just one, work with Roon.
  2. It can be installed on other computers so that they can be used as endpoints without having to run Roon GUI or Roon Server.
1 Like

These considerations made be realize that there is one drawback on using the NUC as a bridge - it has no WiFi, so I must draw a cable to where it is to be placed. Or put WiFi in it - if I do that, will the Roon Server/Bridge be able to make use of the WiFi?

Good idea - I have a spare PI or two. Except that the PI doesn’t have any audio outputs - I must add some to it.

My NUC11TNHi7 does have Wifi. It’s just not recognised by RoonOs. Run DietPi on it as I do (or any other Linux or Windows), and it works fine:

root@Roon:~# ifconfig
docker0: flags=4099  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether xx:xx:xx:xx:xx:xx  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163  mtu 1500
        inet 10.212.153.202  netmask 255.255.255.0  broadcast 10.212.153.255
        inet6 fe80::xxxx:xxxx:xxxx:xxxx  prefixlen 64  scopeid 0x20
        inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx  prefixlen 64  scopeid 0x0
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 10447277  bytes 6229690264 (5.8 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 13624985  bytes 15134689085 (14.0 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x6a200000-6a2fffff

lo: flags=73  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 3756145  bytes 410911698 (391.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3756145  bytes 410911698 (391.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163  mtu 1500
        inet 10.212.153.160  netmask 255.255.255.0  broadcast 10.212.153.255
        inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx  prefixlen 64  scopeid 0x0
        inet6 fe80::xxxx:xxxx:xxxx:xxxx  prefixlen 64  scopeid 0x20
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 1258  bytes 402495 (393.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 471  bytes 68857 (67.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@Roon:~#

and

Microsoft Windows [Version 10.0.22631.3737]
(c) Microsoft Corporation. All rights reserved.

C:\Users\wade>ping 10.212.153.160

Pinging 10.212.153.160 with 32 bytes of data:
Reply from 10.212.153.160: bytes=32 time=1ms TTL=64
Reply from 10.212.153.160: bytes=32 time=1ms TTL=64
Reply from 10.212.153.160: bytes=32 time=1ms TTL=64
Reply from 10.212.153.160: bytes=32 time=1ms TTL=64

Ping statistics for 10.212.153.160:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Users\wade>
1 Like

Excellent, thanks! Then it will need a reinstall of the Server or the Bridge, this time on DietPI - and I will have as much audio quality as the amplifier’s DAc can provide :slight_smile:

F.Y.I. I found the NUC11TNHi7 spec (removed from Intel’s site) at SimplyNuc

The Wifi on the NUC11TNHi7 is WiFi6 (802.11ax).

You don’t give the specific model, but I would imagine that your NUC11i3 is the same.

Thanks, my i3 NUC is this one: Intel PANTHER CANYON NUC11PAHI30Z00

Again, according to SimplyNUC, this NUC has WiFi6 using an intel AX201. In contrast to my NUC, yours runs Bluetooth 5.2 (mine in 5.1).

Well, thanks - then I’ll try your suggested setup. Just got the new NUC today, setting it up for ROCK now, so it will be a bit later.

Btw.: The new NUC is the same model, just with i7, so I expect it to work just as well as a ROCK, only faster.

1 Like