A few times now while I've been working on a VS8 project, with a lot of filters and the like applied, I'll get an error saying "Ran out of Virtual Memory " or something to that effect, and VS closes down.
I found that I currently am using 744MB of virtual memory on my C Drive, which is 130GB in size now. Can I adjust the virtual memory to a higher amount? How would this effect my computer? THANKS in advance if anyone can help!!!!!
Virtual Memory
Moderator: Ken Berry
-
THoff
First, apply the V8.01 patch if you haven't done so yet. It fixes a memory leak that will exhaust your memory faster than UVS normally would.
If you want to increase virtual memory, you can do it from the System applet in Control Panel. Select Advanced, Performance, Advanced again, and make the desired changes.
For best performance, use a permanent swap file by setting the minimum and maximum size to be the same value. This eliminates the need to size the swap file dynamically as memory consumption grows. You may also want to put the swap file on a separate physical drive, or at least a separate logical partition.
If you want to increase virtual memory, you can do it from the System applet in Control Panel. Select Advanced, Performance, Advanced again, and make the desired changes.
For best performance, use a permanent swap file by setting the minimum and maximum size to be the same value. This eliminates the need to size the swap file dynamically as memory consumption grows. You may also want to put the swap file on a separate physical drive, or at least a separate logical partition.
-
B-Riebe
I found that MORE RAM, fixing the min/max Page File settings, working with 2 FAST physical drives, and doing the other tweaks the UVS manual recommends REALLY helped UVS's performance.
In careful monitoring, I learned UVS (8.01) is a memory monster...eats it like candy (RAM & PF). Video editing in general REQUIRES lots of PC resources!! With my new PC and 1GB RAM I expected UVS to fly along nicely.....it did NOT. It was too slow to work in (based on my expectations). I now have 2GB RAM and 2 fast physical drives. UVS runs SO much faster now and is more pleasureable to work in. Also, It uses much less Page File memory now.
My min/max Page File is now set to 4096MB (double my RAM), AND I have this set for BOTH of my drives. My specs:
P4 3.2GHz 800 (HT enabled)
2.0GB DDR2 PC2-4200 RAM
80GB & 80GB 7200 SATA HDDs
DMA Transfer Mode 5
ATI Radeon X300 128MB
Set your Page File min/max double your RAM amount. Do this for each drive. Do the performance tweaking found in the manual. Add more RAM, if possible. GOOD LUCK!
In careful monitoring, I learned UVS (8.01) is a memory monster...eats it like candy (RAM & PF). Video editing in general REQUIRES lots of PC resources!! With my new PC and 1GB RAM I expected UVS to fly along nicely.....it did NOT. It was too slow to work in (based on my expectations). I now have 2GB RAM and 2 fast physical drives. UVS runs SO much faster now and is more pleasureable to work in. Also, It uses much less Page File memory now.
My min/max Page File is now set to 4096MB (double my RAM), AND I have this set for BOTH of my drives. My specs:
P4 3.2GHz 800 (HT enabled)
2.0GB DDR2 PC2-4200 RAM
80GB & 80GB 7200 SATA HDDs
DMA Transfer Mode 5
ATI Radeon X300 128MB
Set your Page File min/max double your RAM amount. Do this for each drive. Do the performance tweaking found in the manual. Add more RAM, if possible. GOOD LUCK!
-
jchunter_2
FYI, I have been running for several months with NO swap file and write caching disabled. I have 1GB memory and 3 GHz P4 CPU. No problems seen at all with capturing analog video, editing, creating video files or DVDs. Video Studio acquires memory during playback up to about 600MB (total) and stays there.
Digital capture to Mpeg2 is the most real-time critical operation and runs about 60 - 90% CPU busy. It makes more sense to me to have lots of real memory space directly available for buffering (if the CPU gets behind the capture stream) than to try to page it out to a swap file. I have not had dropped frames but also have not done enough digital capture to recommend this to anyone else. I would be tempted to first enable write caching during capture if I experienced dropped frames. Even more real memory seems like another great idea.
Digital capture to Mpeg2 is the most real-time critical operation and runs about 60 - 90% CPU busy. It makes more sense to me to have lots of real memory space directly available for buffering (if the CPU gets behind the capture stream) than to try to page it out to a swap file. I have not had dropped frames but also have not done enough digital capture to recommend this to anyone else. I would be tempted to first enable write caching during capture if I experienced dropped frames. Even more real memory seems like another great idea.