[wdmaudiodev] Re: AVStream and Wave Devices
- From: Sam Tertzakian <saekisam@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Fri, 7 Oct 2005 12:38:02 -0700 (PDT)
Oh, that problem...I see...
I will try try this later tonight and let you know.
Thank you for the response...and clarification...I
almost missed that.
--- Richard Fricks <Richard.Fricks@xxxxxxxxxxxxx>
wrote:
> To clarify, Mitchell is referring to the issue where
> your device is not
> showing up under vista and not the bus problem.
>
> -Rich
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf
> Of Sam Tertzakian
> Sent: Friday, October 07, 2005 11:23 AM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: AVStream and Wave Devices
>
> Hi, Mitchell,
>
> If you are talking about the Wave device issue, the
> cause has been resolved...and it is not due to the
> audio stack. It is caused by the underlying bus
> driver
> not responding properly to Kernel Mode Requests from
> SysAudio for device arrival/removal events. For this
> reason, SysAudio aborts creating the device. The
> MSFT
> team responsible for that bus now knows about this
> issue and I am sure it will be corrected in the near
> future.
>
> Thank you for your comments, however...
>
> --- Mitchell Rundle <mitchr@xxxxxxxxxxxxx> wrote:
>
> > Sam and Jeff, what are the categories of the
> bridge
> > pins that represent
> > the inputs and outputs (e.g. speakers, lineout,
> mic,
> > etc.) on your
> > topology filter?
> >
> > We now look at these and create different kinds of
> > "endpoint" devices
> > for these. Wave devices ultimately map to
> > endpoints. In order to show
> > up, the bridge pins need to be one of the
> following
> > types:
> >
> > "External Endpoint Devices" (Things the typical
> user
> > is probably
> > familiar with)
> > KSNODETYPE_SPEAKER
> > KSNODETYPE_MICROPHONE
> > KSNODETYPE_PERSONAL_MICROPHONE
> > KSNODETYPE_MICROPHONE_ARRAY
> > KSNODETYPE_LINE_CONNECTOR
> > KSNODETYPE_HEADPHONES
> > KSNODETYPE_DIGITAL_AUDIO_INTERFACE
> > KSNODETYPE_SPDIF_INTERFACE
> >
> > "Internal Endpoint Devices" (Abstract or exists as
> > an ATAPI jack inside
> > the PC case)
> > KSNODETYPE_ANALOG_CONNECTOR
> > KSNODETYPE_CD_PLAYER
> >
> > We are considering expanding this list somewhat to
> > better accommodate
> > things like headsets, phones, etc.
> >
> > It looks like a whitepaper on this subject is
> > overdue...
> >
> > Let me know if this fixes things or not. If not,
> I
> > will try to track
> > down the device and take a look at.
> >
> > Regards,
> >
> > Mitch Rundle
> > Windows Media Devices Group
> > Microsoft Corp.
> >
> > This posting is provided "AS IS" with no
> warranties,
> > and confers no
> > rights.
> >
> >
> >
> > -----Original Message-----
> > From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> > [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On
> Behalf
> > Of Sam Tertzakian
> > Sent: Thursday, October 06, 2005 5:04 PM
> > To: wdmaudiodev@xxxxxxxxxxxxx
> > Subject: [wdmaudiodev] Re: AVStream and Wave
> Devices
> >
> > I have WHQL certified audio driver that works
> > perfectly under 2k and XP
> > (PortCls). However, under Longhorn, it fails to
> > create a Wave device.
> > MSFT has my device and drivers and some developers
> > are scheduled to
> > investigate why that is happening.
> > Perhaps they will find something interesting in
> > corrected it, or perhaps
> > I am doing something under XP that I should not be
> > doing, but works
> > anyway.
> > It has been over two months now...and Richard
> Fricks
> > told me that if the
> > developers don't get to it soon, then he will look
> > at it.
> >
> > But, I am getting worried that we are getting so
> > close to the final
> > release and this problem still exists.
> >
> > Like your device, I also regiester multiple
> > subdevices.
> >
> >
> > --- Jeff Pages <jeff@xxxxxxxxxxxxxxxx> wrote:
> >
> > > Matt,
> > >
> > > You mentioned that Windows Vista will use the
> > friendly names of the
> > > pins to identify devices. I'm having a lot of
> > grief with Vista Beta 1
> > > and our multi-channel sound cards. Each channel
> on
> > the card is
> > > registered as a separate input, output and
> > topology subdevice, as
> > > described in the DDK under "Multiple Audio
> > Subdevices", and under all
> > > current OSs these appear as separate waveIn,
> > waveOut and Mixer
> > > devices, but under Vista it tries to make them
> all
> > one device with
> > > multiple source and destination pins. This is a
> > big problem as
> > > applications using our cards need to open
> multiple
> > subdevices
> > > simultaneously.
> > >
> > > Am I going to have to write a buss driver and
> > implement the multiple
> > > subdevices that way under Vista, or is there
> > another way around this?
> > >
> > > The Vista Beta 1 WDK documentation on "Multiple
> > Audio Subdevices" and
> > > "Kernel Streaming Topology to Audio Mixer API
> > Translation" is
> > > unchanged from the previous DDK documentation,
> so
> > I was wondering if
> > > this changed behaviour of Vista is actually
> > documented anywhere?
> > >
> > > Jeff Pages
> > > Innes Corporation Pty Ltd
> > >
> > > ******************
> > >
> > > 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/
> > >
> > >
> >
> > ******************
> >
> > 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/
> >
> > ******************
> >
> > 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/
> >
> >
>
> ******************
>
> 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/
>
> ******************
>
> 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/
>
>
******************
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:
