Steps to reproduce:
- Set log level to DEBUG
- Perform some actions
- Press NVDA+F1 to open the log
- Press many times upArrow to review the log.
Actual behavior:
The following lines can be found regularly and often in the log:
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:53:43.008) - Dummy-22 (18476):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:53:43.008) - Dummy-22 (18476):
Calling sync on audio player
DEBUG - nvwave.WavePlayer._isPreferredDeviceOpen (10:53:43.008) - MainThread (7200):
preferred device: WAVE_MAPPER current device name: WAVE_MAPPER (id: -1)
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:53:43.008) - Dummy-22 (18476):
Calling idle on audio player
DEBUG - nvwave.WavePlayer._isPreferredDeviceOpen (10:53:43.008) - Dummy-22 (18476):
preferred device: WAVE_MAPPER current device name: WAVE_MAPPER (id: -1)
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:53:43.008) - Dummy-22 (18476):
Queue empty, done processing```
Expected behavior:
The log does not contain so much information regarding audio player so that the log can be read more easily when debugging. Maybe a solution would be to have a specific log option in advanced panel for this type of debug messages.
System configuration
NVDA installed/portable/running from source:
From source
NVDA version:
Last alpha (commit f33664e)
Windows version:
Windows 10
Name and version of other software in use when reproducing the issue:
N/A
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.
2020.2 is OK. These appeared in last alpha only.
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No
Steps to reproduce:
Actual behavior:
The following lines can be found regularly and often in the log:
Expected behavior:
The log does not contain so much information regarding audio player so that the log can be read more easily when debugging. Maybe a solution would be to have a specific log option in advanced panel for this type of debug messages.
System configuration
NVDA installed/portable/running from source:
From source
NVDA version:
Last alpha (commit f33664e)
Windows version:
Windows 10
Name and version of other software in use when reproducing the issue:
N/A
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.
2020.2 is OK. These appeared in last alpha only.
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No