Tips for stability with HD clips in Vegas 7/8

dirtynbl wrote on 12/18/2007, 4:32 PM

I'm not going to complain that Vegas 8 works like most "a" versions of Sony software...I've come to expect that anything before "b" or "c" usually ought to have been left a beta version. But 8 behaves like Acid 6.0a did...horribly.

With SD footage its wonderful, but with the HD footage it captures itself its awful. 7 has different issues, but doesn't crash quite as often...still its getting pretty frustrating to crash every few minutes. I've been saving constantly, but now many times when I try to open a file I saved before the crash it causes an exception within Vegas 8. Is there a setting I can click or something that says "don't have an exception" every 5 minutes? Or ignore pieces of m2t files that are perfectly normal, but might randomly cause you to crash?

For further info here's the latest message I got:
Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2303B990
In Module 'mcmpgvdec.dll' at Address 0x23000000 + 0x3B990
Thread: VideoCache ID=0x12B0 Stack=0x3D4E000-0x3D50000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010212
EBX=00000000 SS=0023 ESP=03d4eff4 EBP=03d4f00c
ECX=03d4efd0 DS=0023 ESI=00000010 FS=003b
EDX=7c90eb94 ES=0023 EDI=00003074 GS=0000
Bytes at CS:EIP:
2303B990: 89 3B EB 95 8D B6 00 00 .;......
2303B998: 00 00 8D BF 00 00 00 00 ........
Stack Dump:
03D4EFF4: 03D4EF94 03C50000 + FEF94
03D4EFF8: 34CB8B58 33E10000 + EA8B58
03D4EFFC: 03D4F05C 03C50000 + FF05C
03D4F000: 00AA0000 00400000 + 6A0000 (vegas80.exe)
03D4F004: 00AA0000 00400000 + 6A0000 (vegas80.exe)
03D4F008: 00005000
03D4F00C: 03D4F09C 03C50000 + FF09C
03D4F010: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
03D4F014: 00AA0000 00400000 + 6A0000 (vegas80.exe)
03D4F018: 00000010
03D4F01C: 34CB8B58 33E10000 + EA8B58
03D4F020: 34E0FCC8 33E10000 + FFFCC8
03D4F024: 000002D0
03D4F028: 00000500
03D4F02C: 00000006
03D4F030: 34CB8B58 33E10000 + EA8B58
> 03D4F040: 00AA0000 00400000 + 6A0000 (vegas80.exe)
03D4F044: 34CB9FE8 33E10000 + EA9FE8
> 03D4F048: 23030F82 23000000 + 30F82 (mcmpgvdec.dll)
03D4F04C: 34CB8B58 33E10000 + EA8B58
03D4F050: 345DAD48 33E10000 + 7CAD48
> 03D4F070: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 03D4F074: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 03D4F078: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 03D4F080: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 03D4F0A0: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 03D4F0B0: 23028344 23000000 + 28344 (mcmpgvdec.dll)
> 03D4F0D0: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 03D4F108: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 03D4F10C: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 03D4F114: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 03D4F120: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 03D4F150: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
> 03D4F170: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
> 03D4F1A0: 23026179 23000000 + 26179 (mcmpgvdec.dll)
> 03D4F1C0: 23216DFD 23200000 + 16DFD (mcmpegin.dll)
> 03D4F200: 23218527 23200000 + 18527 (mcmpegin.dll)
> 03D4F230: 2323A5C2 23200000 + 3A5C2 (mcmpegin.dll)
> 03D4F244: 7C931C41 7C900000 + 31C41 (ntdll.dll)
> 03D4F248: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 03D4F28C: 01050104 00400000 + C50104 (vegas80.exe)
03D4F290: 03D4F2C0 03C50000 + FF2C0
03D4F294: 3D7D05D8 3D630000 + 1A05D8
03D4F298: 00000033
03D4F29C: 00000000
> 03D4F364: 7C91B690 7C900000 + 1B690 (ntdll.dll)
> 03D4F36C: 7C91B686 7C900000 + 1B686 (ntdll.dll)
> 03D4F370: 7C91B298 7C900000 + 1B298 (ntdll.dll)
> 03D4F37C: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 03D4F398: 7C9321C2 7C900000 + 321C2 (ntdll.dll)
> 03D4F3D4: 7C91056D 7C900000 + 1056D (ntdll.dll)
> 03D4F404: 7C9321C2 7C900000 + 321C2 (ntdll.dll)
> 03D4F418: 00670009 00400000 + 270009 (vegas80.exe)
- - -
03D4FFF0: 00000000
03D4FFF4: 00598AE0 00400000 + 198AE0 (vegas80.exe)
03D4FFF8: 00ADA7FC 00400000 + 6DA7FC (vegas80.exe)
03D4FFFC: 00000000

