video properties for filter driver

  • Thread starter Thread starter Bogdan Dinu
  • Start date Start date
B

Bogdan Dinu

Hello!

I have to implement a filter driver for a webcam, and I would need to extend
the video filter properties for the device.
In the minidriver I would call KsInitializeDriver with a properly
constructed KSDEVICE_DESCRIPTOR parameter, and let the AVStream do the rest
of the work for the irps I'm not interested in, but unfortunately i do not
have access to the driver and I have to extend the functionality through a
filter driver. I need to add a custom GUID to the Supported Propertysets, to
pass it to KsProxy.

The only way I managed to do this till now is to intercept the
IOCTL_KS_PROPERTY and play with the buffers and sizes to add my GUID to the
return buffer, but this is (very) low level and based on the assumptions. Is
there a way to do this at a higher level?

Thanks
Bogdan D.
 
Thanks.

I have checked the driver (using verifier & others) and it vorks fine. It is
just that I didn't want to go low level because all I do is based on certain
assumptions about where the properties data is stored in the IRP and the
protocol used, and all this functionality really depends on the AVStream
driver microsoft provides. I am looking for a implementation similar to a
avstream minidriver structure, using library functions to change the
properties.
 
Back
Top