I can't render 35 min project to any format, it stops with the error :
: Vegas is low on memory try to close blah blah blah,
vegas 8 on the same mchine doesn't have any problems, but I edited project on 9, and now i can't do anything,
looks like a memory leak, cuz the error happens every time mem usage of vegas90.exe goes over one gig,
PC is quad Q95 4Gb of ram with 6Gb of paging file on separate raptor;
vegas gurus, any advice on this?
many many thanks!

A few things you can try:

1. Look at the "Ram Preview" amount. Make that a low number (like 8 or 16 meg).
2. Render out in segments instead of the whole thing at once.
3. Kill all non-essential background tasks (things like anti-virus, etc...)

Thanks Ed,
I tried this already, no good, same error on my laptop and desktop, I can't believe two weeks of work are wasted;
I'm afraid I already know the answer, but is there ANY way to open Vegas9 project on previous version of the app?
Many thanks!

What's actually in the project, Buba? I have to say this really doesn't sound right!

Ian, you are definitely asking the right question...what is on the timeline?

footage from Z7, EX1 and 5Dmkii, M2T, MXF and I converted MOVs from 5Dmkii in neoscene to AVI. 2 video tracks, 4 audio tracks, lots of cuts, very few MB Looks , color curves and color correction in every shot, 35 min in total.
I upgraded from build 772 to 896 and now I'm able to render in short segments on my laptop, but not on my desktop, which is strange, I ran Vista home premium on laptop and XP pro on desktop,
laptop is dual core 2.1 4Gb RAM, desktop is Quad 2.8, 4Gb RAM
next week I was planning to get an i7, but now I'm seriously thinkin to go MAC and FCP,
many many thanks for all your help and ideas,

32bit Vegas is only able to access 2.5GB max of RAM. Until you see a 64bit Magic Bullet, this is going to be an issue. I am fighting the same issues right now on the movie I am grading. Royal pain in the rear. Doing it with long GOP on the time line makes it worse. I only use intraframe codecs on the timeline for projects like this.

You have a mix of some of the more difficult types of footage to deal with and your thinking of moving to FCP?

With a new Mac you will get a newer processor, so that will help. Let us know how that works out.

Did you try rendering out in segments? You can then build a "final" project from the good segments.

yes, I can render in 5 - 6 min segments, but on my laptop only, not on desktop though,
I'm guessing this problem is Vegas 9Pro specific, at least I've never seen nothing like that in version 8c,
many many thanks for your help guys!

Buba,

I had the same problem.
Tried all of the fixes mentioned in the earlier posts.
See link at bottom. Found on Sony's site. While it did not "solve" the problem it helped. It allowed me to use Magic Bullet on some clips but not all clips in a timeline.
It is very simple to do, even though I originally thought it more complicated.
Take a look and see if you want to give it a shot.

Doug

Sony Creative Software - Forums - Vegas Pro - Video Messages (http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=648182)

Great find, Doug, thanks for posting. I am about to edit my first batch of AVCHD and I was getting nervous. Now at least I know there may be a cure!

Hope that gives you a way forward Buba.

A little OT but reading through that thread at the Sony forum reminded me why I hang out at DVi. Much more civilised!

Ian, if it's any consolation, the guy that started that thread was banned from the Sony forum a little while after that thread.
Trust me when I say that he was tame in comparison to some folks on there who got banned within a few days of posting :-(
It's a pretty tolerant bunch over there and Sony lets us get away with a lot of OT stuff that most forums would never tolerate.
Having said that, it's generally a group of very helpful users who are willing to share their knowledge.
Must be the "Vegas love" in us that makes us that way :-)

I upgrade to Vista 64 bits version and 9.0C 64 version for the same problem. Now I can render without "system low on memory" crash.

I have the same problem when using MB.
is there any solution?
I am sure most of you that use MB do not have the same problem.
Just wander what why it happens to selected computer?

Hi

I got this same error. I use Win7 64bit and Vegas 9c 32bit & 64bit. I had few projects to finish. As usual I use vegas to capture tapes, but one project I use cineform neo hd to see the difference. I did not use any plugins for the projects. When I tried to render project (captured via cineform) in vegas 32bit problems arised. It gave me an error "low mem", but rendering in vegas 64bit went through without any hiccups. My conclusion:

- windows 7 64bit + vegas 32bit + cineform files = memory management problems.
It seems that vegas has problem with mixing different file formats (or containers) other than .m2t under above configuration.

My other projects (not captured via cineform) rendered fine in vegas 32bit.

That's my 2 cents.

Tom

Many thanks to everybody for the input,
I did manage to deliver that project, but now have another one, but with the same symptoms,
I have mxf, Neocene converted 5Dmkii and red1 pro res files, before I uninstalled MB Looks, Vegas was just shutting down every time i was trying to open the project, now it shuts down every time I select OK to render;
hey Doug trick with dll editor didn't do the job for me , but thank you anyway,
I even tried to switch to Mac and FCP, men I hate it, will never touch it again :)
I'll try to get new, more powerful with lots more RAM PC and go 64 bit, will let you know if that will help.
cheers:)

Hi Buba, a lot us have the same issues. For me, 64bit Win 7 + mxf + Cineform 7D avi + V8c or V9c 32bit= CRASH. I thought it was Magic bullet but even a non MB looks veg crashes each time i hit render. The strange thing is a slower laptop Macbook Pro running Vista 64bit works pefectly for the same project!!

I am going to try the mem hack which will hopefully do the job for me but Vegas is unusable at the moment. I wonder if there is going to be a 8d/9d to solve this issue..

Folks, the problem has been resolved. I used the NTcore explorer and enabled Vegas8c to handle address above 2G. The system now renders 2x faster than the Q6600. It is about 1:1 for non plugin enabled files.

For MB Looks, the speed is about 1:1.2 .

A few weeks and $3K later I can work again, Vegas still crashes from time to time, but only when I have all kind of different formats footage,
I installed Vegas 9 64 bit on 3.06 i7 12 Gb ram with Win 7 64 bit installed,
it works now, twice as fast , but no MB looks on this setup,
as I said NT core explorer trick didn't work for me, but now on 64 bit vegas goes over 4 Gb with no problem;

*** Good News Alert for Vegas using HD .mov (and other HD/HDV?) *****

I've been struggling with horrible crashes in Vegas 9.0c trying to process footage from my Canon 7D using 1920 x 1080 .mov files. Crashes loading, crashes rendering, crashes just to crash. 3 different computers and 3 different operating systems. I just stumbled on a related string on the Sony forum and also saw a related forum here on DVinfo.net. You can check out the posting #9 by Sean Seah at http://www.dvinfo.net/forum/what-happens-vegas/469066-warning-mb-looks-problem-v8c-win7-64bit.html#post1469823 or the Sony support forum by "blink3times" at Sony Creative Software - Forums - Vegas Pro - Video Messages (http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=648182) to see the strings or give this a try


(Below is a summary of solution and a download site for CFF Explorer program):

http://download.cnet.com/CFF-Explorer/3000-2383_4-10431156.html?tag=mncol

****************************************************************

Most 32 bit exe and dll files have a 2 gig maximum memory cap. I've been playing around with CFF EXPLORER (free download) which is a program that allows you to easily open the exe or dll and click the 2 gig memory switch that allows it to use more than 2 gig.


Reset the memory flags in
vegas80.exe (or vegas90.exe.....)
m2tsplug.dll
mcstdh264dec.dll
sonymvd2pro_xp.dll
to "greater than 2gig" and did a render of which I almost always crash on (avchd at 1920 render to m2ts 1920@16Mb/s with AC3 audio)

open the CFF Explorer program
goto file\open
then find the file... in this case it would be Vegas.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.

Open the others and do the same.

MAKE SURE YOU DO A BACKUP COPY OF THE FILE BEFORE CHANGING IT JUST IN CASE YOU GET INTO TROUBLE!!!

On another note.... rendering stability has CLEARLY and MOST DEFINITELY improved DRASTICALLY
I did lock up once so far (with the plugin pack 3d adaptor) but it was a different lock up/crash that I had ever seen before. The rendering just plain stopped but the program didn't disappear. In fact instead of disappearing, it allowed me to save and close.

This btw SHOULD work with HDV for those that are having issues there too.

Did you get this to work in 9c? I tried to do the same thing but couldn't find these files in my 9c directories

m2tsplug.dll
mcstdh264dec.dll
sonymvd2pro_xp.dll

found them in the 8 directories though...

the m2ts is for AVCHD files handling and 264 for H264 I believe. I started out with the Vegas8.exe file and the improvement was alr obvious. Then I got a hang for aac/avc mp4 rendering and i did the same thing for the mcstdh264dec.dll and mp4 rendering worked. I have not done the rest.

I don't know why Red Giant software doesn't get with the program on 64-bit support. It doesn't seem to be a problem with NewBlue FX. 64-bit is quickly becoming defacto even on entry level systems.

the m2ts is for AVCHD files handling and 264 for H264 I believe. I started out with the Vegas8.exe file and the improvement was alr obvious. Then I got a hang for aac/avc mp4 rendering and i did the same thing for the mcstdh264dec.dll and mp4 rendering worked. I have not done the rest.

Right but my problem is I can't find any of these files in my 9c 32bit directories only in the 8 directories.

I can however edit AVCHD files in 9c so I'm really confused :(

Thomas,

I only use 9.0c 64bit now, but I found them in an older copy of Ver 8-32 bit also. Haven't downloaded Ver 9 in 32 bit on my home machine, but I'll try to check on my office machine.

I had the same problem with low mem messages it took me days to figure out what was wrong in my situation it was the video card driver. I had installed the latest video driver and started to get low mem problems while rendering with MBL. I then installed an older video card driver and the problem with away.

I'm having the exact issue. Crash club for Vegas.

Has anyone tried converting the AVCHD files to Avid DnX?
Thought I'd give it a shot, right now I'm using native AVCHD in the timeline.

...right now I'm using native AVCHD in the timeline.

Really? :(

Really? :(

Yeah, but just 3 second cutaways, thought I could get away with it. Guess not.

Yeah, but just 3 second cutaways, thought I could get away with it. Guess not.

As many times as we've talked about this.. and as many times as you've heard me say I convert my footage to DNxHD... Come on...

And yes, I convert my AVCHD to DNxHD nearly all the time.

As many times as we've talked about this.. and as many times as you've heard me say I convert my footage to DNxHD... Come on...

And yes, I convert my AVCHD to DNxHD nearly all the time.

Actually what seem to cause the memory errors/crashes during renders isn't the native 7d files but the jpegs in the timeline. I think I've isolated it.

Btw, kinda sucky that Vegas 9c can't handle jpegs. Come on Sony. jpegs. Not exactly some super duper HD codec. My Pentium 2 Abobe Premiere 4.0LE could handle that.

I know I'm resurrecting an old topic but I got this same error trying to render a slide show on 9.0e. I'm trying to render at 1920X1080/24p in a WMV.

This same project I rendered a few days ago minus 5 slides I added last night. I got the error the first time I tried and Googled the error message. I lowered my RAM preview and number of threads and it rendered successfully.

Now I added 5 slides to the show last night and I'm trying to render it again now.

The project is exclusively JPEG images with one 15 second video clip at the end. I didn't use any color correction or effects on the images in Vegas. I'm using most New Blue transitions with some Spice Master transitions thrown in.

My machine is a 1.6GHz dual core Toshiba laptop with 3GB RAM.

I just build a phat 12 gig quad core and upgraded to Vegas 10, and Now I'm getting low memory errors, I was able to get it to render by making my preview ram 0. But seriously, it's BS for Sony to continue to have this same stupid problem from version to version. I'm very tempted to buy CS5 and learn that.

I've had low memory problems for three two versions now, and I didn't spend 1500.00 dollars on a freakin machine to fight this software. This machine is a month old and whallaa, already errors, thanks Sony.

What is on your timeline? Are your project properties set to 32 bit?

Are you talking about pixel format? That is set to 8-bit.

Since Vegas 6, I have personally haven't experienced low memory issues or anything remotely similar.

In my case I edit photo montages, weddings up to four cameras, HD, SD, AVCHD and Mt2 files.

If you have had trouble with the last three versions, now on different machines, it would seem you are editing something troublesome, such as large photos, Red files, or whatever.

Hmmm, I just have video files and psd files......

PSD files would likely be the issue, don't you agree? I don't know if the following link would be of help.

I would consider viewing the issue as Vegas using PSD files, versus Vegas just generally having issues. PSD are a proprietary format, so while this may not help you, it is not unreasonable they might cause issues.

Best of luck, I don't use them. If you use them a lot, and can't find a solution with Vegas, then PP would be an obvious choice, and a no brainer. CS5 is reportedly very smooth too. My friends love it.

Working with layered PSD files in Vegas Pro 9 (http://www.custcenter.com/app/answers/detail/a_id/4971)

Thanks,

I plan to see if the psd files are the issue. I use them a lot for titles and tweak as I go along.

Well, I replaced the psd files with png files, it's a no go. Sigh

How large are they? This doesn't make sense. png files handle well in Vegas, provide they are of reasonable dimension, not that I know what reasonable is exactly. I resize all images for Vegas to be no larger than necessary to do some mild panning if necessary. Since my projects are usually no larger than 1280x720 I go no larger than 1500xwhatever maintain aspect ratio. We are supposedly able to use much larger, but I don't just because it drags the system down.

I've put hundreds of photos on my timeline and unless they are of huge dimension they work fine.

So without either png or psd can you verify that then Vegas is then fine?

The png files are around 150kbs or so each, and 1440x1080. There around 9 of them total, the project is 3 minutes long.

This is why it is puzzling. I got the psd/file project to render dropping my Dynamic Preview to 0, I'm trying the same with the png files.

The png files are around 150kbs or so each, and 1440x1080. There around 9 of them total, the project is 3 minutes long.

This is why it is puzzling. I got the psd/file project to render dropping my Dynamic Preview to 0, I'm trying the same with the png files.

Hmm, same project lowered the Dynamic Preview back to 0 and it rendered.

Hmmm, weird.

More details about my computer


Component Details Subscore Base score
Processor Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz 7.4 5.9
Determined by lowest subscore

Memory (RAM) 12.0 GB 7.5
Graphics NVIDIA GeForce GTX 460 7.6
Gaming graphics 4095 MB Total available graphics memory 7.6
Primary hard disk 702GB Free (931GB Total) 5.9
Windows 7 Professional

System
--------------------------------------------------------------------------------

Manufacturer OEM
Model OEM
Total amount of system memory 12.0 GB RAM
System type 64-bit operating system
Number of processor cores 4

Storage
--------------------------------------------------------------------------------

Total size of hard disk(s) 1863 GB
Disk partition (C:) 702 GB Free (931 GB Total)
Media drive (D:) CD/DVD
Disk partition (F:) 44 GB Free (932 GB Total)

Graphics
--------------------------------------------------------------------------------

Display adapter type NVIDIA GeForce GTX 460
Total available graphics memory 4095 MB
Dedicated graphics memory 1024 MB
Dedicated system memory 0 MB
Shared system memory 3071 MB
Display adapter driver version 8.17.12.6658
Primary monitor resolution 1920x1200
DirectX version DirectX 10

Network
--------------------------------------------------------------------------------

Network Adapter Realtek PCIe GBE Family Controller
Network Adapter Realtek PCIe GBE Family Controller

I don't know Steven, I would check my ram timings, I guess. It is a real mytery and makes no logical sense.

Yep crazy.

I want to buy After Effects, so I will probably get the CS5 Suite when it comes out. I'm so tired of Vegas crashes.

I have CS5, it's out. I don't understand your crashes, doesn't happen to me. Well it has, but it had nothing to do with Vegas.

Are you running your media off the same hard drive? You do know that is a no-no, right? Not saying it is the issue.

If you are using the same drive as in your old system, get a new drive for sure.

I had some crashes last month, I moved the media to another drive, crashes stopped. It wasn't Vegas, the hard drive had errors on it.

I have CS5, it's out. I don't understand your crashes, doesn't happen to me. Well it has, but it had nothing to do with Vegas.

Are you running your media off the same hard drive? You do know that is a no-no, right? Not saying it is the issue.

If you are using the same drive as in your old system, get a new drive for sure.

I had some crashes last month, I moved the media to another drive, crashes stopped. It wasn't Vegas, the hard drive had errors on it.

Could be. I use separate video drives, my main drive is brand new like my machine. But it could be the drive, I suppose I could copy the project to another drive and try it there. I don't get the crashes either. By the way, I was going to download the trial for CS5, but it's not available yet.