URGENT HELP!!!!! Low memory torment at DVinfo.net

Barry Rivadue · September 8th, 2010, 08:52 AM

I'll try and be brief:

I'm using Vegas 9.0. I have a new computer with 12 GB RAM.

I'm trying to save a file and all I get now is "low memory, close down other apps." I'm only running Vegas.

I try and increase the virtual memory, according to instructions, for the proper drive. NOTHING CHANGES. I still get the same damn "low memory." I follow every lead, such as restarting the computer. How does the increased memory actually kick in for keeps??

Also, when I try and put the "initial size" entry, I sometimes get "enter numeric value." Yes, I've done that. But that message keeps popping up.

This idiotic situation has stopped me in the middle of a huge project on deadline. Any insight will be cherished beyond belief.

Update: this only seems to be affecting Vegas 9.0. Vegas 8 on the same computer--no problem.

Thanks

Edward Troxel · September 8th, 2010, 09:24 AM

Please give the exact version of Vegas 9. Pro or VMS? 32-bit or 64-bit? 9.0, 9.0e, or something inbetween? What format are the clips? What format are you rendering to?

Two quick things you can try - go to the Options - Preferences - Video tab and

1. Reduce the RAM Preview to a small number (like 16)
2. Reduce the number of rendering threads to 1

Will it work then?

Barry Rivadue · September 8th, 2010, 09:46 AM

Yes, your tip made the rendering kick in again. Is this good for the time being?

I have Vegas Pro 9.oc; not sure what bit, but probably 64. The clips rendered to MPEG-2 from avi.

Thanks so much for this quick fix.

Edward Troxel · September 8th, 2010, 09:56 AM

In Vegas, if you go to help - about, it will list the precise version of Vegas. If you don't explicitly see it say 64-bit, you're on the 32-bit version. Since you're on a 64-bit OS, updating to the 64-bit version of 9.0e may also help. The 64-bit versions can access more ram - the 32-bit versions are limited to a total of 2 Gig no matter how much you have.

Barry Rivadue · September 8th, 2010, 10:12 AM

Thanks, I'll look into that.

Update: It's acting up again (after a few brief renders), but I guess what I should do is download the 64-bit 9.0e. I believe I have 32-bit; I was probably thinking of the 64-bit Windows 7 that I have. Meanwhile, I've migrated most of the project to Vegas 8 (thank goodness for making backups), so not a lot of time has been lost.

Again, much appreciated. This is a great place!

Barry Rivadue · September 9th, 2010, 02:34 PM

Okay, for the record I downloaded 64-bit 9.0e and everything seems back to normal, so I hope such a solution sounds reassuring to anyone with similiar problems.

Craig Longman · September 9th, 2010, 08:58 PM

If you have 12GB, then increasing the pagefile would not have helped at all. The problem is with 32 bits to address memory, you are limited to 4GB total per process, period, no matter what you do. And up to 2GB of that is reserved for windows use only. If you only had 1 or 2GB of RAM, then increasing your pagefile would help. There are 'hacks' to allow each process to use 3GB instead of the normal 2GB windows leaves, but that is just that, a hack.

The 64bit version can theoretically address 17 179 869 184GB of RAM, although I believe in practise no more than 48 bits are actually possible, meaning the 64bit applications can only use the paltry maximum of 262 144GB of RAM. Still, a bit more the the 4GB a 32bit process has for a maximum.

Bottom line, if you can get by with the 64bit plug-ins available (not all the 32bit ones are available for 64bit Vegas), then use the 64bit. =)

Craig Longman · September 9th, 2010, 09:13 PM

And I actually just ran across posted by "Rainer" this on the Sony Forums. It's the easiest way I've found yet to enable LAA on applications. It can adjust the memory that windows reserves down to 1GB for 32bit windows, leaving 3GB for the app, or completely put the OS RAM outside, leaving 4GB for the app on 64bit windows.

Here is the link to the post/app:

Large Address Aware - techPowerUp! Forums

Just in case you absolutely-gotta-must-need a plug-in on in 32bit land.

Barry Rivadue · September 13th, 2010, 09:33 AM

Thanks for the info!

Larry Reavis · September 13th, 2010, 01:53 PM

sometimes it is necessary to use 32-bit versions of Vegas - I do it all the time in order to use the marvelous Smart Deinterlace plugin. Here's how to get beyond the 2GB limit (with a free utility, CFF Explorer):

Sony Creative Software - Forums - Vegas Pro - Video Messages

Craig Longman · September 13th, 2010, 07:16 PM

Larry, the link I provided does essentially the same thing, allowing the LAA flag to be set. I think the techPowerUp one is just a lot simpler to use, point it to an EXE, click one box, press one button.

