I'm playing around with avshws to learn AVStream. avshws shows up in the
"WDM Streaming Capture Devices" category in GraphEdit. I'd like the driver
to appear in "Video Capture Sources" as well. I have some ideas as to how
this might be done, but I'd like to get a deeper understanding. Any info is
appreciated.

AMCap only enumerates CLSID_VideoInputDeviceCategory devices, as do most
capture apps that I'm aware of. What logic determines which categories a
video capture card should belong to? What is the difference between
CLSID_VideoInputDeviceCategory and AM_KSCATEGORY_CAPTURE?

Re: AVStream avshws DDK example by Max

Max
Mon Mar 01 01:47:29 CST 2004

> I'm playing around with avshws to learn AVStream. avshws shows up in the
> "WDM Streaming Capture Devices" category in GraphEdit. I'd like the
driver
> to appear in "Video Capture Sources" as well. I have some ideas as to how
> this might be done, but I'd like to get a deeper understanding. Any info
is
> appreciated.

You can't do this for SWENUM drivers. It can appear under single category.
If you are writing device driver for a "real" hardware device, then you
should be able to register you driver under any category or under multiple
categories.

Check out ATI All-in-Wonder sample in DDK.


> AMCap only enumerates CLSID_VideoInputDeviceCategory devices, as do most
> capture apps that I'm aware of. What logic determines which categories a
> video capture card should belong to? What is the difference between
> CLSID_VideoInputDeviceCategory and AM_KSCATEGORY_CAPTURE?

CLSID_VideoInputDeviceCategory is for "legacy" devices. Originally all
Video-for-Windows devices went under this category (mapped with VFW mapper,
of course).
New KS devices should register themselves under AM_KSCATEGORY_CAPTURE, but
for compatibility reasons they also appear under
CLSID_VideoInputDeviceCategory as some applications try
CLSID_VideoInputDeviceCategory only.

-- Max.