_Vengeance_
30th May 2002, 08:07
Does anyone else have this problem? :confused:
My Virtualdub sometimes flat out stops when the capture drive is full, despite other drives being defined in the "capture drives" configuration. :confused:
It makes me paranoid. I want to go to a party, and record 2 hours of stuff, but I can never be certain it will be successful. As such I have to set up a VCR as a backup method, find a blank tape, and do everything that virtualdub is supposed to get me OUT of doing. :angry:
My theory is that I have a bad configuration value somewhere -- maybe threshold, or "Do not create files [smaller/larger] than", or something. I think I have maybe found a virtualdub bug.
This has happened with 1.4.5, 1.4.6, 1.4.7, 1.4.8. I am currently using the non-sanctioned non-official VirtualdubREC/VirtualdubVCR 1.4.7 with built-in-timer by Joe Redfish (found at www.virtualdub.NET). But I have had this error with several other virtualdubs! :confused:
Currently I have 4 capture drives (120G, 80G, 60G, 40G) set up in decreasing priorty. Do the priority numbers actually matter? Mine are kind of random (ie is 6,4,3,1 the same as 4,3,2,1 the same as 100,50,-5,-69, etc). I have various thresholds set (50,500,100,500M). I have "Try not to create AVI file smaller than 100M" set and "Try not to create AVI file larger than 1999M" set.
Disk I/O: Chunk size 512K, Chunks in buffer 64. Disable windows write buffering CHECKED.
No stop conditions set. :devil:
What gives? Why would it just stop?
My Virtualdub sometimes flat out stops when the capture drive is full, despite other drives being defined in the "capture drives" configuration. :confused:
It makes me paranoid. I want to go to a party, and record 2 hours of stuff, but I can never be certain it will be successful. As such I have to set up a VCR as a backup method, find a blank tape, and do everything that virtualdub is supposed to get me OUT of doing. :angry:
My theory is that I have a bad configuration value somewhere -- maybe threshold, or "Do not create files [smaller/larger] than", or something. I think I have maybe found a virtualdub bug.
This has happened with 1.4.5, 1.4.6, 1.4.7, 1.4.8. I am currently using the non-sanctioned non-official VirtualdubREC/VirtualdubVCR 1.4.7 with built-in-timer by Joe Redfish (found at www.virtualdub.NET). But I have had this error with several other virtualdubs! :confused:
Currently I have 4 capture drives (120G, 80G, 60G, 40G) set up in decreasing priorty. Do the priority numbers actually matter? Mine are kind of random (ie is 6,4,3,1 the same as 4,3,2,1 the same as 100,50,-5,-69, etc). I have various thresholds set (50,500,100,500M). I have "Try not to create AVI file smaller than 100M" set and "Try not to create AVI file larger than 1999M" set.
Disk I/O: Chunk size 512K, Chunks in buffer 64. Disable windows write buffering CHECKED.
No stop conditions set. :devil:
What gives? Why would it just stop?