tweaked WDM Drivers: BTwincap or iulab.com

[Malcolm]

i'm using BTwincap drivers for my BT878 card for some time now. they work perfectly except, that i can't go to powersave mode with WinXP.

I've just found out that there are also tweaked BT8x8 WDM drivers from www.iulab.com (http://www.iulab.com/) (iuVCR) too. They claim, that the drivers are fully ACPI compliant.
Has anyone tested these drivers? Are they any good? Better than the BTwincap drivers?

thanks,
Malcolm

[famawizard]

I use them and on my system with Pinnacle PCTV RAVE they work better (= much faster) than btwincap...but I can't help with powersave mode

Lucio

My sys:
P4 2.6 GHz HT
ASUS P4B800
512Mb
80Gb WD + 60Gb WD
Win XP

[midelic]

Yes,I also use these drivers.
better colors,more details.

[vmesquita]

I've been using BTWinCap for 10 months now (since the drivers that came with my PixelView PlayTV were awful), but never tried iuvcr drivers. I'll give them a try, so I can compare. It's only a pity that, unlike btwincap, source code in not available.

[]'s
VMesquita

[Morpheus_xx]

Is any of the alternative drivers working with radio applications?

I have a hauppauge WinTV with FM tuner and can get it only to work with original drivers...

[vmesquita]

BTWinCap supports FM, but you have to select during instalation. In fact the driver is even able to get mono FM from boards with no FM support! :)

[]'s
VMesquita

[McQuaid]

From their site:

Q8: Why is VirtualDub software unable to capture a frame with more than 288 pixel rows in PAL mode (or 240 pixel rows for NTSC)?

A: VirtualDub, like any other VFW based software, uses a so-called wrapper to translate VFW calls to their counterparts in "DirectShow/WDM world". This slowdowns your PC a bit, and the wrapper grabs only one TV signal field. This results in only 288 lines for PAL/SECAM and 240 lines for NTSC. I think it would be possible to modify their wrapper to solve this problem but unfortunately I do not have the free time and special equipment needed to work on it.


I was under the understanding that btwincap could cap in 480 lines in vdub and avi_io.

Do either of them capture full frame with vdub or avi_io?

[xpavement]

I had been using the btWincap drivers with a Kworld card, and I could get Vdub to capture, but it was a bit buggy at times, so then I unistalled those drivers, and installed the iulab ones when I saw this post. The drivers installed fine, but now I cannot capture in Vdub at all, it just errors out, saying it cannot find a valid device to use. It pops up a list of devices, and I can only select "Conextant Capture", but then it still errors and leaves capture mode. I guess it's having issues with dealing with the wdm-vfw wrapper? I tried removing all my settings from Vdub by using the auxsetup.exe that comes with it, but the problem still remains. I can capture with wdm programs fine for now, but I still miss vdub, even though the wrapper raises the cpu usage during capture. I have been to the vdub forums, I'm just wondering if anyone has any tips or tricks I can try to get Vdub to recognize this device (with these drivers). I'm using winxp pro, and stable 1.5.4 version of vdub.

[midelic]

Forget using drivers from iulab whith virtualdub, cause it's not working under XP(iulab drivers are WDM and virtualdub don't recognize them).
Use instead for capturing ,iuvcr or virtualvcr(free).