Unable to have audio ducking with NVDA

By TheBlindGuy07, 24 February, 2025

Forum
Windows

So I haven't reset my hp laptop since 2023, because I feel so lazy to have my mac when something is really difficult to do there :)
So. I've performed various clean install, real uninstall with manual removal of files after and all that stuff, but whatever the reason is I am simply unable to get audio ducking work on my hp, even with portable versions. It says audio ducking not supported each time, while it was working perfectly fine before. It's of course the same behaviour no matter which tts I use. So. It's not a feature I use often, and I'll reset it eventually anyway. But is there any reason you can think of that may cause the problem, and any fix idea?

Options

Comments

By Brian on Monday, February 24, 2025 - 05:43

Where did you download NVDA from? Did you get it from nvaccess.org? Did you get it from GitHub? Somewhere else?
I want to tell you that I have never heard of audio ducking not working with NVDA, however I have heard of other audio issues depending on certain settings/hardware.

By TheBlindGuy07 on Monday, February 24, 2025 - 06:43

Nvaccess official download page. Yeah I know it's a specific bug as before it was working fine on the same hardware.

By Nut on Monday, February 24, 2025 - 07:43

I noticed this too, while in a Windows 11 vm and also a fresh portable copy I created on my host machine. Both my Windows 11 vm and my host machine are running the same version of Windows 11, version 24H2.

By TheBlindGuy07 on Monday, February 24, 2025 - 21:43

Me too so maybe it's a windows problem? The thing is on my friends computers also win11 it works just fine and so was for me a while ago. In fact on my windows vms on mac it works as well.

By Brian on Tuesday, February 25, 2025 - 00:43

I have no issues with Audio Ducking on my machine. Windows 11, Build 24H2. NVDA Version 2024.4.2.

I have read that audio enhancement applications and/or settings can interfere with NVDA's Audio Ducking. This may or may not be hardware specific.

Could potentially also be an add-on causing a conflict.