Honestly, I can't wait until Vegas is REALLY ready for HD.

Comments

mekelly wrote on 12/19/2007, 5:19 PM

The problem is associated with your machine. I have captured hundreds and hundreds of HD clips and never had a crash ever. I've also never had Vegas crash during editing.

Send your crash report to Support and see what they say.

dirtynbl wrote on 12/19/2007, 9:28 PM

I will, but I can guarantee its not machine related because I've tried it on 3 Windows machines. 2 are brand new and one has been running 7 and 6 before that with never a problem, especially in SD.

The problems are random and not associated with a specific clip. Ie, a clip will crash Vegas one time and not another. I've recaptured clips, tested them in After Effects and Premiere and its just Vegas 8.0a is yet another crappy "a" release from Sony. I use and love all their products they just don't work right away.

Cheno wrote on 12/19/2007, 9:50 PM

dirtynbl,

What camera did your source clips originate from?

There are known Canon issues with HDV Canon cams. My workaround is to render to Cineform Intermediate and they work fine in 8 at that point, plain ol' Canon m2t's though? Really troubling up the system. Apparently it's how the header is written, but I don't see as many complaints on other NLE's with the Canon HDV format.

cheno

deusx wrote on 12/19/2007, 10:25 PM

I capture and edit canon hdv files of all kinds ( 60i, 24pf, whatever ) with Vegas alone.

So far no hickups at all.

mdopp wrote on 12/20/2007, 4:30 AM

I am just in the process of editing a movie of our vacation in southwest US (arizona, new mexico etc.).
I've been shooting 13 tapes with my Sony FX1 camera - all in all several thousand clips, stored in m2t format.
The project is now over 90 minutes long and contains a dozen tracks and many, many clips and effects (including photos, time-stretches, sound effects etc).
For me, Vegas 8 has proven to be very stable. I can work for hours on the project and never ever have to reboot. Actually I've never had one single crash in the last couple of weeks that I've now been working on the project!
Therefore, I really assume it's either your PC or (probably more likely) Vegas has a specific problem with the way your camera writes m2t files.
BTW, I have captured the clips using HDCapture - not within Vegas.

Rendering your m2ts to CINEFORM intermediate codec might be a useful exercise.
Good luck.
Martin

riredale wrote on 12/20/2007, 10:00 AM

Vegas is rock-solid here, too. Since I doubt Vegas is the cause of the crashes, I suspect something else is interacting with Vegas. BTW I'm using HDVSplit to capture m2t clips. You might want to try that free utility to see if there's any difference.

jbd wrote on 12/21/2007, 8:21 AM

Anyone using dual processor, 2gb Ram and successfully rendering m2t? Would you think this should be efficient? I can edit and do everything great until it's time to render. Rendering locks up.
Vegas 7 and HDV worked fine.
Already tried numerous d. ram settings and virtual memory settings suggested on this forum.

rmack350 wrote on 12/21/2007, 9:30 AM

You know, saying "Vegas is solid but, oh by the way, I don't capture clips in Vegas" falls a little short.

What happens when you capture HDV in Vegas? What made you decide not to do that?

Rob Mack