How to select WDm device?

[RenHoek]

I've got a Hauppauge PCI WinTV card and an USB webcam. When capturing in VirtualDub for example, I can only use the Microsoft WDM image capture wrapper.

Is there a way to select the device to use instead of having to take out the device that I don't want to capture from?

[Cart]

VirtualDub is a VFW program that only sees the wrapper. Thus, any configuration would have to be done through the wrapper. There may be registry settings that control it, or maybe not.

Is there some reason why you're not using the VFW drivers for your WinTV?

-Cart
http://www.geocities.com/lukesvideo/index.html

[iamsparticuz]

Im going through the same thing. Virtualdub or FlyCap wont let me capture at a resolution higher than 320x240. When i raise it it says "Error out of memory buffers". When i try and raise the resolution in virtualdub, I receive the error "Error 418: Unsupported video format". Its the same no matter what the pixel depth. When I begin to capture using virtual dub I get the error "Error 418: Capture driver improperly installed" and then "Virtualdub cannot connect to the desired capture driver. Trying all availible drivers". It then switches to the WDM image capture and like i said before, i can't raise the resolution past 320x240. I enabled dib draw and I followed the exact instructions here (http://www.hauppauge.com/xp/xpinstall.htm) for installing wintv with xp. Im hoping to hit a couple birds with one stone here too, when using virtual dub and flycap it stays on the same channel no matter what wintv2000's channel is on. I will change it numerous times and flycab&virtualdub will still be on one, and wintv will be on another. Lots of problems. :( :( :confused:

My specs are as follows.

Athlon 1.4 tbird
512 DDR RAM
Asus A7A266
Western Digital 60 gig 7200 rpm
Sound blaster live X-Gamer 5.1
Geforce 3

Any help or suggestions would be much appreciated.

[iamsparticuz]

Ok, i took the first step in fixing it. I downloaded the new drivers from http://btwincap.sourceforge.net/ and I captured using flycap fine. I still have the channel problem. I couldn't find any support from btwincap. I can use the included software "amcap" and change channels great, but when I go to virtual dub or flycap it is still on the original channel(Channel 4 I believe.) Then when I go back to amcap its on the channel before I changed it.

plz help

[iamsparticuz]

Some1 plz help, i dont see how no1 else has ever had this problem with a capture card that has been out for longer than 2 years and is one of the most popular. Ive spent the past 12 hours trying to fix these problems, some1 plz help. I've tried everything and looked everywhere.

[morsafr]

Don't panic :). Here what to do if you use VDub (don't know FlyCap) with the Btwincap driver.
Just launch the capture module as usual. Effectively you are stuck with the damned channel 4 !
In the "video" menu, go to "Source" and on the first panel you will see the magic button "TV Tuner". Just click on it and proceed as usual ;).

[iamsparticuz]

OMG THANK YOU SOO MUCH. I wouldve been looking for countless more hours just for something that simple. Thank YOU!

[tiki4]

Something else here:

You should know how to change the channel you are capturing from in VirtualDub. The btwincap drivers are great for capturing in any DirectShow based program. I wonder that the wrapper is working correctly in VirtualDub because you usually are not able to capture above the mentioned 320x240 with WDM drivers and Hauppauge WinTV boards (that's my experience with an WinTV PCI). There is however a drawback with the btwincap drivers: The Hauppauge WinTV 2K application does not work any more (at least for me).
Something I tried was to stick with the original WDM driver from Hauppauge and use another application for capturing. Take a look at:

http://www.digtv.ws

The application VirtualVCR there has worked well for me. The author claims that capturing through WDM drivers is much faster than the old VfW interface. I didn't see that on my Win2K box, so I sticked with the VfW drivers.

bye,

tiki4