· My DAC, streamer, or speaker doesn't appear as a Zone in Roon
What type of Zone is affected by this problem?
· *Directly-connected Zones* are affected.
Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?
· Connected directly to my RoonServer machine
Does the device show up at all in Roon Settings -> Audio?
· No, it does not show up there
Does the device play audio from another source when using the same connection?
· The device has no problems with another audio source
Have you checked that Roon is whitelisted in any firewalls?
· I've checked the firewall and the issue remains
Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device
· My devices are on a single subnet but is not visible to Roon
Do you have a complex network setup?
· I have a *mesh network* with devices connected to multiples points
Your local network might need some re-arranging to support Roon.
· None of the suggestions have helped me. I'd like to submit a support request.
Do you have an approximate timestamp of when the issue last occurred?
· 17:33 GMT
What are the make and model of the affected audio device(s) and the connection type?
· Schiit Modi+
Describe the issue
I have an i7 Comet Lake NUC (i7-10710U) Windows 11 PC that I am running Roon Server on as a headless unit. I have a Schiit Modi+ USB DAC connected directly to the NUC via USB. The NUC is connected to an Eero mesh network via WiFi but the Modi+ should be the default audio zone. However, it doesn't show as an audio zone on any Roon remote endpoint device (MacBook Pro, iPad, iPhone) in Roon unless I physically connected (via HDMI to a screen) the NUC first. If I remote into the NUC using Microsoft Remote Desktop, it changes the audio zone and the Modi+ is no longer available on any Roon endpoint until I reconnect physically with HDMI again. Selecting WASAPI or System Output on any Roon endpoint brings up either the error "Too Many Failures" or does not play at all. The Modi+ is the default audio device in Windows and all other audio outputs are disabled in Control Panel / Settings. I basically cannot use Roon Server in a headless way. Note too that I still do use remoting into the machine to burn CD's and add music from other sources so a complete 'set & forget' system where once the Modi+ is enabled leave it alone will not work for me.
Just some thoughts. Windows 11 is a desktop operating system – no monitor connected equals no (local) desktop and user not logged in (locally). Locally connected peripherals may require a local desktop and login to work (properly). Do you use auto log in for your Windows 11?
IIRC does Remote Desktop default to redirect audio to the remote location. This might be a configuration choice though – check the available connection options (if the issue can’t be resolved entirely with auto log in already).
Thank you for your post. Before we get too deep into troubleshooting, we need to simplify some topology that’s causing interference with device announcements.
Diagnostics indicate that the NUC and the rest of the network are on two separate subnetworks, assuming a common 255.255.255.0 netmask. Roon’s device announcements can’t cross subnets/VLANs - you’ll need to restrict this network to a single subnet to verify that the NUC’s RAATServer can announce itself to the remotes.
Thanks for the reply, yes I use auto logon with a local account and no password so anytime I connect through Remote Desktop it auto logs in and the same when rebooting. Good call, will check the settings to see.
Thanks for the reply. The issue is that if I physically connect to the machine via HDMI the Modi+ re-appears on all endpoints even though there is no other (including network) configuration change otherwise.
I’m no longer that much into Windows but IIRC and again: No video equals no (local) login and potentially no access to local peripheral devices. Auto login alone is not enough. You may need a HDMI headless monitor emulator if you can’t keep a monitor/TV connected.
Or maybe you can ask in a Windows forum for more information.
Hey all, @noris & @BlackJack thanks for your replies! I really appreciate your help! This was solved in two ways. 1. with the HDMI dummy plug you suggested and the other with ensuring Remote Desktop had audio device sharing turned on. This then ensured it defaulted to the DAC (which was the default) and that the GPU defaulted to the dummy plug as the video output and didnt shift to the virtual screen.
Hi @Richard_Steward,
Thanks for letting us know how you solved this. I’ll mark this thread to close for you. It’ll remain open for a couple more days in case the problem returns.
