Vegas low on memory?!

matt9b

Well-known member
I have win XP and 6GB ram installed.. brand new i7 920 machine. Yet when rendering a 50 second clip, it stops half way and gives an error "unable to render vss.wmv. Your system is low on memory. Close some applications and try again."

I have no other apps open; I have tried restarting windows, changing the page file size. I have no idea what to do, since this is a new PC with plenty of ram, its a small vegas project, and there is a fresh install of everything.

Has anyone experienced this before? I'm not having much luck lately.. your input is deeply appreciated.
 
Well, no; the 32-bit version uses up to 4 GB combined RAM; about 250 MB is used for the OS and other administrative stuff, and you'll lose as much RAM as the memory size of your video card(s).

But 6GB will definitely not be fully used.
 
Hi guys, I'm aware that win xp 32 doesn't support 6GB ram. I had 64-bit installed, but as you are no doubt aware, 64bit win xp is incompatible with many video and audio softwares - including MBL - so now back to using 32-bit, which is common in the vid editing industry... it shouldn't be necessary to use win xp 64 to edit video in vegas.. and I'm sure there are plenty of ppl out there using 32 bit also. Otherwise how do u use MBL? There must be another solution..?
 
Hi guys, I'm aware that win xp 32 doesn't support 6GB ram. I had 64-bit installed, but as you are no doubt aware, 64bit win xp is incompatible with many video and audio softwares - including MBL - so now back to using 32-bit, which is common in the vid editing industry... it shouldn't be necessary to use win xp 64 to edit video in vegas.. and I'm sure there are plenty of ppl out there using 32 bit also. Otherwise how do u use MBL? There must be another solution..?

Yes, the solution is to use a 64 bit OS and install both the 32 bit and 64 bit version of Vegas. That's what I've been doing for several years now. Including my laptop which is running XP64. I am running Windows7 on my primary editing machine.
 
Yes, the solution is to use a 64 bit OS and install both the 32 bit and 64 bit version of Vegas. That's what I've been doing for several years now. Including my laptop which is running XP64. I am running Windows7 on my primary editing machine.

I tried that, first off. However, MBL didn't work on win 64bit Vegas 32bit. It only works on win 32 vegas 32 here.
 
Vegas, like most complex apps, does leak memory (especially the Sony AVC encoder is a nightmare for that). So if you get low memory errors, or even crashes when encoding with SonyAVC, it's because of various leaks. Not much you can do, other than try to change your project or plugins a bit, so you change the conditions that might trigger a leak.
 
Oh wait.. what? I use MBL on 64bit XP and 64bit Windows7.

Not sure how. I tried it on 64bit XP many times - it didn't work - you may see some of my threads about this a while back, hence the reason for my changing to 32bit XP, and now it works great.

I'm not saying yours doesn't work; just saying I don't know why it behaves differently for you. I'm not going to go back to XP64 though because I have tried it many times and know what the outcome will be.
 
Vegas, like most complex apps, does leak memory (especially the Sony AVC encoder is a nightmare for that). So if you get low memory errors, or even crashes when encoding with SonyAVC, it's because of various leaks. Not much you can do, other than try to change your project or plugins a bit, so you change the conditions that might trigger a leak.


Cheers- I have fixed it now. For those in need, the fix was: options, preferences, video, -> maximum number of rendering threads = 1.
 
Not sure how. I tried it on 64bit XP many times - it didn't work - you may see some of my threads about this a while back, hence the reason for my changing to 32bit XP, and now it works great.

I'm not saying yours doesn't work; just saying I don't know why it behaves differently for you. I'm not going to go back to XP64 though because I have tried it many times and know what the outcome will be.


Its not the OS is the version of Vegas. You can install 32bit version of Vegas on a 64bit Windows 7. It will install under the program files X86. And MBL should work. However if you use Vegas 64bit..Then MBL wont work.
 
Its not the OS is the version of Vegas. You can install 32bit version of Vegas on a 64bit Windows 7. It will install under the program files X86. And MBL should work. However if you use Vegas 64bit..Then MBL wont work.

Yes, I thought this too, however, I was using vegas 32bit on XP64 when MBL didn't work. I re-formatted and tried everything. I started to think it was a graphics card issue until I installed XP32 and it now works fine.
 
Hmmm strange...It worked for me..but I was using windows 7. But my problem was ...After 2 days..I got this unregistered white block stuck all overy my videos. I had to revove the 32bit. It didnt like it when I had 32 and 64 intalled on the same computers. I know I have seen others post they run both versions on the same drive..but I cant for some reason.
 
Memory Leak - probably

Memory Leak - probably

I love Sony Vegas - I've used it since version 3 when Premiere was a complete joke and in the stone age in comparison.

However, they've got a serious, "critical" Rendering, bug situation going on since v.6, it seems, by looking at the forums. It's a guestimate, but as a programmer who's battled memory leaks, it looks like they have a nasty one here - Fix it , Sony.

I'll give you guys at Sony a possible clue, it's to do with your Nested projects. You haven't product tested them properly - shabby job. I took my nested projects (about 15 of them) out of my Feature length movie and hey presto the rendering wouldn't collapse with the "low memory" error message.

That is not all. Nested projects are unstable in general - personally, I'm avoiding them from now on - reference a rendered avi and "replace" the media with updates when required.

Anyway, my 2 cents worth....
 
I still can't render anything with MBL. I tried the 1 track limitation, but still get the "low memory" fault.
Any other tricks? or treats?
 
Back
Top