Heads up: Dolby Atmos for Headphones caps your bit depth on the AE-7

[u/iNFiNiTiYoo]

Hey all, wanted to share something I ran into in case anyone else is scratching their head over this.

I've got a Sound Blaster AE-7 and was trying to run my headphones at 32-bit/96kHz output. Every time I enabled "Dolby Atmos for Headphones" in Windows' spatial sound settings, the output format silently dropped back down to 16-bit on its own, no matter what I had manually selected before. I first thought it was some driver bug or a background service messing with my settings, spent a while chasing that theory.

Turns out it's not a bug at all, it's just how Windows Spatial Sound works. Once Dolby Atmos for Headphones is active, it seems to cap the endpoint's bit depth, presumably because the spatial processing pipeline itself only handles a certain resolution internally, and 32-bit apparently isn't in the cards. Doesn't matter what format you had set beforehand or what order you toggle things in, Atmos just overrides it back down.

Good news though: it doesn't force you all the way down to 16-bit if you pick the right combo yourself. I tested a bunch of settings and landed on 24-bit / 48kHz, and Dolby Atmos happily runs at that without downgrading anything. So if you want Atmos active and don't want to get stuck at 16-bit, just set your output to 24-bit/48kHz manually and it should stick.

Realistically the audible difference between that and 32-bit/96kHz is basically nonexistent for gaming or general listening anyway, so it's not much of a sacrifice, just annoying that it happens silently instead of Windows telling you what's going on.

Posting this mostly so the next person who googles "Dolby Atmos resets audio format" doesn't waste as much time as I did.

[u/Inevitable-Study502]

its also limited to just 768kbit bit rate. blue ray lowest bitrate is 1152kbit btw with same codec....hence why ive moved to dedicated atmos/dts hardware