[wdmaudiodev] Re: Other strangeness in PortCls and AudioDG
- From: Eugene Muzychenko <reg.wad@xxxxxxxxxxxxxx>
- To: Matthew van Eerde <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Fri, 7 Sep 2018 10:31:44 +0200
The developer’s theory is that you are updating the
KSPROPERTY_RTAUDIO_BUFFER_WITH_NOTIFICATION implementation and then
replacing the .sys file, rather than uninstalling and reinstalling
the audio driver. This causes the audio service’s cached state to be
incorrect for the new version of your driver.
Yes, I just replace driver file and restart the driver in a debugging
process, if there were no changes in supported property sets and/or
property values in the Registry.
Can you try uninstalling your driver and reinstalling it?
Of course, reinstallation fixes the behavior. But a driver might
change buffer size requirements on run time, depending on device's
state, protocol settings etc. Using
DEVPKEY_KsAudio_PacketSize_Constraints requires to re-enabling the
interface and rebuild endpoint cache.
BTW, why Microsoft started to prefer registry properties over
filter/pin property sets? A property request can be issued anytime to
obtain current device/driver state and/or requirements/constraints.
AudioDG might issue an appropriate request before allocating the
buffer, and no "alignment dance" would be needed.
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
Other related posts: