Re: Virtual video capture device driver

IMO you are better off to use TestCap. In terms of complexity it is about
the same as avshsw, but it is easier to modify to fit your needs.

VFW capture driver might be your best bet as some people advocate.
Personally I don't like it, but many find it much easier to write as opposed
to doing kernel mode work. See Win95 DDK.

Output of DbgPrint or KdPrint can be captured with DbgView (Google it)
however you will have to get familiar with WinDbg if you are to do any
kernel mode debugging and WinDbg captures the output of those routines as
well.
Read WinDbg help on how to set up and use the debugger.

Overall you are up for a lot of reading in the DDK about what KS is and how
to write a Stream Class or AVStream minidriver.
Then arm yourself with the debugger and step through the code of existing
sample TestCap would be my choice and see what it does and how it works.
After that you should be able to customize it for your needs.

-- Max.



"rep_movsd" <rep.movsd@xxxxxxxxx> wrote in message
news:1136360649.968577.40770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 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
>


.

Relevant Pages

  • Re: BDA AnalogTV tuning examples
    ... have to get some hardware to set up the repro. ... Testcap is a prototypical sample WDM stream class video capture driver ...
    (microsoft.public.win32.programmer.directx.video)
  • [RESEND][PATCH 1/2] v4l2: modify the webcam video standard handling
    ... More generally any capture device, ... * where sequence numbers refer to the frames received by the ... driver, not the captured frames. ...
    (Linux-Kernel)
  • [PATCH 1/2] v4l2: modify the webcam video standard handling
    ... More generally any capture device, ... * where sequence numbers refer to the frames received by the ... driver, not the captured frames. ...
    (Linux-Kernel)
  • Re: Desktop Capture (Vista)
    ... I understood that the composition of whole desktop is dependent on GPU. ... In order to support the screen capture functionlity, ... you should see why a display driver (a mirror driver is ... Catching a snapshot of a single window with a mirror driver, ...
    (microsoft.public.development.device.drivers)
  • Re: Saving Screen Capture
    ... If you allow PrintScr but not Alt+PrintScr, then someone can still capture your pixels. ... it is there so if I download a driver and use it to "steal" what I've ... Note that it is not possible to run ordinary apps in the trusted core, ...
    (microsoft.public.vc.mfc)