-
Vegas Rendering and Memory Error – AGAIN !!
Any help or suggestions would be greatly appreciated !
I have a Vegas 10 (not pro) timeline of about 7 mins with a combination of stills and movie clips in .mov .mp4 and .Mt2s formats that refuses to render and continually gives me the dreaded out of memory error. I’ve tried reducing the dynamic ram setting, dissabling all services / applications via msconfig, the cff >2gb flag in the Vegas.exe files and some of the I/O Plug in dll’s (not sure that i’ve updated all – would my source files dictate which dlls are key?) but nothing appears to be helping.
I’m trying to render using Sony AVC template and have also tried Mainconcept avc template, but no hint of success yet !
My next attempt is to render each clip individually and import into another timeline – no idea why, but thought I’d try it !
Any other suggestions gladly received !
Andy
-
5 Replies
-
Low Memory or Out of Memory does not mean “Not enough RAM”, though adding RAM can sometimes fix a “Low Memory” waning. A “Low Memory” warning usually means that you have exceeded your commit limit. You need either a bigger page file, more physical memory, or both.
One of the biggest sources of confusion over Windows memory usage is the whole concept of virtual memory compared to physical memory. Windows organizes memory, physical and virtual, into pages. Each page is a fixed size (typically 4 KB). To make things more confusing, there’s also a pagefile. Many Windows users still think of this as a swap file, a bit of disk storage that is only called into play when you absolutely run out of physical RAM. In versions of Windows starting with Vista, that is no longer the case. The most important thing to realize is that physical memory and the page file added together equal the commit limit, which is the total amount of virtual memory that all processes can reserve and commit. You can monitor the commit level of any running program in the Memory tab of the Resource Monitor (resmon).
Start the Task Manager, click on the “Processes” tab, then click on “Commit Size” to sort by size. This will show you which processes are memory hogs that you may be able to shut down.
All Windows since XP (and Unix/Linux for that matter) always wants to have page space. Always. Programs (including drivers and codecs) like to and are allowed to pre-allocate as much memory as they want. Even if they are never ever going to actually use it. Sometimes those programs properly deallocate memory, sometimes they don’t (resulting in “memory leak”). Sometimes, programs leave parts of themselves in allocated memory just in case you are going to run that program again. (MS Word, Excel and other Office programs are particularly adept at this). If you have no page file and a program wants to commit some for itself, your PC will crash (AKA, BSOD, or Blue Screen of Death).
Paging file configuration is in the System properties, which you can get to by typing “sysdm.cpl” into the Run dialog, clicking on the Advanced tab, clicking on the Performance Options button, clicking on the Advanced tab, and then clicking on the Change button. I would suggest a value of 1.5X the currently allocated value. The old advice of 2X or 3X your RAM is, well, old advice when a few MB of RAM was normal. 64-bit Windows can having paging files that are up to 16TB in size and supports up to 16 paging files, where each must be on a separate volume.”
DO NOT put a paging file on an external drive because if it’s not present when Windows boots, then Windows will crash.
For more information, see https://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
amazing post Stephen, I’ve been puzzled by Windows and its different performance issues with the page file through all these years, Microsoft is not clear about it… but as you said in recent versions of Windows it doesn’t matter if you have 4 or 32 GB of RAM, Windows NEEDS some GB of drive space for a paging file, I think it’s legacy programming, software and Windows itself should be rewritten for them to ignore the paging file, not happening anytime soon.
you NEED a page file for 100% stability and best performance, don’t ever install your page file in a drive slower than the drive where Windows is installed, for reference I have a 64 GB RAM workstation at my workplace and Windows still crash if you don’t set up a proper paging file… that’s with a couple of Solid State Drives and as I said 64 GB. Software want something “physical” instead of RAM to write temp files, that’s it, don’t mess with the page file !!
-
I was having a “huge” problem with this; VP12 was using all of my systems memory and then it crashed my computer, till I found the setting for allocating memory, I set it to “auto” and now the system is stable. Why this was never a problem till a week ago? I cannot figure that out.
MJM
Malcolm
http://www.malcolmproductions.com -
“don’t ever install your page file in a drive slower than the drive where Windows is installed”
That’s an interesting observation, I’ll have to do some testing (It should be easy since I still have a floppy drive). Is this something you experienced or advice you picked up from someone else?
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
It happened again!!!
Now allocating memory will not solve VP12’s appetite for RAM. From the system monitor I watch Vegas use up all 12 gigs of ram and then crash my system. This is very annoying. I did a search on memory allocation and MS windows guide for Win7/64 is the low setting should be at actual ram and the upper setting is 3x ram. So rather than setting “auto” which worked fine last week, I set it to 12/36 and it’s no better. Gave up in frustration and have a shoot this weekend, I’ll be back on Monday to see if this is a persistent problem or it can be solved with a change of settings. I have already uninstalled VP12 and reinstalled it before, no help there.Malcolm
http://www.malcolmproductions.com
Reply to this Discussion! Login or Sign Up