[wdmaudiodev] Re: AVStream Renderer

  • From: Waldemar Haszlakiewicz <waldemar.haszlakiewicz@xxxxxxxx>
  • To: "John D. Farmer" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Tue, 23 Mar 2004 17:54:26 +0100

Well this part looks correct, but this shows very little -> do you have bridge 
pin,
is the topology correct,.....,is FilterDescriptor correct,......

Anyway 1 little mistake and system can refuse to show the pin.
Again -> go through every structure and check everything 3 times.
Another thing you said you have problems with inf file also ->
you can use KsCreateFilterFactory to register the channels -> don't forget to 
register
KSCATEGORY_AUDIO, KSCATEGORY_RENDER (and KSCATEGORY_CAPTURE if you have capture 
pin).

Waldemar


JDF> I've set those flags in my pin descriptor... Here is the following code:

JDF> {       // Pin 0 - Audio Rendering Pin
JDF>         &AudioPinDispatch,                                   // Dispatch
JDF>         NULL,                                                       //
JDF> Automation Table
JDF>         {                                                                 
//
JDF> Pin Descriptor
JDF>             SIZEOF_ARRAY(PinInterfaces),                     // Interface
JDF> Count
JDF>             PinInterfaces,
JDF> // Interfaces
JDF>             SIZEOF_ARRAY(PinMediums),                      // Medium Count
JDF>             PinMediums,
JDF> // Mediums
JDF>             SIZEOF_ARRAY(PinAudioFormatRanges),     // Data Range Count
JDF>             PinAudioFormatRanges,                                    // 
Data
JDF> Ranges
JDF>             KSPIN_DATAFLOW_IN,                              // Data Flow
JDF>             KSPIN_COMMUNICATION_SINK,            // Communication
JDF>             &PINNAME_KSCATEGORY_AUDIO,        // Name
JDF>             &KSCATEGORY_AUDIO,                            // Category
JDF>             0
JDF> // Reserved
JDF>         },
JDF>         KSPIN_FLAG_RENDERER |
JDF>         KSPIN_FLAG_FRAMES_NOT_REQUIRED_FOR_PROCESSING,     // Flags
JDF>         1,
JDF> // Instances Possible
JDF>         1,
JDF> // Instances Necessary
JDF>         NULL,
JDF> // Allocator Framing
JDF>         AudioIntersectHandler
JDF> // Intersect Handler
JDF>     }
JDF> }

JDF> Where PINNAME_KSCATAGORY_AUDIO is STATIC_KSCATEGORY_AUDIO.
JDF> ----- Original Message -----
JDF> From: "Waldemar Haszlakiewicz" <waldemar.haszlakiewicz@xxxxxxxx>
JDF> To: "John D. Farmer" <wdmaudiodev@xxxxxxxxxxxxx>
JDF> Sent: Tuesday, March 23, 2004 1:24 AM
JDF> Subject: [wdmaudiodev] Re: AVStream Renderer


>> There is a flag that you have to set in pin struct -> KSPIN_FLAG_RENDERER,
>> but there may be other things too -> like KSPIN_DATAFLOW_IN and
>> KSPIN_COMMUNICATION_SINK.
>>
>> Anyway read about the flags in DDK and define them correctly.
>> Another thing recheck every struct 3 times that everything is correct.
>>
>> Peace
>> Waldemar
>>
>>
>> JDF> I am trying to create a AVStream Minidriver Audio Renderer.  I have
JDF> based what I have so far
>> off of the AVSSAMP sample from the DDK, I have taken out most of the video
JDF> stuff and implemented the
>> audio stuff.  The problem I am having is that I can't seem to setup the
JDF> audio pin as a rendering
>> pin.  I want to have it show up as a Audio Renderer in GraphEdit instead
JDF> of a WDM Streaming Capture
>> Device that it currently shows up as.  I've looked at the MSVAD sample,
JDF> and its helped some, but I
>> cannot seem to divine its secrets from the code or its INF.  I know that
JDF> MSVAD is a PortCls driver,
>> but it seems to be the only example I can find that actually shows up in
JDF> the Audio Renderers
>> category in MSVAD.  I've tried different Categories Types, Node Types, Pin
JDF> Types, and Topology
>> Types.  I am rather confused as to what makes a renderer a renderer.
JDF> Could someone please enlighten
>> me?
>>
>> JDF> Any help would be appreciated.
>>
>> JDF> John Farmer
>>
>> ******************
>>
>> 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/
>>
>>
JDF> ******************

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

JDF> URL to WDMAUDIODEV page:
JDF> 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: