Vegas Pro 9.0c -Low On Memory While Rendering

Lu1 wrote on 12/9/2009, 5:04 PM
Hello :)

Would you be able to suggest a solution/hack to solve this pesky problem, please?

Win 7 Pro - 4 GB RAM 32-bit PC with 32-bit Vegas Pro on it only.

When rendering - no matter what format - low on memory appears over and over.

Dynamic RAM 0
Thread 1
Paging File Memory 3X 3250 MB
Nothing else running

The program worked for about two renders...and them "low on memory"
started to show up regardless of actions taken.

I even wiped out the whole drive and installed a fresh Vegas Pro copy.
Under Win 7 - I tried all compatibility setting for VP - no help.

There was a thread on this forum about Windows Headers Memory
Flags tweaked?

Where is that thread? Would it help?

I'm so frustrated - new customer - "half Vegasless" ('cause I can't render
out of Vegas pro 9.0 c at all).

The timeline has barely anything on it.

When I Google this problem, the results are littered with notes about it
for years now - but lack solutions.

Would you please point me in the right direction so I can fix this?

Thank you...Lu

Comments

Alf Hanna wrote on 12/11/2009, 5:40 PM
Since there doesn't seem to be any answer yet, do you take the time to reinstall to 64bit, and try that? I'm rendering just fine on Windows 7. 64 bit with HD into HD and other formats. Like you, just trying all sorts of rendering with little or no content yet. best of luck.
Jockewick wrote on 12/12/2009, 5:03 AM
Are you working with 8bit or 32bit floating point projects?
(Project properties/pixel format)
I get this error message allways if I try rendering a 32bit floating point project. I therefore only work with 8bits as pixel format.

Another time was while working with nested vegs creating a timelapse sequence. When I tried to render my memory usage got over about 75% of available RAM (I have 3.5gb) and I got the error message. That time I was forced to render every separate veg as a proxy .mxf and work with that.

I have Vista 32bit SP2, 4gb ram, Vegas 9.0c 32bit.

/Jockewick
A. Grandt wrote on 12/12/2009, 6:25 AM
I haven't tried Windows7 32 bit, but when I was running 32 bit XP my experience was that Vegas 9.0 was practically useless for encoding h.264 for anything above 720p. And even 720p was dicey most of the times.

I tried to render to MXF and other high bitrate formats (Mpeg2 and lossless codes if I recall) and then encode that in a freshly started Vegas. Sometimes that worked.

I would not be surprised if Vegas Pro 10 becomes 64-bit only.
Lu1 wrote on 12/12/2009, 7:39 AM
I'm unsure about 64-bit.

There seems to be enough posts and threads describing
similar problems using 64-bit Win.

My teacher is using XP (SP2) with VP 8.0c without any problems.
He uses 8.0 over 9.0 most of the time.
Then, others are reporting problems with that combination.

Huh?

Also, the program just started doing it - out of "thin air".
Others are reporting alike,
That shows me some instability in the program - especially
for Win 7.

And, I got the 32-bit program for a 32-bit machine - just like
what it asked for.

Plus...I can run Adobe Suite without any problems...and any other program.

Hopefully, the paid support will be able to help.
So far though, I'm still waiting for a fix - over three weeks.

Lu
A. Grandt wrote on 12/12/2009, 10:09 AM
I honestly don't know what to think of 9. It is a memory hog, and uses an extraordinary amount of it on even simple tasks. But it is the encoders that are really problematic in my opinion, for instance the MainConcept mp4 encoder, you can hardly do anything with it before it coughs up an out of memory error on 32bit.

8.0c is more stable imho, and fully capable of running on 4GB alone.
Lu1 wrote on 12/12/2009, 10:34 AM
There must be a "stability issue" between 8c and 9c...and memory gulping
and leaking and...who knows what else.

When Googled and on this forum - the bug reports VARY A LOT.

I just tried another angle only to get the same message.

So far, it looks like one needs to become an expert software coder/hacker first
before doing any video editing with VP.

Doing that makes a user very unproductive...and the various fix attempts dull the head to boot.

Extremely frustrating.

Dear Santa, please fix Vegas Pro so it works and remains stable, reliable
and is a joy to work with anytime the program runs, ... please.

Lu
Vfontjr wrote on 12/15/2009, 12:51 PM
I was finally able to render two 1920x1080 HD videos. The first was approx 36 minutes. The second was abot 16 minutes. I tried the 2mb hacks to no avail and manipulated just about every rendering setting I could in the main concept plug-in. What finally worked was setting dynamic ram to 0 and the number of rendering streams from 4 to 2. Of course it took almost 6 hours to render the longer video and about 2.5 hours for the shorter one.

I'm running a quad core with 4gb ram and Win 7 32bit. I don't have problems running any other software besides Vegsas Pro 9.
vicmilt wrote on 12/16/2009, 8:34 PM
Here's a weird workaround that I discovered, but don't ask me why it worked.

Same problem, only my project was on a Quad q6700, 2gb ram, sata raid 0 -
100 SECONDS LONG
1920x1080
Tried to render to MPEG 2

Out of memory renders.
I had a bunch of motion effects, blowups and lots of color correction.

So I prerendered hirez renders in 15 second segments (which was as much as it would give me at a time).
When it was all prerendered, I tried to Render As an MPEG2
Out of Memory.

Now here's the weird part. I muted all the video tracks below the prerendered track, and that's all. It rendered w/o a hiccup.
It worked, but I sure wouldn't want to do a feature like that - 15 seconds at a time. And I have no idea why muting tracks that have solid video above them would matter at all. But it worked.