Virtual video capture device driver
- From: "rep_movsd" <rep.movsd@xxxxxxxxx>
- Date: 3 Jan 2006 23:44:10 -0800
Hi
I need to develop a Virtual video capture device, I have so far used a
normal directshow source filter registered under
CLSID_VideoInputDeviceCategory, but several apps fail to recognize it
as a genuine capture device even though AMCAP and WM encoder do so.
So I have decided to write a device driver instead.
Since I have no experience with driver development, I realize that my
best chance of success lies in using the existing samples from MS and
modifying them to suit my requirement.
I have found the following to be viable :
1) The avssamp sample driver
2) The avshws sample driver
3) the TestCap sample
The testcap thing works out of the box simulating a tv tuner, but
theres an awful lot of code in there and it looks forbiddingly
difficult to modify.
The avssamp and avshws seem more manageable , but they register
themselves as "WDM streaming Video Capture" devices and are not
recognized by any app as a capture device, though they work fine in
Graphedit.
Now I have some questions :
1) Can I make the avssamp filter get registered as a normal capture
device?
2) How do i see the output of the DbgPrint and KdPrint functions ?
3) Would it be more simple to write a VFW driver instead?( I read
somewhere that they can be simple user mode DLLs exporting a function
called DriverProc() ) If so where can I get more info on this?(Google
seems to be silent on this one)
Any suggestions are welcome.
Thanks in advance
Vivek
.
- Follow-Ups:
- Re: Virtual video capture device driver
- From: Max Paklin
- Re: Virtual video capture device driver
- Prev by Date: Re: I/O Request processing
- Next by Date: Re: Help wanted for video driver.
- Previous by thread: I/O Request processing
- Next by thread: Re: Virtual video capture device driver
- Index(es):
Relevant Pages
|
