Freezes, hangs & crashes

ShawnLaraSteele wrote on 6/22/2008, 10:44 AM
Vegas 8.0 crashes quite often for me. Sometimes it seems to get confused when doing something in the background and it just hands, then I have to use taskmgr to kill it.

I've been pretty paranoid about saving very often and I rename the project as I go in case I get a corrupted version that won't load (never had that problem, but all the crashes make me nervous).

I'd love to get some of the crash reports back to sony, but they're error reporting seems odd since it catches its exceptions and then just ignores them.

Comments

Darren Powell wrote on 6/22/2008, 5:45 PM
Ground Control to Sony ...

Your software doesn't work.

I repeat ...

Your software doesn't work.

Where's 8.0c?

Ground Control to Sony?

Are you there ... over?

Has a space alien eaten your brain?

I repeat.

Your software doesn't work.

Darren Powell
Sydney Australia

Oops ... just tried to open a little 10 minute project with m2t's.

-----------------------------------------------------------------

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x258ED79C IP:0xD12F221
In Module 'mcmpgdmux.dll' at Address 0xD120000 + 0xF221
Thread: ProgMan ID=0x878 Stack=0x306F000-0x3070000
Registers:
EAX=00000000 CS=001b EIP=0d12f221 EFLGS=00010246
EBX=0000003d SS=0023 ESP=0306f130 EBP=0306f16c
ECX=78134c58 DS=0023 ESI=257f8f48 FS=003b
EDX=016a0608 ES=0023 EDI=258d4f48 GS=0000
Bytes at CS:EIP:
0D12F221: 8B 87 54 88 01 00 50 56 ..T...PV
0D12F229: E8 12 F7 FF FF 83 C4 08 ........
Stack Dump:
0306F130: 25809058 24340000 + 14C9058
0306F134: 257F8F48 24340000 + 14B8F48
0306F138: 0D12B52E 0D120000 + B52E (mcmpgdmux.dll)
0306F13C: 257F8F48 24340000 + 14B8F48
0306F140: 258D4F48 24340000 + 1594F48
0306F144: 00000000
0306F148: 25782F48 24340000 + 1442F48
0306F14C: 3BFFDD90 3A0C0000 + 1F3DD90
0306F150: 2322453A 23200000 + 2453A (mcmpegin.dll)
0306F154: 257F8F48 24340000 + 14B8F48
0306F158: 257971B8 24340000 + 14571B8
0306F15C: 00000000
0306F160: 00000000
0306F164: 7C838F36 7C800000 + 38F36 (kernel32.dll)
0306F168: 7C838F36 7C800000 + 38F36 (kernel32.dll)
0306F16C: 00000000
> 0306F170: 33BBB3DA 33BB0000 + B3DA (mcplug.dll)
> 0306F188: 33BBB520 33BB0000 + B520 (mcplug.dll)
> 0306F194: 33BB8449 33BB0000 + 8449 (mcplug.dll)
> 0306F1AC: 01163691 01150000 + 13691 (vegas80k.dll)
0306F1B0: 05DC1EF8 05AD0000 + 2F1EF8
0306F1B4: 0306F1E8 02F70000 + FF1E8
0306F1B8: 0000A6B4
0306F1BC: 3A47EF3C 3A0C0000 + 3BEF3C
> 0306F1E0: 01163578 01150000 + 13578 (vegas80k.dll)
0306F1E4: 05DC1EF8 05AD0000 + 2F1EF8
0306F1E8: 3BFFDD90 3A0C0000 + 1F3DD90
0306F1EC: 3A47EEF0 3A0C0000 + 3BEEF0
0306F1F0: 00000000
> 0306F1F4: 007425B2 00400000 + 3425B2 (vegas80.exe)
0306F1F8: 01FC6870 01F30000 + 96870
0306F1FC: 3A47EF3C 3A0C0000 + 3BEF3C
0306F200: 3A47EEF0 3A0C0000 + 3BEEF0
0306F204: 00000000
> 0306F21C: 00744E70 00400000 + 344E70 (vegas80.exe)
0306F220: 0306F234 02F70000 + FF234
0306F224: 00000000
0306F228: 0306F7A8 02F70000 + FF7A8
0306F22C: 00000000
> 0306F294: 7C910945 7C900000 + 10945 (ntdll.dll)
> 0306F298: 7C91094E 7C900000 + 1094E (ntdll.dll)
> 0306F2AC: 7C914190 7C900000 + 14190 (ntdll.dll)
> 0306F2B4: 7C901005 7C900000 + 1005 (ntdll.dll)
> 0306F2C4: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 0306F2C8: 7C910970 7C900000 + 10970 (ntdll.dll)
> 0306F2CC: 7C97E4C0 7C900000 + 7E4C0 (ntdll.dll)
> 0306F2D0: 7C913E6F 7C900000 + 13E6F (ntdll.dll)
> 0306F2D4: 7C913E62 7C900000 + 13E62 (ntdll.dll)
> 0306F308: 006E006C 00400000 + 2E006C (vegas80.exe)
- - -
0306FFF0: 00000000
0306FFF4: 005258F0 00400000 + 1258F0 (vegas80.exe)
0306FFF8: 00ADA678 00400000 + 6DA678 (vegas80.exe)
0306FFFC: 00000000

