|
|
| bypatel |
| Posted: Oct 31 2002, 03:51 AM |
 |
|
Unregistered
|
I've been using VirtualDub with no problem for years. However, just recently it's been eating up memory. I'm trying to convert a DV file (captured via Pinnale DV Studio 7) to Divx5 using VirtualDub. I encode at 1-pass with 960 bitrate. No audio compression, direct stream copy. It used to work fine, however, now it seems to keep eating memory until my system runs out of memory. I have 512 megs of ram on a P4 machine. I have a lot of free space on my hard drive, so more than enough virtual memory.
Can anyone explain what might have changed or how to fix it? |
|
| bypatel |
| Posted: Oct 31 2002, 03:52 AM |
|
|
Unregistered
|
Forget to mention the DV file is about 18 gigs. I don't think virtualdub would need that much memory to make a divx file. There should be some cap I assume? I don't know how the internals work..anyone care to shed some light. |
|
| ChristianHJW |
| Posted: Oct 31 2002, 02:05 PM |
|
|
Advanced Member
Group: Moderators
Posts: 1768
Member No.: 2
Joined: 7-July 02
|
Yes .... the fact that a 18 GB AVI file is simply crap ... max. size per segment is 2 GB ( independent of OS/file system ) ...
--------------------
Visit the unofficial Virtualdub support forum on http://forums.virtualdub.org - help to reduce the big number of emails Avery Lee is getting every day !!
Support matroska as container and Gstreamer as the only truely open, x-platform multimedia platform .... |
|
| bypatel |
| Posted: Oct 31 2002, 05:38 PM |
|
|
Unregistered
|
| QUOTE (ChristianHJW @ Oct 31 2002, 08:05 AM) | Yes .... the fact that a 18 GB AVI file is simply crap ... max. size per segment is 2 GB ( independent of OS/file system ) ...
|
Well I've acutally used VirtualDub on 20 GB DV files before and they've worked fine. This just suddenly started happening. I am hesitant to believe that I have to break up the file into 2 GB segments to get it to work. |
|
| Kippesoep |
| Posted: Oct 31 2002, 09:13 PM |
|
|
Moderator of the Virtualdub support forum
Group: Moderators
Posts: 447
Member No.: 441
Joined: 6-October 02
|
OpenDML AVI files, such as those created by VD can be much larger than that. There some code in VD that limits them to 127GB, though. So that's not your problem.
Does this also happen with other codecs? The DivX codec may have a memory leak. Are you using any filters? They may have memory leaks. There could, of course, be a memory leak in VD itself, but it seems unlikely that it would have gone unnoticed by this community. |
|
| bypatel |
| Posted: Nov 2 2002, 03:41 AM |
|
|
Unregistered
|
| QUOTE (Kippesoep @ Oct 31 2002, 03:13 PM) | OpenDML AVI files, such as those created by VD can be much larger than that. There some code in VD that limits them to 127GB, though. So that's not your problem.
Does this also happen with other codecs? The DivX codec may have a memory leak. Are you using any filters? They may have memory leaks. There could, of course, be a memory leak in VD itself, but it seems unlikely that it would have gone unnoticed by this community. |
Thanks for info on OpenDML.
I'm not using any filters at all. I do use the "Full Processing Mode" for Video and then choose the Divx 5.02 Codec for compression. It could be the Divx codec that has a memory leak. However, I tried using the XviD Codec and the Indio Video 5.0 Codec as well. The same thing occured. The "Mem Usage" in the windows task manager just keep increasing until it consumed all the virtual memory I had and aborted with a virtual memory error.
Just out of curiosity I was wondering if anyone else has been looking at the task manager when running VirtualDub? If so, have you noticed whether the VirtualDub process continually consumes more and more memory? Or does the memory consumption stay at a fairly constant rate?
I don't think VirtualDub is the cause of the error. I have used VirtualDub in the past do the exact same process, i.e, converting an 18 GB DV file into a Divx file. However, it seems I may have done something recently to my system which may have caused this...however, I can't pinpoint what exactly I've done. |
|
| bypatel |
| Posted: Nov 4 2002, 08:36 AM |
|
|
Unregistered
|
Just for everyone's information, I finally figured out what was wrong. I had remembered that before when I loaded the DV file into VirtualDub I took a peak at the "File Information" selection. At one point it had stated the DV file was using the microVideo DV 300 codec. However, I had recently installed a seperate Pinnacle DV codec. This new codec I installed overwrote the old codec. Doing this caused my memory leak. After doing a complete uninstall of my software, I reinstalled my Pinnacle Studio 7 without installing the seperate Pinnacle DV codec. Now my file information for the DV file once again shows microVideo DV 300 codec. Apparently the seperate codec must've had some sort of issue that it caused a memory leak. =) I'm happy I can go VD'ing again. |
|
| Morsa |
| Posted: Nov 4 2002, 08:56 AM |
|
|
Moderator of the Vdub support board
Group: Moderators
Posts: 640
Member No.: 246
Joined: 9-September 02
|
Greta news!!! |
|
