[wdmaudiodev] Re: Forcing system to use Pin names

  • From: Waldemar Haszlakiewicz <waldemar.haszlakiewicz@xxxxxxxxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Tue, 25 Mar 2003 13:18:27 +0100

Thanks.
That cleared a lot.

Waldemar


MR> There are 3 ways that you can support "multiple stereo pins".  Each
MR> method will have a different result.

MR> 1) Multiple filters, each with a single stereo pin:  This will be
MR> exposed as multiple devices in both the MME Wave API, and the
MR> DirectSound API.
MR> 2) A single filter with multiple stereo pins:  This will show up as a
MR> single device in both the MME Wave and Dsound APIs.
MR> 3) A single filter with a single stereo pin that supports > 1 possible
MR> instance:  This will show up as a single device in both APIs, but you
MR> will get multiple secondary Dsound buffers.

MR> Mitch Rundle
MR> Microsoft

MR> This posting is provided "AS IS" with no warranties, and confers no
MR> rights.

MR> -----Original Message-----
MR> From: Waldemar Haszlakiewicz
MR> [mailto:waldemar.haszlakiewicz@xxxxxxxxxxxxxxx]=20
MR> Sent: Thursday, March 20, 2003 4:05 PM
MR> To: wdmaudiodev@xxxxxxxxxxxxx
MR> Subject: [wdmaudiodev] Forcing system to use Pin names



MR> Hi everyone

MR> We are writing a multi-stereo-channel AVStream driver and we have come
MR> across a problem.

MR> 1st: Is there a way to force the system to use pin names instead of
MR> interface one. The thing is that even if we have set multiple in/out
MR> pins in KSPIN_DESCRIPTOR_EX the system recognizes only the ch. 1-2. That
MR> is logical as the system is still using the interface name and with that
MR> only ch. 1-2.

MR> Our wishes:
MR> We would like to create only 1 filter which would support multiple
MR> (stereo) pins.

MR> Filter(interface) is registered to KSCATEGORY_AUDIO, KSCATEGORY_RENDER
MR> and KSCATEGORY_CAPTURE.


MR> Waldemar

MR> ******************

MR> WDMAUDIODEV addresses:
MR> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
MR> Subscribe:    =
MR> mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dsubscribe
MR> Unsubscribe:
MR> mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dunsubscribe
MR> Moderator:    mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx

MR> URL to WDMAUDIODEV page:
MR> http://www.wdmaudiodev.de/

MR> ******************

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

MR> URL to WDMAUDIODEV page:
MR> http://www.wdmaudiodev.de/

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

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.de/

Other related posts: