Experts: HELP what does this error mean?

hackazoid wrote on 12/29/2007, 3:14 PM

Still puzzled on this family video project. Real simple as it runs 24 min with 4 tracks containing (1) text overlay, (2) 720x528 JPEGS + quicktime videos+ text file separators, (3) video sound & some wave audio, and (4) a music track. Only do pan&zoom, no external stuff like Digital Juice.

Did a test on the quicktime by dumping 10 min of vids and 10 min of 3 MB JEPGS on the track and it rendered fine.

But when I try to render my file--even only the first 7 minutes via a loop, I get two messages:

* for MPEG2... either 'low on memory' or it just hangs

Note: Have 2 GB & Task Mgr shows 1,507,452k available and 394,376k in cache. Kernel has 108,456k of which 74,064 is paged. Is there some setting that is off?

* Tried to render the 7 min section as .WMV and just got the message below. It differs from the one in my prior post but I don't know what it is trying to say.

Spend 3 days on this so hoped to get it to work for tonight. I used to use Movie Maker 6....is it more reliable for simple videos like this & can I back convert somehow?

One reason for buying V8 was to be able to tap into the vast knowledge I've seen on this board so any suggestions are welcome.

Many thanks--message below:

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x7814507A
In Module 'MSVCR80.dll' at Address 0x78130000 + 0x1507A
Thread: ProgMan ID=0xD00 Stack=0x475F000-0x4760000
Registers:
EAX=000fd200 CS=0023 EIP=7814507a EFLGS=00210216
EBX=00000000 SS=002b ESP=0475f51c EBP=0475f524
ECX=0003f480 DS=002b ESI=00000000 FS=0053
EDX=00000000 ES=002b EDI=7ea600a8 GS=002b
Bytes at CS:EIP:
7814507A: F3 A5 FF 24 95 94 51 14 ...: 78 90 8B C7 BA 03 00 00 x.......
Stack Dump:
0475F51C: 00000000
0475F520: 30B66DD8 30610000 + 556DD8
0475F524: 0475F898 04660000 + FF898
0475F528: 5F03754A 5F020000 + 1754A (wmfplug3.dll)
0475F52C: 7EA600A8 7EA60000 + A8
0475F530: 00000000

Comments

blink3times wrote on 12/29/2007, 6:02 PM

I've seen the "Low Memory" warning as well, and I have 6gigs of Ram. It's obviously a memory bug in Vegas and I believe it has been reported and they're looking into it.

In the mean time....
I had to break up my project and do several renders to get around the problem. Make sure your original project is saved, then delete several tracks to make it simpler, Then render.

Open your original project and import/replace the rendered tracks as necessary and render through again. On my first try, my jpg's were about 4M each which caused all kinds of problems. I resized and compressed to around 500Kb and it all seemed to work much better.

You *MAY* be able to avoid all of this extra work if you make sure all your jpg's are under 500Kb each. On my first try my jpg's were around 4M each which seemed to cause all kinds of problems. Things went much smoother though when I resized and compressed to around 500kb each.

hackazoid wrote on 12/29/2007, 8:55 PM

Thanks.. good to know the memory msg isn't just me.

The JPEGs should be OK as is since I read on the forum to size at 720x528 px which produced files of ~200k at '8' quality on PS.

I've seen some posts on Quicktime issues as my Casio vids were converted to those but they render fine in separate tests I've made.

Any idea what the error message is saying?

Regards.