[wdmaudiodev] Re: AVStream based Capture Filter

  • From: Andy Cao <cao.andy@xxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Tue, 3 Mar 2009 10:37:13 +0800

Hi, Tim
    Thanks for your reply.
    There IS only one Capture pin. The audio data comes from a BDA device.
In my old version, audio/video data different sperate output pin in the same
filter. But some third-party software use "Audio Captrue Sources" DShow
category to capture audio data. So I have to use a different filter to
register the category.

    In GraphEdit, my AudioOuputPin can render and its SetState(KSSTATE_RUN)
is invoked.

2009/3/3 Tim Roberts <timr@xxxxxxxxx>

> Andy Cao wrote:
> > hi
> >       I wrote an AVStream driver and registered it to "Audio Capture
> > Sources" category. But the registered filter display different in
> > KSStdio/GraphEdit from that I declare in my code. And my filter play
> > in GraphEdit, GraphEdit is hung.
> >
> > my filter's pin description is here
> > ...
> >       The KSStudio show only one Capture pin, and tell that the capture
> pin
> > is KSPIN_COMMUNICATION_SINK (not KSPIN_COMMUNICATION_BOTH as I
> > declare).
> >
>
> Well, there IS only one capture pin, right?  You have one fake input pin
> for the analog audio, which is optional (InstancesNecessary==0) and has
> no valid data ranges, and one real capture output pin, which is required.
>
> How far do you get in graphedt?  Does the pin connect?  Do any of the
> state changes happen?
>
> --
> Tim Roberts, timr@xxxxxxxxx
> Providenza & Boekelheide, Inc.
>
> ******************
>
> 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: