Windows 11 with Dolby Atmos

Roon Core - Windows 11 PC
Anthem MRX 540 AVR

The PC has an Atmos license and I like to keep it enabled for Netflix / Gaming. However, whenever Atmos is set as the Spatial Sound setting in Windows Sound Settings, Roon won’t play anything. I’ve tried setting the Audio Zone as a 5.1 system with the Send Stereo / Mono content as 5.1 toggled on and off.

The only way I’m able to listen to music is to switch the windows sound panel to Stereo when using Roon. It’s not the end of the world, but it is a bit of a hassle to mess around with settings every time I change apps.

Looking for tips to simplify the process.

hmm… Isn’t that Roon Ready? Why are you not selecting the Anthem directly over the network? How do you have things cabled? What’s your signal path?

I could use it as an airplay device, but that would be exclusive use vs. also having Windows sounds (email, meeting notifications, etc.).

The signal path is Nvidia 3090 → HDMI → Anthem MRX.

Bumping this because it’s become a little more annoying with the recent Windows 11 2h22 update (more steps). If I want to listen to Roon, I have to go into my sound settings, open the old control panel window, reconfigure my Playback device as Stereo. When I’m done, back into Sound settings to reconfigure as a 5.1 Atmos setup.

The behavior of Roon when Atmos is on is if I start Track 1 of an album, it quickly skips through all tracks without playing anything and then stops.

Can official support chime in?

Hi @JD_Cincy,

Thank you for your patience while we took the time to escalate this issue internally.

I’d first recommend temporarily uninstalling the Realtek ASIO driver on your Windows device and testing again. Please let me know if that changes any of the symptoms you’re experiencing and we’ll proceed with next steps from there.

@connor I do use the Realtek device for Mic Input, but I went ahead and uninstalled the driver, rebooted, and disabled the HD Audio device in bios. All devices are disabled aside from the MRX 540 and my USB DAC / AMP. The issue remains, it just rapidly skips through the entire album without playing audio.

Windows Media Player - Tested fine
iTunes - Tested fine

Edit: I also tested System Output and directly to the MRX (windows device, not airplay) with the same result.

image

Thanks for testing, @JD_Cincy, I’ll report these results back to the team and we’ll circle back shortly.

Hi @JD_Cincy,

I just wanted to let you know the team is syncing on this issue again today; we haven’t lost track of it. Please hang in there a little longer, and we should have a more definitive conclusion here.

Hi @JD_Cincy,

I have an additional step to try to pin down definitively if the issue is between Roon → Drivers or between the Drivers → Windows System Output.

Would you please take the following steps to see if the OS can identify any issues with the native or third-party drivers remaining?

  1. Press Windows key + I to open Settings.
  2. Choose Update & Security.dolby atmos windows 10 not working spatial sound isn't working
  3. Select Troubleshoot from the left pane.
  4. Highlight the Playing Audio troubleshooter and click Run the troubleshooter.dolby atmos windows 10 not working spatial sound isn't working
  5. Follow the instructions and, after the troubleshooter ends the task, restart your PC.
  6. Open Sound icon > Spatial sound and try enabling Dolby Atmos again.

If nothing else, this will stabilize conditions in the OS so we can narrow down every variable in the chain and isolate the issue if it’s within Roon’s own I/O.

I ran through those steps and it recommended disabling Audio Enhancements, I did that, and Roon audio played, but went back to Dolby Atmos and it went back to skipping songs.

I reconfirmed Media Player and iTunes both play with Atmos enabled.

Thanks @JD_Cincy,

One more quick test: what happens if you play to System Output instead of directly to the device? We’ll pull logs once you’ve tested.

Selecting direct to the receiver through windows vs. the System Output behaves the same.

These are the 2 options, the 2nd is direct to the receiver -
image

Hi @JD_Cincy,

Our QA team is investigating and reproducing the issue; I’ll respond here as soon as I have an update from them I can provide.

Thank you for your patience, doubtless this is a frustrating issue.

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.