John_Cline wrote on 6/22/2008, 7:29 PM
"Ground Control to Sony ...

Curious, Vegas Pro v8.0b works perfectly for me (and thousands of others.) Perhaps a more accurate statement would be "Your software doesn't work on my particular machine."

It appears that the crash is in the Main Concept MPEG de-multiplexer. By any chance were these HDV files captured with HDVsplit?
deusx wrote on 6/22/2008, 8:40 PM
I haven't had any version of Vegas crash since the actual Major Tom crashed and that was a long time ago. Probably changed 6-7 machines and 4 Vegas versions ( +a,b,c,d releases of each )

Don't now what else to tell you.
Darren Powell wrote on 6/23/2008, 4:02 PM
Yeh, you're right ... Vegas only experiences major instability when you start loading up the timeline with m2t's ... not everybody does that of course ... when you're trying to make a project over a certain size Vegas simply runs out of memory and crashes in lots of interesting ways... and ... SCS have indicated that this is a 'known problem' ... and ... it's taking forever for the bug fix to be released ...

so ... the software doesn't work as advertised ... and it's taking a long long time to fix ....

Darren Powell
Sydney Australia

winrockpost wrote on 6/23/2008, 4:20 PM
Well deusx you wanna see it crash try this

Add a clip to TimeLine (video WITH audio).
-Right click the Event and choose "Select in Project media list"
-Right click the media and choose "Replace"
-Choose a media WITHOUT audio (video only) to replace the media.
-Now, right click the Event on Timeline and choose "Open in Trimmer" > Vegas Crash and close.

farss wrote on 6/23/2008, 4:26 PM
"Curious, Vegas Pro v8.0b works perfectly for me (and thousands of others.) Perhaps a more accurate statement would be "Your software doesn't work on my particular machine.""

Do you know how many machines this project has been tried on and by how many people?
Curious that SCS have admitted they have a problem.
It shouldn't matter how the data was captured. Code that crashes due to bad input data is bad code. Read any decent text on coding.

Bob.
Xander wrote on 6/23/2008, 5:11 PM
I've only had crashes in 32bit mode. I work with .m2ts captured by HDVsplit and have not had any issues. I use the Sony HD 63 min tapes - not sure if that makes a difference. However, most my projects are sub ten minutes. I am doing a wedding now that will be about an hour long - will see how that goes.
Avanti wrote on 6/24/2008, 8:31 AM
Vegas 8b lockup on HDV render

My first use of V8b and first HDV edit project and my first Vegas render lockup ever since V4.

I'm trying to render a 30 second video intro in V8b, in took 2 hours to get 39% complete, then hung there for another 2 hours doing no progress. I had to shut it down with Task manager. This is the error report from Task Manager:
Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: vegas80.exe
Application Version: 8.0.0.217
Application Timestamp: 47852d9a
Hang Signature: 79d5
Hang Type: 6144
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Hang Signature 1: 164e5eec46a6b56cda74da5e6d24afb3
Additional Hang Signature 2: 1b1d
Additional Hang Signature 3: c5d056a9e25dcc452039720e32fec6b5
Additional Hang Signature 4: 79d5
Additional Hang Signature 5: 164e5eec46a6b56cda74da5e6d24afb3
Additional Hang Signature 6: 1b1d
Additional Hang Signature 7: c5d056a9e25dcc452039720e32fec6b5

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409



My system setup is:
Vegas 8b, in 8 bit mode
Vista 32 bit
4 gig memory
Quad core Q9300
NO virus protection
NO email or web browsing
New computer
Up to date BIOS, software, and drivers
Very few other programs installed
Fresh and only install of Vegas 8b trial version
No screen savers, background programs, no hibernate, or energy saving options.
No M2t clips on the timeline, just QT HD Jumpbacks, masks, TGA sequence, alpha AVI's.
Total of 23 video tracks, and 2 audio tracks.

