Not enough memory? WTFIS!!!

[Paul James chatman]

I’m having the same problem with Vegas giving me “The system is low on memory” errors. And there is enough RAM. I was trying to render a…..17 second clip. And it halts the render with that message!! It’s just a two 4 sec vid clips and a pic with a rose falling beside it. Nothing big at all.

I never had this problem with Vegas 8.

hello

[Joe Mantaratz]

Ideally you should not dump large pic files like that in the time line you need to resize them to your project setting using photoshop or whatever software you have to do that. You didn’t mention how many of those 530 pics you placed on the timeline. Rendering pics at full res will most assuredly run you out of memory in a hurry.

[John Rofrano]

> Each pic is 3.7Mb in size.

Those are extremely large pictures. A DVD cannot even display 1 mega-pixel so 7MP are 7x the resolution that you need. You are asking Vegas to do an incredible amount of resizing 30 time a second.

> Ultimate S wont work in Vegas 9

You need to upgrade to Ultimate S Pro 4.1 to get support for Vegas Pro 9.0. Otherwise Ultimate S 3.1 works in Vegas 5 thru 8.

> Now…. anyone have an idea what caused all of this, and how to avoid a repeat?

Since A DVD can only display 720×480, keep your images around twice that (1440×960) which should still give you plenty of resolution to pan and scan.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Ben Longden]

Thanks for the quick replies, Guys.

I’m not 100% convinced its a PC issue. I do acknowledge that the PC is dealing with some huge numbers, and this may be the problem.

When Vegas 6 was first released, a client wanted a 400 image slideshow done. I shot that one with the same camera, same PC and applied Ultimate S to do the transitions and pan-n-scan.

It did work, flawlessly and rendered to .avi in less than an hour.

How many pix in the current problem were used?
All 530 (1.96Gb total), with six titles produced in Vegas. The final product is 720×576 SD widescreen PAL.

Thoughts?

Ben

Do unto others…

[Al Bergstein]

Ben, I agree with the idea that the pics you are using aren’t sized right. Get those things down to manageable sizes, under 1MB to be safe. Barring that, this might be a job for 64 Bit Win7 or Vista, instead of XP (which you said you used) with Vegas. XP will only address at most 2 GBs of RAM for all applications running in the memory space (4GBs total, but 2 reserved for the OS) and that includes all your antivirus, and other oddball applets that load at startup. XP also had other limitations of resources that would run out long before you ran out of RAM, and yes, there was a PAE version but that was mainly for the Server products back then. It was a hack to get the OS over the hump until the true 64 bit versions arrived.

So 64 bit does free you up to have lots more head room, and I bet that’s why Sony wants all new users of Win7 to head that way. IMHO a video editor tool should be addressing all available memory. There may be other reasons to not go to 64 bit, but this seems like a reason to have someone else with a 64 bit system try it out for you.

Hope that helps.

Alf
Panasonic HMC-150 & FCP on MacPro Dual Quads, 12 GB 7.0.1 on 10.6.2
also – Vegas Video 9.0c on Win7/64bit

[Rob Mack]

One thing to keep in mind is that if your 1.96 GB of files on disc are compressed images they need to be uncompressed to RAM as Vegas works with them. In other words they’re probably bigger than you think, byte-wise.

Reducing their physical dimensions to what you need ought to be a help. Reducing your preview RAM setting to a low number would also free up some memory.

Still, you’d hope that VP9 could do better at this with it’s supposed support for larger images.

Rob Mack

[Ben Longden]

The saga gets better, and I’m thinking DVDA is the villain….

After finally rendering the 530 JPGs to an .avi file, I went back and tried to render that .avi into an MPEG2 file for 1) burning to DVD-ROM and also 2) to DVDA for a DVD.

As soon as I pressed GO, it came up with the same blasted error message. Not enough memory.

Something made me actually look at the HDD real estate available. An alarm bell went off, as I had 50GB left on the C drive. So I hunted down the temporary but permanent files that DVDA makes after each job, and mercilessly nuked them.

I now have nearly a terabyte back on the C drive, and needless to say Vegas is rendering to any format with ease.

Moral of the story is to purge the DVDA files regularly….

Ben

Do unto others…

[Gary Brown]

I’ve been happy as a clam with Vegas 6 – 9. Still am, I have 30 installations of 8 & 9. Lately, however some large 12 MP jpgs have caused some problems rendering. It appears that even 64 bit versions of Vegas only use 4GB to render. I would love to be corrected and shown how to get my Win 7 (Pro & Ult) machines to use more than 4GB during any rendering process. It is this limit that causes the issue with really large files. It simply fills up. Yes, scale your images to a sane size, and you will ‘solve’ your render problem. The app is designed to ‘see’ the frame size of a 2k to 3K image stream. But it really seems that the extra 12 GB I have here at the studio, and the extra 8 I have at home would be really useful in either using the larger image files or speeding the entire process. Vegas doesn’t appear to use most of the extra memory that can be available in the 64 bit architecture.

“Better, Faster, Cheaper … Pick Two!”

Gary R. Brown, SCVE
Video Systems Engineer
Portsmouth Public Schools
Portsmouth, Virginia
23704-2135