I think it's not the PC sleep or hibernate, I never use that either. I think CoolGTX is talking about a specific NVidia audio sleep timer? I didn't even know it existed.
 

Why not use sleep or hibernate?  They are gifts from God.

Nereus
 
I think it's not the PC sleep or hibernate, I never use that either. I think CoolGTX is talking about a specific NVidia audio sleep timer? I didn't even know it existed.
 

 
 
the screen shot I used was from techpowerup -- did not show the Audio Timer Box checked .... I just wanted to Show Where to Find it
 
Fixed it

ty_ger07
Why not use sleep or hibernate?  They are gifts from God.

Known bug for 3 years with sound & Nvidia drivers .... many experience the bug only after sleep or hibernate

Cool GTX

Nereus
 
I think it's not the PC sleep or hibernate, I never use that either. I think CoolGTX is talking about a specific NVidia audio sleep timer? I didn't even know it existed.
 

 
 
the screen shot I used was from techpowerup -- did not show the Audio Timer Box checked .... I just wanted to Show Where to Find it
 
Fixed it

 

Thanks for that. I redid the NVCleanInstall but ran into some issues with it failing the GPU driver install the second time (even when choosing the NVCleaninstall's Clean Installation option), requiring a DDU. I did get it installed with both Nvidia HD Audio device sleep timer disabled as well and enabling the Message Signaled Interrupts (the audio drops when selecting different browser tabs or alt tabbing sounded like this option may help with that as well).
 
Man, third party software devs fixing Nvidia's problems in 2024... yeah... (so far, so good - going to test this for a couple of days)
 
Edit - so far so good, but LatencyMon still shows a very high latency after letting it run for a while (this is with Soundkeeper not running).

Which browser?
 
Test ---> turn Off Hardware acceleration for Browser

Cool GTX
Which browser?
 
Test ---> turn Off Hardware acceleration for Browser

I've done that in the past to fix Nvidia driver issues. This time, it seems like both Soundkeeper and NVCleaninstall, with Nvidia HD Audio device sleep timer disabled as well and enabling the Message Signaled Interrupts, seems to fix Dolby Atmos going robotic or completely dropping out. I've gotten two, second long audio drop outs so far - but that was just when alt tabbing or swapping browser tabs. If that's the worst, then it's acceptable compared to needing to disable the receiver in windows sounds or power cycling the receiver to get Dolby Atmos working again.
 
If the audio goes robotic, or completely drops out - I'll try with hardware acceleration disabled in Brave. Until then, I'm happy with the results so far, and I appreciate your help.

arestavo

Cool GTX
Which browser?
 
Test ---> turn Off Hardware acceleration for Browser

I've done that in the past to fix Nvidia driver issues. This time, it seems like both Soundkeeper and NVCleaninstall, with Nvidia HD Audio device sleep timer disabled as well and enabling the Message Signaled Interrupts, seems to fix Dolby Atmos going robotic or completely dropping out. I've gotten two, second long audio drop outs so far - but that was just when alt tabbing or swapping browser tabs. If that's the worst, then it's acceptable compared to needing to disable the receiver in windows sounds or power cycling the receiver to get Dolby Atmos working again.
 
If the audio goes robotic, or completely drops out - I'll try with hardware acceleration disabled in Brave. Until then, I'm happy with the results so far, and I appreciate your help.

Just a quick follow up:
 
I've found using Soundkeeper with the "all" argument to work better for me. Installing a new driver with NVCleaninstall after already completing it once requires me to first use DDU with the options that I use (Nvidia HD Audio device sleep timer disabled as well and enabling the Message Signaled Interrupts), and it also requires me to unplug my DP to HDMI adapter (for sound) to get video out to the TV to get safe mode set (due to DP now taking precedent over HDMI, it started with the 30 series IIRC). The NVCleaninstall method does work, it just takes that much more effort for me vs having a program run at startup.
 
Again, thanks to all that contributed. Hopefully if anyone has similar issues in the future (or now), they'll find that these two methods work for their Dolby Atmos problems.

Thanks for the update, I'm sure it can help others
 
I would like to suggest that you edit your first Post & include some = Tag your post: (bottom of screen)
 
That will help others find the solution, if / when they have a similar issue