Roon refuses to identify NUC / AQ Dragonflys

OK, Ladies - I’m mystified.

My NUC arrived today. I tried exporting video via USB - no dice (black screen). But since the thing is supposed to have Win 11 already installed, I plugged in the Ethernet cable (success with connectivity - green lights at the Ethernet socket). I plugged in the Audioquest Dragonfly (success with connectivity - red dragonfly logo). I plugged in the audio adapter (stereo 1/8" headphone male to twin RCA males plugged into amplification).

I then fired up the Roon core - No ID of the Dragonfly at all.

Troubleshooting:

I know the Dragonfly works because I plugged it into the Mac mini (with the Roon core) directly. Roon immediately identified it and played music without issue to the analog output of the Dragonfly.
I know the Ethernet network is live - Other devices (including the TV) are plugged into the living room Ethernet switch, and THEY can all see the internet.
I know the amplification chain is good - I can plug in my disc player and get music out of the speakers.

My conclusion: Either the NUC is defective or Roon isn’t working right.

Your thoughts?

Will try this evening & report results. Thanks!

It’s not clear ,

Where is your Core/Server ? I assume the Mac
Do you have Roon installed on the NUC as a remote app?

Try putting a monitor onto the NUC , and Boot you should get a Windows welcome page or start page that will prove the NUC is ok and Windows is running ok . Now install Roon as a Windows app, as a Remote , do not create a server (assuming you already have one) . Log into Roon etc and your server should show up ready for connection

The Dragonfly will need an app to go through it won’t show as a network device direct this is my Win10 with Dragonfly inserted

My Roon Server is a NUC/ROCK ,when I plug my Dragonfly into my WINDOWS PC I see Settings>Audio. If I plug to the NUC (I can’t just do this) I should see Dragonfly in the Roon Ready section I think.

Have you enabled the Dragonfly in Settings

Few ideas to try …

Are you planning to install ROCK or stay Windows ?

I can’t enable the Dragonfly in Settings because the DAC is not shown at all.

The NUC must stay Windows.

When you have followed the advice above to get everything working, you can, if you wish, then install Roon Bridge and set it to run on startup. This will enable you to use the Dragonfly as an Roon endpoint without having to start the Roon Desktop app on the NUC.

Edit: should have replied to thread rather than @Mike_O_Neill. Sorry.

Then you must install Roon as an a std install. Do you intend the NUC as the Server or an End Point , it will determine how you install Roon

Your plans are not clear, difficult to advise

Hi @Mike_O_Neill -

To clarify:

My Roon Core is on a Mac mini in the computer room. For the time being, it has to stay there. The Mac mini is connected to the NUC (in the listening room) via Ethernet.

I just want the NUC to act as an End Point until I get delivery of a new Roon Nucleus One.

I won’t have any video out from the NUC until Tuesday (when a mini-display-port to HDMI adapter arrives from Amazon). Once I can see what I’m doing with the NUC, what do I need to install to make the NUC into a functional End Point? I don’t think I can install another copy of Roon, because I’d need a second license, yes? I already have a copy of Roon Remote installed on my iPad (for control of the core). If I install a second copy of Roon Remote on the NUC, will they conflict?

Roon has cost me a FORTUNE by breaking their support for Apple End Points, and I DO NOT APPRECIATE IT! Until Roon “upgraded” to 2.0, my system identified my Apple TV-3 as a valid End Point over Ethernet.

When I lost connection, I assumed that my Apple TV had gone bad & replaced it. No difference - Roon still wouldn’t work.

I then tried to persuade my Roon Core to recognize a Roku Ultra as an endpoint (thinking that the USB-C port on the Roku would allow me to hook up the Dragonfly via an adapter). Nope - Roon still wouldn’t recognize the Dragonfly.

I then bought a Lightning to USB adapter and tried to use my iPhone as an endpoint with the Dragonfly plugged into the USB side of the adapter. Nope - Roon won’t recognize the phone or the Dragonfly.

I then gave up and ordered the Roon Nucleus One, hoping to do away with the NUC and the Mac mini completely. But Roon isn’t delivering any until mid-June (if then).

BOO on Roon!

Did you load Roon on to the NUC?

You can either.

  1. Load Roonbridge on the Nuc and it show up in the Audio devices of the Mac Mini RoonServer as long as you have allowed the Windows firewall access.

  2. Load Roon on the NUC and use it as the server and turn your mac Mini into a remote.

The steps to do either are different. It doesn’t sound like you have actually done the correct steps for either scenario.

A few saliet points

I am assuming you have abbreviated your connection description . I take it you have a router or switch between them . You cannot simply plug ethernet into Mac Mini and the other end of the cable into the NUC that’s not how it works it needs to via your Router or a local Switch. ie

Mac > Ethernet Cable> Router (or switch)>Ethernet Cable > NUC

Do you not have a conventional PC monitor that you can connect to the NUC by HDMI just while you do the installation ? You will need a keyboard and mouse too. After that it can run headless

The Roon license covers ONE Core/Server . Any additional software (Remote , Bridge etc) is part of that license. So all you need to do is to download the Roon Installer file

https://roon.app/en/downloads

and install on the NUC/windows. All relevant Windows software is in the one package.

You would only need a second license if you run a second core not any of the remote or bridge apps…

During that install there will be a message (I think , it’s a while back) asking if this is to be the server (say No)

Now when you start the NUC version of Roon it will display available servers on your network , so the Mac Mini should show up as a selection, click Connect and that should be that

No , you can have as many Remote apps as you wish the limitation is only the Core/Server as above . I have at least 5 remote instances on various tablets and phones no problem.

Let us know how you get on :sunglasses:

Thanks @Jim_F - Yeah, I got that. My licensed Roon Core is currently on my Mac mini & must stay there until my Nucleus One arrives.

Thanks @Rugby - Since I want the NUC to be an endpoint, I installed Roon Bridge. A shortcut appeared on the Win-10 desktop, but when I click it, nothing seems to happen?

Thanks @Mike_O_Neill - Yes, you’re right - my connection description IS abbreviated. The Mac mini in the computer room connects to a Netgear Orbi combo cable modem, WiFi base, and router. From the Orbi, an Ethernet cable runs through the attic to the listening room, where a 5-port Ethernet switch feeds the NUC, the TV, an AVR, a Roku, an Apple TV, and a Yamaha disc player.

Ideas? Thanks again to all of you - Boomzilla

Roon Bridge has no gui or anything it will just start and run in the background. You can check its running with task manager.

If you’re not seeing Roon Bridge on your core and it’s definitely running then most likely Windows firewall is blocking it. Ensure the RAATServer application and anything Roon related on the pc are exceptions in windows firewall.

Hi @Jim_F -
You’re absolutely right - but just now, I have but two available computers in the house - The Mac mini (where the Roon Core currently resides) and the NUC (where Roon Bridge is currently installed, but doesn’t seem to be working). Why don’t I move the core to the NUC? Might be the thing to try…

Hi @Simon_Arnold3 -
The Windows task manager is installed and open, but not working…

The first thing I’m going to do is fight the good fight with Windows Defender firewall. I suspect it’s the culprit. If that doesn’t solve the problem, I’m moving the Roon Core to the NUC.

Time to ask the obvious question.

Have you enabled the a Dragonfly endpoint in Roon → settings → audio. It should appear undead a set of endpoints associated with the NUC.

It will.aopear as an icon in the notification section. There you can stop it ir set it toneun on login.