Steps to reproduce:
Have your audio device configured to grant WASAPI "exclusive mode".
Start an app that can use exclusive mode, such as foobar2000.
While you're playing something in exclusive mode, also do something that will generate speech.
When you stop the playback, when NVDA should make sounds, the error sound plays.
This is not synth dependent, tested with OneCore and ESpeak.
It is a rare issue, so in my opinion not high priority, but attempting to fix it might improve the audio stability.
Actual behavior:
Error sound plays, whatever action you make.
Expected behavior:
Speech should resume as normal.
NVDA logs, crash dumps and other attachments:
NVDA log attached.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
Latest alpha (but has had the same behavior since the change to WASAPI).
Windows version:
Windows 11 23H2
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes, has been present since WASAPI was introduced
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
nvda-wex.log
Steps to reproduce:
Have your audio device configured to grant WASAPI "exclusive mode".
Start an app that can use exclusive mode, such as foobar2000.
While you're playing something in exclusive mode, also do something that will generate speech.
When you stop the playback, when NVDA should make sounds, the error sound plays.
This is not synth dependent, tested with OneCore and ESpeak.
It is a rare issue, so in my opinion not high priority, but attempting to fix it might improve the audio stability.
Actual behavior:
Error sound plays, whatever action you make.
Expected behavior:
Speech should resume as normal.
NVDA logs, crash dumps and other attachments:
NVDA log attached.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
Latest alpha (but has had the same behavior since the change to WASAPI).
Windows version:
Windows 11 23H2
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes, has been present since WASAPI was introduced
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
nvda-wex.log