Does your APO have any dependencies on code running outside of audiodg.exe,
e.g. a user-mode service? If so, this sounds like a race condition between the
audiosrv service starting (which starts the “listen to” audio session) and that
user-mode service starting.
Windows Performance Recorder allows collecting logs during boot.
From: cedric demiere<mailto:cedric.demiere@xxxxxxxxxxx>
Sent: Tuesday, November 26, 2019 3:00 AM
Subject: [EXTERNAL] [wdmaudiodev] APO and "Listen to this device"
We encounter a strange problem in Windows 10 when we use the "listen to this
device" option in sound device properties.
To reproduce the issue with do the following :
- Set-up a 'listen to this device' configuration to a device with an APO.
- Hear that render effect are correctly applied.
- Shutdown the computer then start it.
- On Windows start, the 'listen to this device' is still running but we can't
hear any effect.
This issue is not reproduce when we simply do a restart of the computer.
We ran some tests on our code and we see that our APO can see the stream. if we
disable/enable the "listen to..." again, all work correctly.
Now, we cannot clearly tell if the bug come from our side or Microsoft side.
Does anyone have information about the 'listen to this device' feature ?
Especially if this feature have some limitations or use another 'path' than
classic Windows audio path to render sound.