Time limit in vdub?

[dabliu]

Hi, i'm capturing my vcr collection using a pinnacle dc10+ & vdub on a K6II @500mhz, 160Mb ram and 40GB HD. It works fine, and i'm capturing videos at full size and rate (30 fps @ 640x480) with no dropped frames at all. But it seems Vdub has a capture time limit: it captures a little over an hour and crashes, always exactly at the same time, no matter what resolution or bitrate. I've tried messing around with vdub configurations, but it seems the limitation remains. I just don't know what else to try.

<font size=-1>[ This Message was edited by: dabliu on 2001-10-09 22:17:03 ]</font>

[Beretta]

What codec are you using? Are you capturing to a single .avi file, or to multiple files?

[jeex]

you're probably running in to the fat32 file size limit or avi file size limit.. capturing to mulitple file's should do the trick.

[holistic]

http://www.virtualdub.org/docs_capture

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 *2^32 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



** 2^32 is 2 raised to the power of 32



<font size=-1>[ This Message was edited by: holistic on 2001-10-10 01:13:19 ]</font>

[dabliu]

I'm using the hardware codec, and capturing uncompressed mjpeg files to multiple files. It seems the bug holistic reported it's exactly what's happenig. I'm getting 1 hour 11 minutes 34 seconds.... unfortunately, i've got the fatal version of it... and apparently, there's no fix for the bug (I'm usig a DC10+). Thanks anyway, it helped a lot. (at least, now I know what's happening, and it isn't anything I was doing wrong)

<font size=-1>[ This Message was edited by: dabliu on 2001-10-11 04:23:33 ]</font>

[Ronin2]

I was caturing through a Pinnacle PCTV card and VirtualDub reported the above problem and worked around it. I've now changed over to AVI-IO and there doesn't seem to be any problem at all, this may be a possible solution for you.

Regards,
Ronin2