-
Vegas Render Error (Low Memory)
Hello to everyone in sony vegas land,
I know this issue has been covered before, unfortunately the creative cow threads i have read and google searches i have done havent been successful in resolving my problem.
the main issue is; when i attempt to render out a project i get the dreaded ‘low memory error’
my specs are
sony vegas 10c 64bit (reinstalled yesterday)
windows 7 ulitmate 64bit
i7 930@2.80GHz
12Gig RAM (more than enough to run vegas i would assume)the file type in the vegas projects are MXF out of a sony ex3 (i havent used these file before, until now)
project is 16min long with basic effects (soft vignette/few flash transitions/ bump up contrast)
I have increase my page file to 100gig! so virtual memory isnt the issue – i think?!
the only way i can get anything to render is to nest the project in a untitled project and do small sections.
anyone? please?
-
8 Replies
-
How big is your page file?
Windows since XP (and Unix/Linux for that matter) always wants to have page space. Always. Programs 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. Sometimes, programs leave parts of themselves in allocated memory just in case you are going to run that program again.
System/virtual memory and RAM are NOT the same thing. RAM is your physical chip-based memory. Total System Memory is the blending of real RAM and disk based page space. The kernel takes care of swapping memory pages between RAM and page space as fast as possible and with some adaptive intelligence so that programs are executing from real RAM and are not stuck waiting for their memory pages to be brought in from page space.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Hi Stephen,
I have allocated 100 gig to page file, the default or susgested amount is 18gig.
-
Overkill rarely fixes anything and sometimes makes things worse. Microsoft doesn’t recommend increasing the pagefile to more than 3 x RAM, and the maximum allowed size for any one instance of pagefile.sys on a machine is limited to 4GB.
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.
Are you running Norton, by any chance?
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Okay i’ll drop it back to 36 gig which is 3 x RAM. Im not running Norton either, ESET NOD 32 as anti virus.
My bosses computer is outdated, slow and only 32bit, yet his system handles Vegas 10 with ease, zero issues when rendering and uses all the same effects, transitions and file formats.
I have recently changed the graphics card back to an older model as I suspected that this may have been influencing the rendering process too. Unfortunately the issue persists.
what do I do?
-
From my last post:
“and the maximum allowed size for any one instance of pagefile.sys on a machine is limited to 4GB.”
I am wondering if it isn’t time to start over with a fresh install of Windows and Vegas. It sounds like you have been chasing a fly with a shotgun. Who knows what carnage that you have on your PC.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
But the recommended page file minium is 18gig on my system? I have already reinstalled vegas, my windows system is running perfectly in all other areas and applications, just Vegas seems to be the trouble maker. If it was a page file issue I would hope that me slowly increasing it – 18 – 25 -35 – 45 – 55 – 65 – 100 gig would have resolved it.
Yesterday I had one project render out when a computer tech was here, today its back to the same issue.
really dissapointed in how much of an issue this has become.
-
Jack,
I just went through the very same issue which took a while to sort out. I changed the ram, graphics card, everything that had memory attached but to no avail. Finally I ended up going for a brand new install of Windows 7 64bit (we used a new operating drive because I was concerned that the 32mb on board memory of the drive might have had a glitch but I reckon a format would have surficed). We also had the bios for the Asus P6T board updated at the same time. We then installed VP 10c 64bit and all is running incredibly smoothly. My feeling is that either Windows or VP 10c somehow screwed up the codecs slightly, or that they conflicted slightly with the older bios. Like I said, the system is flying now, better than ever actually. Best of luck with it, I know how frustrating is.
-
Thanks Charles, that info is valuable – first hand experience is hard to beat.
Might have to bite the bullet and reinstall windows, though I would desperately prefer not too.
Reply to this Discussion! Login or Sign Up