Vegas 10 program bug

[Jim Ho]

Interesting.

My projects at this time are small. My media files are @1GB and my output wmv is 500MB (<4 minutes). Makes no sense to upgrade to $500 Vegas Pro.

I don’t mind breaking the project into two. But, why does rendering abort when I use media files of only 500MB or less.

Last nite, I ran one of the old projects from a time when Vegas wasn’t acting up. 956 MB media files to produce 459MB. Runs fine. Task manager shows 600MB usage that peaks at +700MB.

Then, I render a recent project. 976MB to produce 500MB. No major differences from the first project.

Crashes immediately. Task Manager shows memory usage started at +700MB.

Of course, I checked to make sure that the computer was idle before I began rendering (Processes 57, CPU 0%, Memory 14%).

[Jack Monkiewicz]

Jim, out of interest what file type are you using in your project? I too have the dreaded low memory issue when ONLY using MXF’s, but apparently Steve would have me believe that my computer is broken and Vegas is fine.

If you can get advice from John Rofrano, it is generally very good.

Best of luck

[Jim Ho]

Hi Jack,

I started off using AVCHD from Pany GH1. The size was very efficient, but it took much longer to extract 30p from its 60i container.

Yes, there was a limit to the size of the project, but rendering was not buggy. Funny thing was that I was using a 4GB machine.

With the new 8GB machine, Vegas worked ok with Nikon D5100 MJPG files. Then, a few weeks ago, the problems started. Can’t figure out why a multimedia 200MB project can run out of memory?

[Jim Ho]

Did it again!

Got a small project (500 MB media files) to render. Tinkered with it. Error message (not Low Memory warning).

Tried again and again after waking the machine from sleep. Finally, success. It rendered the full project!

Monitored Task Manager for the computer statistics. Can’t see any hint of a system issue. CPU usage about 80%. System memory usage BELOW normal.

[Nigel O’neill]

I think to assume that x GB on the timeline using xyz memory is a flawed (and crude) means of measuring memory usage. I regularly dump 15 GB of HDV into multiple tracks. My memory usage will vary depending on filters, effects and transitions applied to the footage.

Running Vegas x32 in a 32 bit operating system environment has resulted in some low memory errors for me, which I get around by running the x64 version of Vegas on my Windows 7 x64 Ultimate system. I have yet to experience a failed render in Vegas that I could not overcome – ever. I cannot say the same for Avid, Adobe and Pinnacle.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Jim Ho]

NIgel,

I do minimal PP. Just trim, sharpen, brighten and color correct (Studio Colorspace to Computer colorspace).

My system spec – i7 2600 8 GB. Windows 7 64-bit, GEForce GT40 dedicated 1gb total 4GB shared 3GB.

[Nigel O’neill]

And you have this problem with Vegas Pro 10 x64?

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Jim Ho]

No Nigel,

I have Studio 10 32b-bit.

[Jim Ho]

Problem disappeared.

Didn’t use it for a while for larger projects. Now, 1Gb projects are okay again. Memory usage is rock stable.

Don’t know what happened.

As I said, it’s a not a hardware problem.