64 bit out of memory error... again....

noiseboyuk wrote on 1/28/2012, 12:54 PM
Hi all, first post here. Have been having terrible problems with Vegas Platinum Suite 11 today - Win 7 64 bit, 16gb RAM, 3x displays via 2x ATI HD5450. Lots of crashing, sometimes only on a few keystrokes. Most of the project media is iPhone video and WAVs, when I removed a 720p mp4 that was also in it, the crashes improved (but weren't eliminated). The project is under 3 mins in length, 3 video tracks, 8 audio.

However, it's on export that I'm truly stuck, getting the "out of memory" error when trying to render that I see many others before me have had. So, I have tried the following:

Reducing RAM pre-render to 0
Reducing cores to 2
Checked the >2gb switch on all 6 exes and dlls as detailed by DC Doc on this thread - http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=12&MessageID=783168

I've checked all 6 files switches have "stuck" - all confirmed as >2gb. Complete cold restart for the computer - all to no avail. Most exports (not just HD) produce the memory error instantly, some (like AVI with a PAL DV codec) make it to 10% before failing.

Free memory is typically around 12gb.

System stable on all other apps, including some very RAM hungry ones. Very grateful for any help folks, driving me insane.

Thanks,

Guy

Comments

noiseboyuk wrote on 1/28/2012, 3:47 PM
A partial breakthrough - I purged unused media, dropping the memory use from 1.6gb to 1.1gb, and I can now render - Hallelujah. But it is this REALLY the RAM limit of this program? I appreciate it is only 32 bit, but I'm pretty shocked that the limits are so tiny. My little project is only 2 1/2 minutes long!

I'd have thought that >2gb would have helped, but it doesn't for me. Roll on proper 64 bit...
D7K wrote on 1/28/2012, 4:40 PM
I was having similar problems, but found out that my errors were due to:

1. Having an 3 ghz 4 core that was too hot...even with after market cooling.

2. upgrading both my CPU to a 6 core and drivers to the most current.

Things are much better. I'm using build 283.

I have 16 Gig, and VMS normally will use about 4 gigs. It might also be the number of tracks, I noticed with my 4 core that anything more than 4 tacks over taxed it.
noiseboyuk wrote on 1/28/2012, 5:01 PM
Thanks D7K - I'm on an i7 2600k - pretty poor program if it can't handle 3 minutes of material with that, isn't it? I too am on 283.

When you say tracks - you mean video tracks, right? I'm using 3 tracks, but 1 is purely for titles over black, and another is used to chroma key around 8-10 shots.
Markk655 wrote on 1/29/2012, 9:55 AM
I'm wondering if you might benefit from an uninstall and thn a clean re-install. You can check the knowledge base for the instructions for a clean re-install
noiseboyuk wrote on 1/29/2012, 12:33 PM
Interestingly, it hasn't crashed since I deleted the unused media - has been totally stable, if a little quirky. Do you people think there may have been a corrupt bit of media in there that was mucking everything up?

In general, VMS's memory use does seem very odd. When it initially loads, it takes only around 150mb of RAM... but this is a false reading. Clicking anywhere, such as the media bins, suddenly has it rocketing up to its true value (1.2gb currently) - then the program works. But it seems to drop its memory again from time to time, then go through the whole reloading procedure all over again (it also redraws the media thumbnails at this time)

Does anyone understand how the program manages its RAM? Never seen this sort of behaviour before. If no-one else has found this, I'll do a reinstall. Still, at least it has stopped crashing...
D7K wrote on 1/29/2012, 12:51 PM
I'd try a reinstall also, I had some problems (not memory) when I first got the program and a reinstall fix the issues I was having.
gofigure wrote on 2/1/2012, 4:33 PM
After having all the same memory issues with the program and reading the suggestions on what to and none worked I simply keep the program size under 1.7 -1.8 Gig.

I check Task Manager during editing to see what SVM is consuming. If it gets in the 1.8 range it becomes unstable and if you are at 1.9 or more something as simple as clicking on help can blow you up. Nice Sony

Amazing Sony wont fess up to the 2gig program limit but rather have us all chase down a bunch of fixes. I may move on to Adobe.