Windows not sending 'KSCATEGORY_AUDIO' notification for audio devices about directxtk HOT 6 CLOSED

Thanks for the follow-up. All audio devices are supposed to use KSCATEGORY_AUDIO as well, so maybe it's a driver bug?

What driver is it?

from directxtk.

Realtek High Definition Audio, version 6.0.8945.1

from directxtk.

Are you using the default audio device when creating the XAudio2 mastering graph, or are you enumerating a specific device?

from directxtk.

I have confirmed that this is a driver bug.
Since uninstalling the Realtek HD Audio Driver and reverting back to the standard Windows 10 driver solves this problem (still a realtek driver, but the one that ships with Windows), it sends an KSCATEGORY_AUDIO as expected.
But once the Realtek HD Audio Driver (tested versions: 6.0.9225.1, 6.0.8945.1) is installed, it no longer receives it, and instead starts receiving DEVINTERFACE_AUDIO_RENDER.

Proposition:
Since this bug might affect other systems causing inconsistent behaviour based on the audio driver, I suggest to also register notifications for DEVINTERFACE_AUDIO_RENDER so that even systems with an audio driver with this behaviour can get notifications as expected.

from directxtk.

Thanks for the follow-up.

If you use the default device for XAudio2 instead of enumerate a specific device, on Windows 10+ you won't actually get a graph error for changing end-points as OnCriticalError. This relies on WASAPI virtualized client. In that case, you don't really need this notification.

from directxtk.

Yes, it is best to handle this using Audio apis rather than rely on WM_DEVICECHANGE.
Anyways, I hope this issue will be helpful to anyone that runs into this bug as I couldn't find anything about it.

from directxtk.