Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- From: "Max Paklin" <mpaklin@xxxxxxxxxxx>
- Date: Mon, 23 May 2005 10:05:13 -0700
Just to add to what Tim said.
What you usually do is your declare your driver as supporting all media
types that it can possibly support at any given time. And then you reduce
that list by rejecting certain types that are NOT to be supported at a
particular point from KSPIN_DISPATCH::SetDataType, KSPIN_DISPATCH::Create
and KSPIN_DESCRIPTOR_EX::IntersectHandler callbacks.
-- Max.
"Tim Roberts" <timr@xxxxxxxxx> wrote in message
news:f5h29150bs09s45ee4df3j1rioqg1lsjn5@xxxxxxxxxx
> yinmun <yinmun@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>>Hi Tim,
>>
>>Thanks for spotting the mistake =) Indeed after returning the buffer size,
>>I
>>now managed to display the property dialog box, but the format range still
>>can't be read properly, as all the fields in the dialog box are empty.
>>
>>I'm supporting this property as if I load the driver using GraphEdit, and
>>right-click on the pin to display the Pin Properties to change its
>>streaming
>>format, the AVStream will query this property.
>>
>>Have you tried displaying the format dialog box in GraphEdit without
>>supporting this property explicitly? If so, how did you do it?
>
> The KSDEVICE_DESCRIPTOR for the whole driver includes a pointer to the
> KSFILTER_DESCRIPTOR for the filters in the driver, which includes a
> pointer
> to the KSPIN_DESCRIPTOR_EX for the pins in that filter, which includes a
> pointer to the KSDATARANGES that the pin supports. The
> KSDEVICE_DESCRIPTOR
> is passed to AVStream in KsInitializeDriver, and from that, AVStream knows
> how to find the dataranges and display them in a dialog.
>
> The data structures are 75% of the work in an AVStream driver.
> --
> - Tim Roberts, timr@xxxxxxxxx
> Providenza & Boekelheide, Inc
.
- References:
- Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream.
- From: yinmun
- Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream.
- From: Tim Roberts
- Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- From: yinmun
- Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- From: Tim Roberts
- Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- From: yinmun
- Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- From: Tim Roberts
- Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- From: yinmun
- Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- From: Tim Roberts
- Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream.
- Prev by Date: Re: How to implement IBDA_SignalStatistics in a BDA tuner?
- Next by Date: Re: usb priority question
- Previous by thread: Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- Next by thread: Re: Supporting KSPROPERTY_PIN_CONSTRAINEDDATARANGES under AVStream
- Index(es):
Relevant Pages
|