Virtual Dub Strange error, help needed ASAP

[Mozzy]

hi there i promised my brother in the US id send some british TV over to him, however im having a wierdproblem while capturing.

im using huffy codec (ive also tried MJPEG and booktree YUV - and they had the same prob, so im thinking its VDUB) and after about 20-30 mins i get an error pop up saying

"AVI Output : The paramiter is incorrect"

after this it stops capturing and the file ive been capturing to becomes useless. however the file is fine if i terminate it normally before this happens.

the thing is the shows are an hour long, has anyone else had this problem and if so how do i get round it?

it is REAAAAAAAAAAAALY bugging me!

thanks for your time

[EBKID]

I think I have a simular issue. I read your mail and have seen no one else reply. I have done a bit more looking and have found some info that might help. Try http://virtualdub.org/docs_capture it got a load of info on problems including.

Why does my video capture stop at 1 hour, 11 minutes, but I still get audio?
This is a bug in many video capture drivers. The exact limit is actually 232 microseconds, or 1 hour, 11 minutes, 34 seconds. Many TV tuner devices are susceptable to this bug, as are the miro/Pinnacle DCxx devices; you may be able to fix the problem simply by upgrading to the latest capture drivers. There are two incarnations of this problem. In the non-fatal version, video frames are still sent to the application, but the timestamp on the video stream starts over from zero. VirtualDub will correct for this problem automatically, allowing you to capture beyond 71 minutes. The other possibility is that the driver stops sending data altogether. VirtualDub will notify you if this occurs, but will not be able to capture past 71 minutes in this case.

Vanilla capture devices based on the Conexant/Brooktree BT848/878 reference drivers are usually either immune to the problem or have the non-fatal form of it. I'm told that the bug in Pinnacle's DC30(+) drivers still exists but is nonfatal as of the 1.41a drivers. As of this writing, the bug in the DC10/10+/20/20+ drivers is fatal and cannot be worked around.

There are apparently a few drivers that are even susceptable to half this limit (35 min.) due to using signed 32-bit arithmetic. VirtualDub does not yet detect or attempt to bypass the 35 minute limit that results.

I'm getting an error when I try to capture an AVI file bigger than 4GB.
You'll get this problem if you either (a) are running Windows 95/98/98SE/ME, or are saving to a FAT32-formatted partition. Either limits you to 4GB. If you want to capture a single file bigger than 4GB, you must have your capture partition formatted as NTFS and you must be running Windows NT/2000. The error message itself is caused by Windows, and not by the limitations of the AVI file format.

So how do I capture more than 4GB?
You must do all of the following:

Use normal capture (F6 key) and not compatibility mode capture (F5 key).
Check Capture/Enable multisegmented capture.
Add one or more drives to Capture/Spill drives. Set the thresholds to 50MB, and make sure you use a full path (i.e. E:\ and not E. Also, set priority of all drives to 0 to avoid a bug in V1.4c.
VirtualDub will then capture in segments to a bunch of 2GB files.