| Printable Version of Topic
Click here to view this topic in its original format |
| Unofficial VirtualDub Support Forums > Capture > Capture Crash After 1,5 Hour |
| Posted by: Renele77 Mar 7 2005, 08:34 AM |
| Hello! I have tried to capture a 2 hours movie from VHS and I always have the problem that Virtualdub 1.5.10 stopps after 1,5 hours. I could see that the usage of RAM was increased from 170 MB to 1 GB in some seconds. I have enough diskspace for files and I´m using multi-segment-files (1 GB each file). Why does VirtDub stops and use a lot of memory? Thanks a lot! |
| Posted by: phaeron Mar 7 2005, 04:41 PM |
| Need more info: What version of Windows, and any video/audio codecs in use? |
| Posted by: Renele77 Mar 7 2005, 09:01 PM |
| Hello! I use XP and have P4 3200 Mhz. I tried today Virtualdub 1.6.4 but I got the same error. I used PICVideo MJPEG and Hyffyv and nearly after 1:22 h the capturing stops and the memory usage increases to the highest level. Since I tried 2 different codecs it seems to depend on Virtualdub or XP. After pressing ESC I got sometimes message that audio data were lost. But this may depends on the stopping capturing. Are there some settings which stops capturing? But I have not much lost frames and the quality should be ok. |
| Posted by: Renele77 Mar 7 2005, 09:08 PM |
| I have read something about a bug in capturing drivers which stops at 1hour 11 minutes. But I'm above this limit. I'm using BT878 chipset and VWF drivers. Are there problems with VWF drivers and BT878? What tests I can made or should I use some better drivers? Any ideas? Thanks a lot. |
| Posted by: phaeron Mar 8 2005, 05:28 AM |
| I'd have to review the code to be sure, but I think I know what's going on here. For some reason the timing calculations in the video code have gone haywire and VirtualDub is adding some absurd number of drop frames to the output file. The rise in memory usage and the "stop" is caused by an never-ending loop that is adding zero-byte frames to the output file. I'll bet your last segment file is filled with a very high number of drop frames at the end. The 1:11 bug has to do with the video clock from the capture driver suddenly restarting from time zero once that amount of time has elapsed. I'm not quite sure how that could cause this situation, but part of me suspects that the video clock adjustment code might react very badly to such an abrupt change in time base, perhaps leveling or even inverting the estimated time slope. You might try turning it off in Capture > Timing and see if it makes a different. |
| Posted by: Renele77 Mar 8 2005, 06:31 AM |
| Hello! I'm not sure if I understand right what I have to switch off in Capture Timing. Can you describe the option? But can you imagine why I have the problem during capturing when many VDub users doesn't have? Beside the switching off what I can I do? Which software part of my PC (driver or tools) can cause such a 0-byte filling at the end? Should I reinstall some drivers? I'm thankful for any suggestion! |
| Posted by: phaeron Mar 8 2005, 06:39 AM |
| The option you want is called "Correct video timing if it is off from real-time." Video capture drivers are basically all unique; almost none of them work 100% correctly and each has their own unique quirk. It happens that older versions of the BT8x8 driver have a timing wraparound at 1h11m. Whether this is responsible for triggering the interesting behavior you are experiencing, I don't know; the suggestion to toggle the timing option is so far a guess. If you can find updated video capture drivers, I would encourage you to try updating, just in case the behavior of the newer driver avoids the issue. |
| Posted by: Renele77 Mar 9 2005, 06:23 AM |
| Hello again! I reinstalled my wintv application and vfw drivers to have a clean situation. But I did not find this option in version 1.5.10. but I find something similar in v1.6.4. "filling null byte frames when streams are far apart" I deselected all sync.-options and but now the capturing stopped also after 1,5 h but without increasing the memory! It´s really strange why capturing just stops without any warning. It seems that Vdub can not capture longer than that time!? - at least at my PC :-( It is possible to use the wdm-driver with Vdub or can I just use VCR in this case? Which possibilities I have now to be able to capture longer movies??? Thanks a lot. Rene |
| Posted by: Renele77 Mar 9 2005, 06:30 AM |
| add. question: Could it depend on resolution? When I want to use the Hauppauge software for capturing I'm not able to set it to 720x480 but in VDub it is possible. Power saving settings in XP or switched off. Are there other options which I did forget? Did you never heard about similar problems during capture? I can't believe that I'm the only one. Rene |
| Posted by: Armageddon Mar 10 2005, 08:12 PM |
| Post edited to avoid confusion - my apologies. (no info) |
| Posted by: phaeron Mar 11 2005, 08:22 AM |
| Probably not, actually. The original poster's problem isn't an application hang, but VirtualDub simply stopping to capture frames. It'll still respond; it simply doesn't update the side panel because it's not writing frames to disk. (I'll fix the panel so that it updates even if frames are being continuously dropped.) Renele77, can you do me a favor? Turn on the timing log under the Capture menu, and let the capture run until it stops capturing video frames. Then stop it and save the log to disk, zip it up, and either post it somewhere with a link or send it to me by email. The file will be a .csv (comma separated value) text file that contains a list of the video frames captured along with the timestamps that the capture device is reporting as their time of capture. That'll help me determine what's wrong with the capture clock. |
| Posted by: Armageddon Mar 11 2005, 11:28 AM |
| Post edited to avoid confusion, my apologies (no info) |
| Posted by: Renele77 Mar 12 2005, 09:03 PM |
| Hello! I have saved the csv-file after the crash. Now I want to send it to you but I can't find your email. Can you send me a PM with your address please that I can send you the file? By the way I want tell you some new information: I tried to capture using the Hauppauge-Software Win TV 2000 and the process runs longer than 1,5 hours. But I detected that the audio and video stream are getting asynchron. At the beginning of the movie sound and video are synchron. But if you go further in the video-file the difference will increase. After 1,5 or 2 hours sound and video have a difference of 1 or 2 seconds. I have read that this depend on the hardware since the 2 streams are handled seperatly. Can be this the reason? Now I know wha VDub have the option "resync". It seems that WinTV2000 does not have this functionality. ok, I'll wait for you address and any suggestions. I thank you for helping me. I'm sure we fix the problem! :-) |
| Posted by: Renele77 Mar 15 2005, 06:32 AM |
| Hello! I 've sent the logfile via mail. Since I must reinstall my machine I tried again to capture by VDub 1.6.4. I couls detect following behavior, when I'm enabling following options: Captur --> Timing: Resync audio to video will result in no sound or better in rush and the capture hangs after 1 hour. If I use video to audio I have sound, but I did not try to capture longer. If I use no Sync I have sound too. Could it depend on my TV-card? I have Hauppauge Win TV PCI with BT878. I use XP with NTFS on my data partition which has 140 GB. Which reasons are there for broken capturing? I have reinstalled the XP so I should not have some software-conflicts. I just installed Office and a Codec-package (ACM ...), win TV application and VDUB 1.6.4. But I have again some problems to login in some websites like GMX and VDUB-forum. Do I catch again spyware by the codec-package????? Hope you can help. Renele77 |
| Posted by: phaeron Mar 16 2005, 08:39 AM |
| Okay, I think I know what it is. It's a numeric overflow in the audio resampler, and it's happening because I switched the capture system from milliseconds to microsecond timing in the 1.6 series. Sheesh, 128-bit arithmetic wasn't enough. Working on a fix for 1.6.5. |
| Posted by: Renele77 Mar 16 2005, 12:18 PM |
| Hello! Thats great! So I know that it does not depend on my pc and you can improve the tool. So I'm looking forward for 1.6.5 Thanks a lot and best wishes! A question: Where do you come from? I'm from Leipzig (Germany). VDub is a great tool and did you developed it by yourself in freetime? René |
| Posted by: i4004 Mar 16 2005, 06:11 PM | ||
so the story goes; http://www.virtualdub.org/virtualdub_history |