Any help would be appreciated.


bruceo wrote on 6/24/2008, 3:03 PM
"Curious, Vegas Pro v8.0b works perfectly for me (and thousands of others.) Perhaps a more accurate statement would be "Your software doesn't work on my particular machine."

It appears that the crash is in the Main Concept MPEG de-multiplexer. By any chance were these HDV files captured with HDVsplit?"

Duesx and J C

Do you work with 6-10 hours of source m2t footage across 500-1000 clips or even 5-10 source clips for that matter. If so you would have problems as we have had on at least 10 different configurations and installs as well as everyone else i personally know who used vegas with this type of source.
Editguy42 wrote on 6/24/2008, 4:40 PM
Winrock,
I tried your experiment several times and never had a crash.. I am using just SD AVI files. Are you meanng try this with HD files.
John_Cline wrote on 6/24/2008, 4:48 PM
"Do you work with 6-10 hours of source m2t footage across 500-1000 clips or even 5-10 source clips for that matter."

My average project for the last couple of years has involved around 12-20 hours of source .m2t files with around 50-100 clips. I haven't had any problems, which is not to say that I won't in the future.
winrockpost wrote on 6/24/2008, 5:06 PM
yes editguy hdv files, I should have specified , this is repeated here on four various machines,, It was asked by another forum member a while back to repeat his/her results
farss wrote on 6/24/2008, 5:49 PM
And all this in V8.0b?
What is the source of those m2t files, tape, HDD?
How were they captured, cheap camera or good VCR?

Clearly a couple of years ago you wouldn't have been using V8.

Bob.
John_Cline wrote on 6/24/2008, 6:04 PM
Bob,

I don't know if you are asking me specifically, but the majority of the source files are captured live via Firewire from some V1u HDV camcorders using the Vegas HDV capture utility. The rest of the clips are usually B-roll and shot and captured from tape using the V1u camcorders, again with the Vegas capture utility. Occasionally, I'll use HDVsplit if the Vegas machines are busy when I need to capture the B-roll stuff. All in Vegas 8.0b, except as you note, I would have been using Vegas v7 previously. I did have some problems with the first release of Vegas Pro v8.0, but 8.0a took care of them.

John
deusx wrote on 6/24/2008, 7:33 PM
>>>"Do you work with 6-10 hours of source m2t footage across 500-1000 clips or even 5-10 source clips for that matter."<<<

As I mentioned in that other thread, I could have 30-50 clips on a timeline without problems, but even that, to me, is not a good workflow.

Isn't it easier to break things down into a few or many vegas files. You can't work on all of it at once, just like you can't shoot in 2 or 200 different places at the same time. Timeline looks like a mess, what's the point? There is nothing to be gained by dumping all footage into a single vegas file and onto a single timeline. There is everything to be gained by keeping it simple.

I'm sure there is a way to crash Vegas, I just haven't run into it.
I can crash XSI and Fusion ( $5000 and best support on the planet )
every time with certain things. Those are called bugs and you live with them.
farss wrote on 6/25/2008, 6:01 AM
Well I just had my first crash in the latest V8. Same project that had rendered OK on my Core Duo crashed on my new Quad. Wierdess thing is it crashed after it had finished encoding and after I had closed it.
Didn't have any problems with playback on the T/L, encoded very fast with all 4 cores at over 90%, no complaints there and the encoded file is fine. Wierd.
It's a very simple project, two camera shoot, only around 5 clips, double headed audio at 24bit, Wave Hammer compressor on the buss master. Other thing I'm not happy about is Wave Hammer will still cause the audio to cut out during preview, dang, not as easily as on the Core Duo I must admit. That FX must use a lot of CPU.

Bob.
JJKizak wrote on 6/25/2008, 10:07 AM
When 8.0b first came out I tried it (32 bit) on my Vista 64 machine on short projects (HDV & SD) and it worked ok. I did not try to render the entire project however. Just some short pre-renders. 8 gig ram, Q6600, Eva 8800.
JJK
farss wrote on 6/25/2008, 6:39 PM
John,
sorry for being vague, yes I was asking you. Just that I recalled you saying previously you'd stuck with V7.0.

So far on this new quaddie on it's first project I'm having all the horrors. I just found one point on the T/L where Vegas decodes the m2t as a black frame and yet the thumbnail shows it perfectly. It'll be interesting to see what the rendered output contains. Fingers crossed that it doesn't crash in the process.

I recall Peter Wright had this exact black frame problem quite some time ago. I downloaded his very short clip as did others and we could all repo the problem. Peter was sending the project and clip off to SCS. Wonder what ever happened to that trouble ticket.

