Page 2 of 3
Posted: Fri Jan 09, 2026 8:07 pm
by ilz74898
Yeah, This happened to me too. I had to make sure I was using a high-speed HDMI cable and then select the monitor as the default device in the old Windows sound control panel. Good luck!
Posted: Fri Jan 09, 2026 11:47 pm
by ym048993
Agreed, and also double-check that spatial sound is turned off in Windows—sometimes that setting blocks Atmos from enabling.
Posted: Sat Jan 10, 2026 1:53 pm
by 85wovyobxg
Agreed. I had the same problem. For me, it turned out I needed to manually select the monitor as the Atmos device in the Dolby Access app, not just in Windows sound settings. Let me know if that works.
Posted: Sat Jan 10, 2026 2:02 pm
by tms4395
Agreed. Yeah, and make sure you're using a high-speed HDMI cable too—older ones can limit the audio signal.
Posted: Sat Jan 10, 2026 5:32 pm
by n4pfo
Same here. Also, have you checked if the Atmos app or your media player is set to output in that format? Good luck!
Posted: Sun Jan 11, 2026 3:25 am
by 849fjapsxeea
Agreed. You could also try forcing the Atmos format in Windows sound settings by right-clicking the speaker icon and selecting "Spatial sound."
Posted: Sun Jan 11, 2026 7:01 pm
by FrNfSJVEv
Yeah, This happened to me with a different Atmos-capable monitor. I had to go into the Sound Control Panel, select the device under "Playback," and manually enable Atmos in the "Spatial sound" tab there.
Posted: Mon Jan 12, 2026 12:31 am
by mze147
Can confirm. I had the same problem. Even after that, I needed to make sure the specific app, like Netflix or a game, was set to output Atmos in its own audio settings.
Posted: Mon Jan 12, 2026 12:36 am
by bstc6282522
This. Yeah, agreed. Also double-check that your HDMI cable is high-speed, since older ones can sometimes block the Atmos signal.
Posted: Tue Jan 13, 2026 8:14 pm
by mscjOQnoO
I had the same problem. For me, it was actually a setting in the monitor's own on-screen menu that needed to be switched to enable Atmos passthrough.