· I'm having trouble with my DAC, speakers, streamer, etc.
· My device has never shown up in Settings > Audio
Trying to add Holo May DAC but it does not show in Audio tab in Settings
Roon core running on dedicated NUC. Roon remote running on Win10 PC and DAC connected to this PC as well.
The Holo May must be used by USB and in this case should be connected to the Roon Server, i.e., the NUC.
It might work if you let the Roon Server play to the Windows PC as endpoint and connect the DAC to the Windows machine, but I believe in this case Roon on Windows would use the Windows system output.
Are you saying there is no way to connect the Holo May DAC to my Win10 machine that is running Roon Remote?
USB DACs must be connected to the headless Roon Core always?
It is possible to use the Windows PC with a running Roon app (or Roon Bridge) as the endpoint for network streaming. And then the DAC would be connected to the Windows PC.
However, I think that in this case the Roon Server would only „see“ the Windows PC as the output, and it wouldn’t know what’s „behind“ it. So the May as such would not appear in the Roon audio settings and you would choose the Windows PC as the output „zone“ for Roon. And then the Windows machine has to output to the DAC.
I am OK with that, but I cannot choose the Windows PC as the output zone…
So I am stuck in limbo 
@Zachi, are you saying that you W10 PC is not showing as a Roon Remote or Roon endpoint option with either Roon or Roon Bridge installed on it? Have you checked that the W10 PC has roon.exe, raatserver.exe, and roonappliance.exe set as exceptions in the Windows (or third-party) firewall, as well as ensuring your W10 PC is set to Private network?
And what about this?
Thanks. Have you rebooted the NUC? Occasionally when I lose access to a Remote device rebooting the Roon Server recovers the ability to play to it.
I just checked that the W10 PC has roon.exe, raatserver.exe, and roonappliance.exe set as exceptions in the Windows firewall.
I confirmed W10 PC is set to Private network.
Restarted Roon Core (ROCK).
Nada. No change. Still Cannot see the DAC.
Also, confirming it is not a hardware issue - I launched Jriver MC 26 that is installed on W10, and successfully played music on the Holo May.
So, definitely a Roon software issue.
Looking at the Task Manager - I see both Roon Appliance as well as Roon Server are running.
Is that normal? Should I somehow stop Roon Server process on the W10 PC?
It shouldn’t matter but you can stop it. Right-click the little Roon icon in the notification area on the Windows task bar. Also uncheck the “Launch at startup”:
(The Roon installer installs the Roon Server on Windows as well, but as you use ROCK it’s not necessary)
Thanks @Suedkiez
Any suggestions anyone? At this point, I am out of ideas…
Probably a small stupid oversight of something, but no idea what to try next to debug this issue.
I’m out of ideas, sorry. Official support will show up but it may take a bit of time
There is an issue of communication between your Server and your PC. The Server queries the PC to find out audio devices on it, and then the Server builds the audio devices using the responses.
Notice the “This PC” section…
You’ll notice that your screen pic is missing the Local “This PC” completely which again suggests that the communication is broken.
Some people have mentioned the most common causes.
Firewall. This can be mis-configured, so I’d just test by turning off the firewall completely and see if the audio devices show up. If not, then turn it back on. If so, then you know that a firewall configuration is the issue.
Private vs Local which you’ve already said that you checked that it is private.
VPNs running on the PC. VPNs and other network software can cause issues.
Software Conflicts
Conflict with software that controls audio devices, including Gaming Overlays, DAW software, etc.
Sometimes out of date Realtek drivers have caused this.
You might try resetting your Raatserver which would force the server to recreate the audio devices.
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
- Create a Backup of your current Roon database
- Exit out of Roon
- Navigate to your Roon’s Database Location
- Find the folder that says “RAATServer”
- Rename the “RAATServer” folder to “RAATServer_old”
- Restart the Roon App to generate a new RAATServer folder
Before testing all the great suggestions by @Rugby (thanks!!!) - I have a related question:
A friend told me that I am installing the “wrong Roon software” on my Win10 PC.
He told me I need instead (or in addition) to install Roon Bridge!
Any chance he is correct? If the Win10 machine will BOTH be used to control what’s playing AND has the DAC attached to it - do I need both Roon Desktop (or Roon Remote for Win) PLUS the Roon Bridge running on it??
Your friend is partly correct. If you want to control Roon, you need the full Roon installation that includes the graphical interface. If you just want to play to your W10 PC, then all that is needed is Roon Bridge, and you control Roon with another device. While both can be installed on your W10 PC, only one should be running. If you always intend to control Roon with your W10 PC, then you don’t need Roon Bridge installed or running; Roon Bridge is the Roon Remote application without a graphical interface and other features not needed.
Thank you all for the great tips and suggestions!
Managed to get it to work!!! 
After turning off Windows Firewall - it worked for the first time!
So… re-enabled windows firewall, and started playing with it.
I did not think I ended up changing anything, but it now works. Maybe disabling and enabling the firewall all by itself changed something or refreshed something? 
Either way, restarted Win10 and it still works, so I am finally in business!!
You guys rock. 
Glad you got it working. Now to enjoy some music! 
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
