Vegas refuses to render – memory problems?

[Frederic Baumann]

Hi,

I have the same problem with my new Vegas Movie Studio Platinum HD 10.0, see my post from yesterday.

I have also seen other posts about low memory errors with Vegas Pro.

As far as I understand, nobody has found out the reason of these errors. Though it looks like adding gigas of RAM does not fix anything.

I have logged my problem to Sony’s support. They have given me several answers of no help. The only thing I feel is that they don’t really read the details I give, and don’t really care about it…

My only suggestion so far: all of us who are experiencing this problem should log it on the Sony support. Then maybe Sony will decide to really investigate it and fix it in a patch.
I have also complained on the Sony Facebook fan page, maybe you can do it as well to help make the problem a priority for Sony.

For me it is a priority: I just cannot render my movies 🙁

[John Rofrano]

This is a common problem with DSLR cameras that shoot movies. They all use some non-standard format that appears to work at first but then gives all sorts of problems later. What you need to do is transcode the footage into a standard format that Vegas can edit and render. Most Canon 5D/7D shooters use CineForm Neo Scene ($99 USD). You can also use VASST GearShift ($49 USD) to batch convert the files right within Vegas. You can also use a any one of a number of free utilities like AviDemux, MPEG Slipstream, etc., to convert the footage to M-JPEG, Lagarith, Huffyuv, or some other lossless or near lossless format.

I would definitely contact Sony technical support and let them know you are having problems with the native Canon t2i files. Perhaps they can fix this in a future release because it sounds like a bug if you can render them individually but not as a group.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Charles Biddle]

We have had the same problem for some time with a variety of files, but we have never had as much trouble as of late. Various render issues failing at different points in the process. Sometimes a specific memory error message will pop-up, sometimes it will give a generic Vegas has encountered an error, and other times Vegas will simply shut down. All very stressing to say the least.

The machine in question is a windows 7 64bit with i7-930 and 6GB of ram (problem also occurs on a Vista 64bit q6600 and 8GB of ram). We have tried lowering preview ram to zero, setting render threads to zero, and we never seem to find a fix.

Our usual workaround involves rendering to intermediates (regardless of the original footage type) in multiple sections and then rerendering to our final format.

While this is not ideal in anyway, it can get a file out if a deadline is approaching. The reason to render to the intermediate (Cineform *.AVI) is not for the 4:2:2 colorspace, but rather the file closes as it progresses in the render process. If an mpg2 or mp4 file doesn’t completely render, there is no usuable information left. The intermediates normally keep what has been rendered so far and are usable. We have had exceptions to this pop-up so it’s not a 100% workaround. If you attempt to render a 5 minute video and it crashes 1 minute in, you should have 1 minute of rendered video. Place that on your timeline above the original clips and then render the next few minutes repeating the same procedure.

After all is said and done you’ll have renders of varying lengths that will eventually equal your entire video length. Usually this will render. Yesterday while attempting this horrible workaround it would render out the intermediate, but would not render a complete *.mpg or *.mp4 as needed. We placed the “section renders” onto a new copy of Vegas and were able to render as needed.

It’s a miserable process that sometimes we have to go through. Otherwise we would simply switch to another program. Love Vegas, not loving the render errors.

So when is the Scarlett coming out again 2009, 2010, 2011…

[Fred Robinson]

I had no end of problems with this too with Vegas Pro 9e. A large part of the fix was tweaking the IOSurrogate exe program (found in Vegas’s x86 folder) to allow it to behave like a 64 bit program and handle large files. You do this using a program such as CFF Explorer. Since I did this I’ve had no more crashes. Seems like Sony released the 64 bit version without making it capable of handling the larger file sizes, i.e. a main benefit of having 64 bits!! The giveaway for me was that the program lives in the x86 folder (i.e. 32 bit).

Other things I always do now when starting Vegas are:

– Open Vegas as administrator
– Hold down Alt+Shift too, and tick ‘yes’ to clear previous cache, and click ‘no’.

These two steps have got rid of the problems I was having with ‘media file missing’ etc.

Good luck.

Fred

[Shaun Yee]

how do you tweak the file? I have downloaded explorersuite, and I want to know how u tweak the exe, which i found…

[Fred Robinson]

open the explorer program
goto file\open
then find the file… in this case it would be FileIOSurrogate.exe
On the left side you’ll see “NT HEADER”…. “DOS HEADER”… etc
Highlight “FILE HEADER” under “NT HEADER”
On the right side you’ll see a chart and in the bottom right corner you will see “CLICK HERE”
Click on that and a check box menu system will open.
Scroll down the menu list until you see “app can handle > than 2gig address space” and check that.
Save the file and close.

I’ve read in some other ‘tips’ that people have done the same with other .exe files within Vegas too, but I only changed this one and it worked for me.

Fred

[Jason Guerra]

Great info…I am having the same issues…when I followed your steps it asked to save and I hit yes but it says it cannot save file do you want to change the name? Thanks so much for all your help…any ideas on this?

[Fred Robinson]

Only thing I can think of is that you have Vegas open? Make sure it’s not open, or better still that it hasn’t been opened at all since a restart. Other than that – no. I can’t see why you’d be having that problem. 🙁