-
Render stops saying system low on memory
I’m rendering a 720p video and it does this every time tonight. I’ve done it before although for renders that can take up to 3 hours+ and its been fine. I have no idea what the issue is.
I have a Q6600 2.6GHz quad core cpu, 6GB of RAM, running Vegas Pro 32bit on Windows 7 64bit.
-
27 Replies
-
What render format? WMV seems to give this error a lot. Did you try Vegas Pro 64-bit? That should see more memory. Vegas Pro 32-bit can only see 2GB even though you have 6GB.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I’m rendering using mp4. I did try 64 bit and the render worked initially, but I checked free memory and it was going down the whole time during the render. At the rate it was decreasing it would’ve taken about half an hour to reach zero, while the render itself would take almost 2 hours.
I need to use 32bit for the third party plug-ins that I NEED to use.
-
Tried rendering the project firstly to an .avi file first? Then re-render that file to MP4.
Doing this means it can do all of the plugins and corrections work and simply put out a .avi file, before spending processing power converting to MP4.
Just makes things less complicated for the processor..
Ben
Do unto others…
-
Won’t that just compress it twice though? I don’t want to sacrifice any quality…
Its saying system low on memory, I don’t see how that would have anything to do with CPU.
-
I do notice when my the render will stop and say system is out of memory. I go to task manager and see the memory usage by Vegas increasing by about a meg and a half every second, so eventually it will max out, and say it needs more I guess. I do not understand this though, why would it use more and more as it goes along. I either uses a certain amount or it doesn’t depending on the intensity of what is needed to be used. A later part of a render shouldn’t be more RAM intensive than the beginning. This is very frustrating to figure out.
-
Sorry, I just shoot SD for news… What I really meant to say when I said render it back as a .avi first, was to render the project to the same format as the original material. Then render that one…
As its in the same format etc, then vegas will recognise the untouched files wont need recompressing, so it completes the transitions, FX and whatnot without altering the quality.
I have a huge RAM real estate, plus HDD space, and even for some jobs, if there is colour correction etc then vegas sucks up almost all memory. Dont know why…. it never used to do it… So far, I figure its a Full Moon thing.
If vegas is having to do corrections, sound processing AND then render out to a different format all in the one hit then things can get messy.
If you just ask it to do one thing at a time, like us blokes, then all will be well.
Sometimes, the PC just gives up…. so to make it a low stress workflow, I use the above method.
Ben
Do unto others…
-
Also…. if you use DVDA, dont forget that it makes a hidden copy of EVERY job you have done, and this needs to be nuked from time to time.
Have a look in documents and settings/your name/my documents for DVD Architect projects. Give this folder a quick enema and that will give you back a LOT of HDD real estate.
Ben
Do unto others…
-
It still uses the same amount of RAM when rendering it as .avi like the original file, but of course less CPU.
-
Did you try the option of network rendering? This sometimes solves the problems with memory that occurs in Vegas 9, even if you are just using one PC without network-connected render machines.
Theo
-
What version of Vegas Pro are you using? Vegas Pro 9.0b had some memory issues while rendering that were fixed in the “C” update (Vegas Pro 9.0c) which may have been in 9.0 and 9.0a as well.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up