Steps to reproduce:
- Run an alpha snapshot that uses WASAPI by default, on a system running Windows 10 or below (Windows 11 does not exhibit this problem).
- Set the system to automatically go to sleep in power options if this isn't already done.
- Wait for the system to enter sleep mode.
Actual behavior:
Actual result: If using WASAPI, the system does not enter sleep mode, but it does enter sleep mode if WASAPI is disabled.
Expected behavior:
Expected result: NVDA should allow the system to enter sleep mode automatically if this is set, regardless of whether NVDA is set to use WASAPI or not.
I rely on the system being able to automatically enter sleep, and this could also cause confusion for others if they set the system to sleep and then find that the system isn't going to sleep. Therefore, as a last resort, I would prefer to have WASAPI disabled by default if the OS is anything less than Windows 11 so that this issue would not present itself unless someone specifically enables WASAPI. Again, Windows 11 does not exhibit this issue. Presumably all versions of Windows before Windows 11 are impacted.
NVDA logs, crash dumps and other attachments:
I cannot seem to find anything in the log related to audio. I also ran a portable version of NVDA to try and get a log, and I could not locate the NVDA log file in the portable version (I ran with debug level logging then restarted in the hope that I would get an NVDA_Old.log file but I could not find one.
System configuration
NVDA installed/portable/running from source:
Temporary copy (running an alpha snapshot from the launcher) as well as a portable version later to try and get a log.
NVDA version:
alpha-28193,d1ce3bc9 (2023.2.0.28193)
Windows version:
Windows 10
Name and version of other software in use when reproducing the issue:
None
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.
This is not applicable as no other NVDA versions support WASAPI and thus do not exhibit this behavior.
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?
Yes.
Steps to reproduce:
Actual behavior:
Actual result: If using WASAPI, the system does not enter sleep mode, but it does enter sleep mode if WASAPI is disabled.
Expected behavior:
Expected result: NVDA should allow the system to enter sleep mode automatically if this is set, regardless of whether NVDA is set to use WASAPI or not.
I rely on the system being able to automatically enter sleep, and this could also cause confusion for others if they set the system to sleep and then find that the system isn't going to sleep. Therefore, as a last resort, I would prefer to have WASAPI disabled by default if the OS is anything less than Windows 11 so that this issue would not present itself unless someone specifically enables WASAPI. Again, Windows 11 does not exhibit this issue. Presumably all versions of Windows before Windows 11 are impacted.
NVDA logs, crash dumps and other attachments:
I cannot seem to find anything in the log related to audio. I also ran a portable version of NVDA to try and get a log, and I could not locate the NVDA log file in the portable version (I ran with debug level logging then restarted in the hope that I would get an NVDA_Old.log file but I could not find one.
System configuration
NVDA installed/portable/running from source:
Temporary copy (running an alpha snapshot from the launcher) as well as a portable version later to try and get a log.
NVDA version:
alpha-28193,d1ce3bc9 (2023.2.0.28193)
Windows version:
Windows 10
Name and version of other software in use when reproducing the issue:
None
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.
This is not applicable as no other NVDA versions support WASAPI and thus do not exhibit this behavior.
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?
Yes.