[wdmaudiodev] Re: Excessive AVStream Driver Filter Creation

  • From: Eugene Muzychenko <reg.wad@xxxxxxxxxxxxxx>
  • To: Gary Daniels <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Tue, 6 Aug 2019 22:58:56 +0200

Hello Gary,

With the current insiders build, it will only process the
endpoint(s) associated to the interface that changed state.

Another problem with Audio Endpoint Builder is that it may issue
hundreds of KSPROPERTY_PIN_PROPOSEDATAFORMAT requests to determine
number of channels actually supported for every data range reported by
the driver.

Currently, KSDATARANGE_AUDIO allows to report only a maximal number of
channels supported. Therefore, if the driver supports only 8 channels,
it must return 8 as the maximum. If the driver supports a very wide
range of sampling rate (for example, 8000..192000) and bitness (for
example, 8..32) Audio Endpoint Builder issues dozens of proposed
format requests to query particular SR/BPS supported by the driver,
and must query each combination for 1, 2, 4 and 6 channels.
Eventually, total number of requests can reach hundreds.

Maybe it makes sense to extend the structure by the MinimumChannels
field (naming it, for example, KSDATARANGE_AUDIO_EX), so the driver
might correctly report all supported ranges in
KSPROPERTY_PIN_DATARANGES/KSPROPERTY_PIN_DATAINTERSECTION requests.

Regards,
Eugene

******************

WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:    mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:  mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator:    mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx

URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/

Other related posts: