Sony Vegas 9 has Memory issues.

FilmingPhotoGuy wrote on 6/16/2009, 1:12 AM

I was halfway thru a SV8 project when i upgraded to SV9. I completed the project in SV9. When attempted to render out to any format, after about 10 seconds I get "The system is low on memory. You may be able to reduced memory usage by closing other applications". I ran "EndItAll v2" but get the same.

I have since upgraded to i7 2.66 with 6GB of 1333 DDR3 Ram. I get the same error. Task manager reports i'm only using 1.3GB of Ram.

Project 1280x720. 3 video tracks, 2 audio tracks. About 30 minutes.
AVCHD 1920x1080 shot with Canon HF10

Text titler is "Bluff" rendered to same format as project. Tried deleting all text on same layer.

-Craig

ushere wrote on 6/16/2009, 2:52 AM

what little i've done with avchd in 9 has been done after converting it to mxf. so far, apart from preview / speed up problems i've had no problems at all..... xp pro 32 sp 3 / i7 920 / 6gb ram (moving to 64 bit win 7 eventually)

VanLazarus wrote on 6/16/2009, 3:21 AM

I've gotten that memory error a number of times in my limited use of Vegas 9.0.

Project settings: 1920x1080 60p, 8 bit
Source footage: AVCHD 1920x1080 60p (from Sanyo HD2000)
Don't know what the exact error was, but basically said that system was getting low on memory.
i7 920 6gb
Vista 64 bit and Windows 7 64 bit

My workaround was restarting Vegas.... But I haven't even been able to edit/render a complete project due to crashes with my MP4 clips.

VideJoe wrote on 6/16/2009, 4:51 AM

I have a simple project (one Picture, one Video track, one Audio track and one Text Overlay track, Color Correction) which was made in V8 and renders to 1440x1080 25P (also the source media) quite well.
But opening the same project in V9 I get an "unknown error" trying rendering tot the same template.
I wish I kept my upgrade money in my pocket!

blink3times wrote on 6/16/2009, 5:14 AM

"Maybe SCS will read it and add it to the 9.0a bugfix soon."

Yes... and maybe if I put a pink flag in my window and the space shuttle flies overhead and takes a picture.... SCS will see it on the tv and come to my rescue :)

You NEED to put a problem ticket in on the issue if you wish them to see it.

LReavis wrote on 6/16/2009, 10:28 AM

to reduce the "short on memory" problem, I closed all but the video preview & toolbars in the View menu in V9. I then saved a problem project in V8 after un-checking the same View items. Finally, I was able to open a troublesome project in V9 and render it maybe 25% of a complete render before "low memory" promp appeared - better than I'd ever done in V8.

Cutting the project into tiny pieces and rendering each works for me in V8 (probably would in V9, but not tested yet). Especially troublesome segments can be cut-and-pasted into their own V8 instance, then rendered (even with no waveforms/thumbnails displayed, simply having a long project can cause fits).

I use 8 bit, 1920x1080i, mostly HDV but with some Cineform clips & lots of stills; either on a Q6600/3gHz on an Asus MB/4GB RAM, or on an old P4/3gHz/2GB RAM on an Intel MB; same story on either (for that reason, I stick with the faster Q6600). Always WinXP, SP3

MattWright wrote on 6/17/2009, 3:23 AM

Hi There.

I also had these problems for ages, and then on a message thread I found this fix and tried it "http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=650217"
I have not had this problem since, to be honest it has transformed my rendering.

TRY IT.

Matt

SuiteD wrote on 6/18/2009, 4:37 AM

How are you using the memory above 3.x GB with XPP32?

ken c wrote on 6/18/2009, 6:15 AM

I find that Vegas *still* doesn't release memory back after being launched, used, closed down.... my system grinds to a halt only after I use Vegas, within a day... and that's with a dualcore 4 gigs of ram winxp fast system....

I can use After Effects, C4D, all my other intensive render apps and they all cleanly release memory back once they're done... but I know that "If I use Vegas (5,6,7,8,9), I'll have to reboot my computer sometime within the next day or two", which is cumbersome since I use Vegas at least a few times a week.

Any chance they'll fix this "Vegas sucks up memory and doesn't release it back cleanly after it's been shut down" bug? And this doesn't show up in the memory pool/taskmgr.exe stats, it's just something I've seen from years of using Vegas, is my system runs great til I use Vegas, then after closing Vegas, my system eventually slows down, memory lockups, and I need to reboot within a day or so of using Vegas.... any ideas?

I can run my system for many days without problems, *unless* I use Vegas, which then I see my other apps slow down, and the computer needs a reboot. So I've isolated and tested it, it's definitely Vegas, after using it (and other apps) for years, together, singly etc... Vegas sucks up memory and doesn't release it back once it's closed.

thx...

TheHappyFriar wrote on 6/18/2009, 9:34 AM

I find that strange as I only reboot when I *NEED* to now. I always standby or leave it on. Vegas on/off, doesn't matter. Might be an issue with windows thinking vegas still needs the memory. Have you ever re-formatted?

RexA wrote on 6/19/2009, 1:45 AM

Matt said:
Hi There.

I also had these problems for ages, and then on a message thread I found this fix and tried it "http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=650217"
I have not had this problem since, to be honest it has transformed my rendering.

TRY IT.

Matt

----

The link you posted was the end of a very long thread and that post didn't say anything about a fix for the problem. Can you point us more specifically to the good information?

Terje wrote on 6/20/2009, 12:08 AM

>> I find that Vegas *still* doesn't release memory back after
>> being launched, used, closed down.

This seems very odd. Normally when an application is shut down, Windows will reclaim all the memory it has used, and in normal situations there is not much an app can do about that. So, with a few minor exceptions, it isn't really possible for Vegas-related memory issues to persist after Vegas has been shut down. That would be, unless you were on Windows 95 or 95, which you are not.

So, assuming you are right, and I have no reason to assume otherwise, something else is probably going on.

I assume you have checked the task list and made sure Vegas doesn't hand around. You should also take a look at the task list and see if there are other processes starting up (svchost and the likes, though I don't think Vegas still uses 16 bit DLLs) that do not die after Vegas goes away.

If what you are seeing is indeed correct, the most likely problem is one out of two
- you have a hardware issue exacerbated by Vegas
- there is a bug somewhere in Windows exposed by your use of Vegas

The last one isn't entirely unlikely. Vegas uses VfW, a technology that was already old in 1997. It would not surprise me the least if there are issues with VfW in Windows that Microsoft hasn't looked at in years and years.