But the both do achieve the same end.

Larry Reavis · September 14th, 2010, 11:42 AM

does it also work with .DLLs? I've read that the I/O plugs are even more important than the .EXE

Craig Longman · September 14th, 2010, 04:48 PM

I'm not sure how. I'm fairly confident that this is a flag in the PE that Wow64 uses when setting up the process space. Instead of 0-2GB for app and 2GB-4GB (virtual address) for OS, it instead creates either 0-3GB user and 3-4GB OS (in 32bit) or 0-4GB user with OS outside in 64 bit.

Once that memory layout is set, it's set. DLLs are still (unfortunately) mapped right in the middle of that generally, so you still can't get more than 2GB contiguous, but then that is rarely required =) There is no real sense (and a some reasonable negatives) to re-basing the DLLs to lower down.

However, I think it is changeable on DLLs, simply because they also use a PE header for basic image information.

I can't find anything to actually back me up on the 'net, so I can't be positive. But given that it really is a decision to adjust the memory layout at process creation, I'd have a real hard time understanding how it could be needed (or matter) in the DLL also. How would the memory remap? If the EXE hands a memory pointer with the bit 31 set, what would happen? The DLL just wouldn't be able to see that memory? It doesn't make any sense to me.

Gerald Labrador · September 21st, 2010, 04:46 PM

I had this same problem and was solved by a kid on youtube.

I can't find the link now, but...basically you copy your timeline, open a new instance/window for Vegas, paste the timeline to the new Vegas project, then export/render. This solved the low memory error for me.

I was exporting to 1080 mp4 from a timeline consisting of AVCHD, HDV, and Canon EOS 1080 files.

September 8th, 2010, 08:52 AM	#1
Barry Rivadue Major Player Join Date: Jun 2002 Posts: 508	URGENT HELP!!!!! Low memory torment I'll try and be brief: I'm using Vegas 9.0. I have a new computer with 12 GB RAM. I'm trying to save a file and all I get now is "low memory, close down other apps." I'm only running Vegas. I try and increase the virtual memory, according to instructions, for the proper drive. NOTHING CHANGES. I still get the same damn "low memory." I follow every lead, such as restarting the computer. How does the increased memory actually kick in for keeps?? Also, when I try and put the "initial size" entry, I sometimes get "enter numeric value." Yes, I've done that. But that message keeps popping up. This idiotic situation has stopped me in the middle of a huge project on deadline. Any insight will be cherished beyond belief. Update: this only seems to be affecting Vegas 9.0. Vegas 8 on the same computer--no problem. Thanks

September 8th, 2010, 09:24 AM	#2
Edward Troxel Sponsor: JET DV Join Date: Dec 2001 Location: Southern Illinois Posts: 7,953	Please give the exact version of Vegas 9. Pro or VMS? 32-bit or 64-bit? 9.0, 9.0e, or something inbetween? What format are the clips? What format are you rendering to? Two quick things you can try - go to the Options - Preferences - Video tab and 1. Reduce the RAM Preview to a small number (like 16) 2. Reduce the number of rendering threads to 1 Will it work then? __________________ Edward Troxel [SCVU] JETDV Scripts/Scripting Tutorials/Excalibur/Montage Magic/Newsletters

September 8th, 2010, 09:56 AM	#4
Edward Troxel Sponsor: JET DV Join Date: Dec 2001 Location: Southern Illinois Posts: 7,953	In Vegas, if you go to help - about, it will list the precise version of Vegas. If you don't explicitly see it say 64-bit, you're on the 32-bit version. Since you're on a 64-bit OS, updating to the 64-bit version of 9.0e may also help. The 64-bit versions can access more ram - the 32-bit versions are limited to a total of 2 Gig no matter how much you have. __________________ Edward Troxel [SCVU] JETDV Scripts/Scripting Tutorials/Excalibur/Montage Magic/Newsletters

September 9th, 2010, 08:58 PM	#7
Craig Longman Regular Crew Join Date: Jul 2010 Location: London, ON Posts: 175	If you have 12GB, then increasing the pagefile would not have helped at all. The problem is with 32 bits to address memory, you are limited to 4GB total per process, period, no matter what you do. And up to 2GB of that is reserved for windows use only. If you only had 1 or 2GB of RAM, then increasing your pagefile would help. There are 'hacks' to allow each process to use 3GB instead of the normal 2GB windows leaves, but that is just that, a hack. The 64bit version can theoretically address 17 179 869 184GB of RAM, although I believe in practise no more than 48 bits are actually possible, meaning the 64bit applications can only use the paltry maximum of 262 144GB of RAM. Still, a bit more the the 4GB a 32bit process has for a maximum. Bottom line, if you can get by with the 64bit plug-ins available (not all the 32bit ones are available for 64bit Vegas), then use the 64bit. =) __________________ CraigL