Bob.
bruceo wrote on 6/25/2008, 7:44 PM
"Isn't it easier to break things down into a few or many vegas files. You can't work on all of it at once, just like you can't shoot in 2 or 200 different places at the same time. Timeline looks like a mess, what's the point? There is nothing to be gained by dumping all footage into a single vegas file and onto a single timeline. There is everything to be gained by keeping it simple."

Are you saying nest smaller .veg files to your master? That opens a bigger can of worms. The power with vegas is the fact that you can throw all of your mud on the timeline and locate what you want very fast visually.

I still have some bad bugs, with vegas capture utility capturing whole tapes, but I can work around them and with smart render it doesn't really cause terrible wastes of time dealing with the bugs. The main issue now is Vegas is UNUSABLE for the same project but using m2ts from the Sony CF unit The mainconcept decoder and the videobuffer crash so ungracefully that it renders projects totally useless wasting weeks of man hours. Similar crashes occured, albeit less frequently with V7 and m2ts, but right now Vegas and Sony CF m2ts on long form projects are 100% useless on 9 projects so far.

Vegas 8c, where are you???
PaulJG wrote on 7/1/2008, 5:08 PM
I have the same problem. I am editing a 45 min Horror flick. All my scenes work fine that are under 4 mins. If it is longer then that is crashes when rendering. Also, when opening the file, I have to quickly zoom in on the time line or it will crash.

So far I think this has cost me at least 15 hours extra work dealing with all the crashes. Unfortunately, I think it will cost me many more hours.

Besides this "major problem", I love Vegas. Hopefully they will get this fixed with version 8c. Waiting for version 9 is out of the question.


4 gigs of ram, 2.5 dual core processor, 550 Meg Video NVidia card. A gig hard-drive, etc.

**********************************************************

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2303B990
In Module 'mcmpgvdec.dll' at Address 0x23000000 + 0x3B990
Thread: VideoCache ID=0x988 Stack=0x3A8E000-0x3A90000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010212
EBX=00000000 SS=0023 ESP=03a8eff4 EBP=03a8f00c
ECX=03a8efd0 DS=0023 ESI=00000010 FS=003b
EDX=7c90e4f4 ES=0023 EDI=00002428 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:
03A8EFF4: 03A8EF94 03990000 + FEF94
03A8EFF8: 00000014
03A8EFFC: 03A8EF58 03990000 + FEF58
03A8F000: 01204800 01150000 + B4800 (vegas80k.dll)
03A8F004: 01204800 01150000 + B4800 (vegas80k.dll)
03A8F008: 00005A00
03A8F00C: 03A8F09C 03990000 + FF09C
03A8F010: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
03A8F014: 01204800 01150000 + B4800 (vegas80k.dll)
03A8F018: 00000010
03A8F01C: 02E00D58 02DE0000 + 20D58
03A8F020: 01A9AD08 01A90000 + AD08
03A8F024: 77C2C2E3 77C10000 + 1C2E3 (msvcrt.dll)
03A8F028: 40EFAED0 405D0000 + 92AED0
03A8F02C: 03A8F0F0 03990000 + FF0F0
03A8F030: 00000001
> 03A8F040: 01204800 01150000 + B4800 (vegas80k.dll)
03A8F044: 40EFAF80 405D0000 + 92AF80
> 03A8F048: 231C7370 23000000 + 1C7370 (mcmpgvdec.dll)
03A8F04C: 03A8F060 03990000 + FF060
03A8F050: 15C2F200 15830000 + 3FF200
> 03A8F070: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 03A8F074: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 03A8F078: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 03A8F080: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 03A8F0A0: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 03A8F0B8: 0F0D04F1 0F0C0000 + 104F1 (mcmpgdmux.dll)
03A8F0BC: 1FD79048 1FB90000 + 1E9048
03A8F0C0: 1FDA4048 1FB90000 + 214048
03A8F0C4: 03A8F154 03990000 + FF154
03A8F0C8: 1FD160C8 1FB90000 + 1860C8
> 03A8F0D0: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 03A8F0FC: 7C80189C 7C800000 + 189C (kernel32.dll)
> 03A8F100: 0F0D1CFE 0F0C0000 + 11CFE (mcmpgdmux.dll)
- - -
03A8FFF0: 00000000
03A8FFF4: 005995C0 00400000 + 1995C0 (vegas80.exe)
03A8FFF8: 00ADC81C 00400000 + 6DC81C (vegas80.exe)
03A8FFFC: 00000000