Is the affected network Zone connected with Ethernet or WiFi?
· Ethernet
Does the issue affect all file formats?
· The issue *only affects one file *format.
Which format is giving you trouble?
· DSD
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)?
· It is connected through a different device (e.g Rasberry Pi)
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
If the device has multiple output options, do the other options work as expected?
· Only one output type is affected while the other output type works as expected
Is the device using the latest firmware as per the manufacturer?
· Firmware is up-to-date but the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· 5pm 2/5/2025
What are the make and model of the affected audio device(s) and the connection type?
· Windows 11 PC HDMI to Marantz Cinema 50 receiver.
Describe the issue
"Failed to initialize the Audio device" multichannel DSD
Describe your network setup
Music files stored on Synology NAS, Roon server on ROCK, Roon Bridge on Windows 11, all hardwired Ethernet
Roon doesn’t play DSD over HDMI. DSD will be converted to PCM. Look at your signal path after selecting a DSD file and see what it shows. Post a shot of the signal path here is you can.
I don’t know about the bridge, maybe it can with that running on windows.
If you try to enable System Output and have the system route the audio to the Marantz, does that work as expected? For the LR zone, did you by any chance have Exclusive Mode set up for it, and have something else controlling it on the desktop when attempting to play to it? Also, yes as @Mike_LC mentioned, seeing the Signal Path for the zone when it is working can help clarify the audio output chain.
Yep, native DSD over HDMI via PC like hardware is not possible.
You may save time converting all your DSD files. Instead you may enable PCM output in Roon. Should also work for multichannel.
Have you set your speaker layout in roon properly to e.g. 5.1?
Yes, as shown above I have DSD working when the roonbridge is in 2 channel mode, the issue is DSD when the roonbridge is in multichannel (5.1 or 7.1). flac is working with the roonbridge in multichannel, but the only test file I had was a quad 4.0 file, not a 5.1 file. So, I’ve converted a 5.1 channel .dsf to a 5.1 channel .flac to test.
There is an existing investigation into this issue - we’ve escalated to determine the status of the ticket and will post here once we have a clear next step. Thank you!
Wondering if you have selected 7.1 with surround and rear speakers swapped in settings rather than 5.1. When I run HDMI into my Integra integrated and my Marantz prepro, I get the same error message on 5.1. But it works for me using the bigger speaker array setup. JCR
What I would check here at first:
Use multichannel flacs with 176,4 in your system, because a lot of DACs doesn’t support them.
If this is not working, then change the settings in Roon to pcm 96 max and try your multichannel dsfs again.
Well, I stand corrected. I can indeed duplicate the exact same issue with a W10 PC outputting HDMI to my Denon integrated. DSD 2.0 plays fine downconverted by Roon to 32/176.4. DSD MCH gives the fail to initiate device error message. I note that on two PC to HDMI systems I have at home, I cannot open Roon settings any longer for the Intel Display Audio endpoint. The endpoint disappears briefly when attempting to enter Device Setup in Settings.
So this is something new, as I used to be able to play DSD MCH files just fine. Not sure which Roon version has broken this. JCR
HI @David_Phillips,
Sorry for the long delay in responding. Unfortunately there is much to report at this point. The investigation is still ongoing. Once we have something to report we will let you know here.
@daniel, I have the same going on with at least two of my HDMI MCH endpoints, so please keep me posted as well.
I note that this thread closes in 14 days without further traffic. Obviously, your note and mine here start the 14-day clock again. Are we, as users, responsible to keep the thread open by posting at least every 13 days? Thanks. JCR