September 9th, 2010, 09:13 PM	#8
Craig Longman Regular Crew Join Date: Jul 2010 Location: London, ON Posts: 175	And I actually just ran across posted by "Rainer" this on the Sony Forums. It's the easiest way I've found yet to enable LAA on applications. It can adjust the memory that windows reserves down to 1GB for 32bit windows, leaving 3GB for the app, or completely put the OS RAM outside, leaving 4GB for the app on 64bit windows. Here is the link to the post/app: Large Address Aware - techPowerUp! Forums Just in case you absolutely-gotta-must-need a plug-in on in 32bit land. __________________ CraigL

September 8th, 2010, 09:46 AM	#3
Barry Rivadue Major Player Join Date: Jun 2002 Posts: 508	Yes, your tip made the rendering kick in again. Is this good for the time being? I have Vegas Pro 9.oc; not sure what bit, but probably 64. The clips rendered to MPEG-2 from avi. Thanks so much for this quick fix.

September 8th, 2010, 10:12 AM	#5
Barry Rivadue Major Player Join Date: Jun 2002 Posts: 508	Thanks, I'll look into that. Update: It's acting up again (after a few brief renders), but I guess what I should do is download the 64-bit 9.0e. I believe I have 32-bit; I was probably thinking of the 64-bit Windows 7 that I have. Meanwhile, I've migrated most of the project to Vegas 8 (thank goodness for making backups), so not a lot of time has been lost. Again, much appreciated. This is a great place!

September 9th, 2010, 02:34 PM	#6
Barry Rivadue Major Player Join Date: Jun 2002 Posts: 508	Okay, for the record I downloaded 64-bit 9.0e and everything seems back to normal, so I hope such a solution sounds reassuring to anyone with similiar problems.

September 13th, 2010, 09:33 AM	#9
Barry Rivadue Major Player Join Date: Jun 2002 Posts: 508	Thanks for the info!

September 13th, 2010, 01:53 PM	#10
Larry Reavis Regular Crew Join Date: Dec 2009 Location: Encinitas California Posts: 121	sometimes it is necessary to use 32-bit versions of Vegas - I do it all the time in order to use the marvelous Smart Deinterlace plugin. Here's how to get beyond the 2GB limit (with a free utility, CFF Explorer): Sony Creative Software - Forums - Vegas Pro - Video Messages

September 13th, 2010, 07:16 PM	#11
Craig Longman Regular Crew Join Date: Jul 2010 Location: London, ON Posts: 175	Larry, the link I provided does essentially the same thing, allowing the LAA flag to be set. I think the techPowerUp one is just a lot simpler to use, point it to an EXE, click one box, press one button. But the both do achieve the same end. __________________ CraigL

September 14th, 2010, 11:42 AM	#12
Larry Reavis Regular Crew Join Date: Dec 2009 Location: Encinitas California Posts: 121	does it also work with .DLLs? I've read that the I/O plugs are even more important than the .EXE

September 14th, 2010, 04:48 PM	#13
Craig Longman Regular Crew Join Date: Jul 2010 Location: London, ON Posts: 175	I'm not sure how. I'm fairly confident that this is a flag in the PE that Wow64 uses when setting up the process space. Instead of 0-2GB for app and 2GB-4GB (virtual address) for OS, it instead creates either 0-3GB user and 3-4GB OS (in 32bit) or 0-4GB user with OS outside in 64 bit. Once that memory layout is set, it's set. DLLs are still (unfortunately) mapped right in the middle of that generally, so you still can't get more than 2GB contiguous, but then that is rarely required =) There is no real sense (and a some reasonable negatives) to re-basing the DLLs to lower down. However, I think it is changeable on DLLs, simply because they also use a PE header for basic image information. I can't find anything to actually back me up on the 'net, so I can't be positive. But given that it really is a decision to adjust the memory layout at process creation, I'd have a real hard time understanding how it could be needed (or matter) in the DLL also. How would the memory remap? If the EXE hands a memory pointer with the bit 31 set, what would happen? The DLL just wouldn't be able to see that memory? It doesn't make any sense to me. __________________ CraigL

September 21st, 2010, 04:46 PM	#14
Gerald Labrador Regular Crew Join Date: Nov 2008 Location: San Diego, CA Posts: 55	I had this same problem and was solved by a kid on youtube. I can't find the link now, but...basically you copy your timeline, open a new instance/window for Vegas, paste the timeline to the new Vegas project, then export/render. This solved the low memory error for me. I was exporting to 1080 mp4 from a timeline consisting of AVCHD, HDV, and Canon EOS 1080 files.