Is your feature request related to a problem? Please describe.
The advanced settings GUI of NVDA is packed with some settings that are already widely tested by the community and per policy should not appear under advanced settings or in the GUI at all since their default behavior should not be changed by the user. Letting these hard settings changeable overcomplicates investigations especially when most significant issues were already fixed and the community already tested most use cases.
This applies also for use WASAPI setting, in most cases we have to find out who has manually changed this setting and who not. My understanding if the original implementation is that The users are expected to use WASAPI by default without being able to change it.
Describe the solution you'd like
Remove the "use WASAPI for audio output" setting from the GUI and enforce WASAPI to enabled for everyone.
Describe alternatives you've considered
Leave as is but we will never be able to discover all the issues that come with WASAPI since many people might use both and switch back and forth to compensate for issues deriving from WASAPI or nvWave. For true testing we should remove this setting completely from the GUI.
cc: @jcsteh what do you think? Are any drawbacks which come from only using WASAPI?
Is your feature request related to a problem? Please describe.
The advanced settings GUI of NVDA is packed with some settings that are already widely tested by the community and per policy should not appear under advanced settings or in the GUI at all since their default behavior should not be changed by the user. Letting these hard settings changeable overcomplicates investigations especially when most significant issues were already fixed and the community already tested most use cases.
This applies also for use WASAPI setting, in most cases we have to find out who has manually changed this setting and who not. My understanding if the original implementation is that The users are expected to use WASAPI by default without being able to change it.
Describe the solution you'd like
Remove the "use WASAPI for audio output" setting from the GUI and enforce WASAPI to enabled for everyone.
Describe alternatives you've considered
Leave as is but we will never be able to discover all the issues that come with WASAPI since many people might use both and switch back and forth to compensate for issues deriving from WASAPI or nvWave. For true testing we should remove this setting completely from the GUI.
cc: @jcsteh what do you think? Are any drawbacks which come from only using WASAPI?