Capturing with VDUB limited only to 252x288

[wpeter01]

I have a problem capturing with VDUB. In general the SW is working well but I am limited to 352 x288. Each time I want to increase the resolution I got the message"Not supported resolution." It does not matter which codec I am using Huffy, uncompressed, Microsoft..... On the other hand I am able to capture with Ulead Video Studio and my WinTV application of my WIN TV GO card even at higher esolutions. I do not understand this situation. Any advise for me???

By the way my machine is a 1300 MHz AMD Duron and I am running WIN 2K, but anyway this problem is not related to my HW, I am almost sure.
Any suggestions would be welcome.

[wpeter01]

Just as additional information I tried the BT driver, but my chipset is based on the BT88x and the driver available are for BT848 and878. Both do not work properly in my system. Any help would be appreciated.

Werner

[easydvd]

still sounds like a driver problem to me. Are the ones you're using VFW or WDM? VFW ( video for windows ) used to give me that problem, although the sourceforge ones worked with my chipset Look around for some new drivers and I would think your problem can be solved like that

[snowmoon]

Try the following.

1) Turn off overlay and turn on preview. Then try setting the resolution to 640x480.

2) Make sure that your drivers are updated

3) Try the http://btwincap.sourceforge.net/ drivers to see if they work any better.

[wpeter01]

@snowmoon

How have you installed the btwincap driver. Have you deinstalled first the old one. I know there is an option delete the old driver, but when I tried it I can still find the Haupauge TV driver in the device manager. Do I have to delete those first??

By the way: VDUB shows me that the Miscrosoft WDM driver is active.

[pethu]

I suffer the same problems, and came across the following info in the tweaked WDM driver FAQ:

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.

Drat! I really, REALLY want to capture in 288x576 to make some HQ SVCDs...

[liquid217]

just a simple heads up, but i thought i would add my 2 cents. the wrapper does in fact support interlace. I have capped at 720x480 at 29.97 fps with no trouble at all. I suggest you follow snowmoons suggestion, this should do the trick.

[pethu]

First off, a solution that works in Windows/XP with my default drivers: iuVCR can capture in 352*576 without any problems! That could be worth $25 after 30 days trial... It has a on-timer function to, which I think is lacking in VirtualDub...?

On the topic of new drivers, theres is a problem (evidently well-known amongst manufacturers and Microsoft) with video capture WDM drivers in XP that makes them a nightmare to install for at least some cards. For the Pinnacle PCTV, I tried installing both the tweaked bt848 and the btwincap drivers with the same disastruous result: The Card is no longer recognised but listed as "unknown" with no appropriate drivers, with two new capture devices installed that don't correspond to any real gardware!
As a result, not a single function is available until the original drivers are re-installed... This works the same whether you use the driver installers, or try to "update drivers" for existing hardware... Yuck!

[CauCauCau]

First off, a solution that works in Windows/XP with my default drivers: iuVCR can capture in 352*576 without any problems! That could be worth $25 after 30 days trial... It has a on-timer function to, which I think is lacking in VirtualDub...?

VDStart - Check the tools section to the left.