Vegas Pro 8.0b Crashes Continuously

AWinn wrote on 6/9/2008, 6:11 PM

The project I am currently working on has MPEG files from a sony Hard Drive Camera, .AVI files from a Cannon as well as a couple of JPEG's (which I have reduced the size to about 400, and WAV files from a couple of songs ripped from a CD (with permission). In total, probably near 80 thumbnails (though I have swithed to list view). With that said, the application is crashing/showing error messages after adding two or three files into the timeline. Sometimes, I can not even get that far. I am currently using Visa OS and have a Dual Core Proc with 2 Gigs of ram. I have tried to shut down everything but Vegas (including McAfee), but nothing is working. The program seems extremely unstable, but I have never had problems with Vegas before (although this is the first project using Vegas Pro 8.0b. Any suggestions?

Back to post

Comments

Paul Mead wrote on 6/12/2008, 5:54 PM

Wow, talk about a cookbook blow-off response from support. I hate that crap. "Just reinstall the world and your problem should go away." Sometimes it works, but not near enough to put so many people thru so much pain.

Considering that the Main Concept DLLs seem to be a common thread in all of these complaints, has anyone actually tried bugging Main Concept to see if they can offer any suggestions? I took a quick look at their website and it looks like you can start by sending a nicely worded note to support@mainconcept.com . Maybe you could tell them that you are suggesting to Sony that they quit using Main Concept decoders or something. I mean, at this point desperate actions are warranted. Right?

Btw, I did a google of "access violation mcplug.dll" and found a chorus of people complaining about the same thing in various websites (with no solutions). So much for Vegas' wonderful reputation for stability. Whether or not it is Sony's problem, somebody needs to get to the bottom of it.

Darren Powell wrote on 6/13/2008, 2:10 AM

Yeh, I agree Paul_Mead ... it definitely looks like an issue with the MainConcept plug ...

My mate Bob (farss) came down the other day and checked out my project ... all seems fine except it won't render and crashes all the time ... real PITA stuff ... Bob put me onto Veggie Toolkit ... I've been experimenting with rendering 32bit projects (just little 30 sec commercials that wouldn't render in 32 bit before) and they actually render the whole .veg file in Veggie Toolkit when using one of the YUV templates ... try the same thing with an m2t template by MainConcept and it just disappears off the screen ...

Again, I don't really care who is to blame ... I'm just one of many trying to use the product ... if Sony are using MC for their MPEG2 stuff ... then it should work ... no matter what.

So ... as I've said a million times before ... fix it Sony, talk to MC, whatever you have to do ... write some lines of code that fix the problem and send me the update ... and kindly pay my 'time wasted' invoice within seven days or I'll send the BOYS around !

(OK, so they're only boy scouts ... but you never know they might be able to do something, right? :-)

Darren Powell
Sydney Australia

fusionspliced wrote on 7/15/2008, 7:23 PM

Apparently I'm not alone. Been running on version 6 for the last 3 years and decided to upgrade to 8 and it hasn't crashed yet but doesn't respond for 30 seconds at a time, very annoying. It does that every time I switch between different programs and back to Vegas. Can't remember if I put version 8 on this computer when I had XP on it, but I'm thinking I'm going to throw a new drive in tomorrow and load it up with XP and see if there's a difference.
I have a 2.4 core 2 duo with 3 gigs of ram and dual monitors. This is my first big project with ver 8, 3 camera views with 2 gig clips from Sony hard drive cameras. If I have to shut down the second monitor then it pretty much cuts down my productivity 75%.

rs170a wrote on 7/15/2008, 7:58 PM

...doesn't respond for 30 seconds at a time, very annoying. It does that every time I switch between different programs and back to Vegas.

Options > Prefs > General.
Look for the "Close media files when not the active application" box.
If it's currently selected, de-select it.
If it's not selected, select it.

Mike

fusionspliced wrote on 7/16/2008, 5:05 PM

Excellent rs170a, that was it. I had to deselect it, thanks!

Simonm wrote on 7/17/2008, 7:50 AM

Well I know it's over a month since, but I'm still getting crashes after rendering. I'm using no plugins at all. At least most of the time it seems to render OK first!

Here's the data dump:
----------------------->8 ----------------

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC000008C (array bounds exceeded) IP:0x90E2CE8
Thread: GUI ID=0xE60 Stack=0x12D000-0x140000
Registers:
EAX=7ffde000 CS=001b EIP=090e2ce8 EFLGS=00210202
EBX=00000000 SS=0023 ESP=0012da54 EBP=0012da7c
ECX=00000000 DS=0023 ESI=090e2ce8 FS=003b
EDX=0012daac ES=0023 EDI=0012dab8 GS=0000
Bytes at CS:EIP:
090E2CE8: 62 00 4E 77 D8 85 34 05 b.Nw..4.
090E2CF0: 00 00 00 00 F9 00 00 00 ........
Stack Dump:
0012DA54: 7E418734 7E410000 + 8734 (USER32.dll)
0012DA58: 002A0122 00290000 + 10122
0012DA5C: 00000219
0012DA60: 00000007
0012DA64: 00000000
0012DA68: 090E2CE8 08F90000 + 152CE8
0012DA6C: DCBAABCD
0012DA70: 00000000
0012DA74: 0012DAB8 00040000 + EDAB8
0012DA78: 090E2CE8 08F90000 + 152CE8
0012DA7C: 0012DAE4 00040000 + EDAE4
0012DA80: 7E418816 7E410000 + 8816 (USER32.dll)
0012DA84: 090E2CE8 08F90000 + 152CE8
0012DA88: 002A0122 00290000 + 10122
0012DA8C: 00000219
0012DA90: 00000007
> 0012DABC: 7E41882A 7E410000 + 882A (USER32.dll)
> 0012DAD8: 7E440457 7E410000 + 30457 (USER32.dll)
> 0012DADC: 7E418830 7E410000 + 8830 (USER32.dll)
> 0012DAE8: 7E4189CD 7E410000 + 89CD (USER32.dll)
> 0012DB38: 7E440457 7E410000 + 30457 (USER32.dll)
> 0012DB3C: 7E4189F0 7E410000 + 89F0 (USER32.dll)
> 0012DB48: 7E418A10 7E410000 + 8A10 (USER32.dll)
> 0012DB58: 7E42DBBF 7E410000 + 1DBBF (USER32.dll)
> 0012DB90: 7E42593F 7E410000 + 1593F (USER32.dll)
> 0012DBB8: 7E425981 7E410000 + 15981 (USER32.dll)
> 0012DBBC: 00400000 00400000 + 0 (vegas80.exe)
> 0012DBC0: 01445328 01150000 + 2F5328 (vegas80k.dll)
0012DBC4: 001B00D4 00150000 + 600D4
> 0012DBC8: 01213EC0 01150000 + C3EC0 (vegas80k.dll)
0012DBCC: 0012DC6C 00040000 + EDC6C
0012DBD0: 00000001
0012DBD4: 0012DBF4 00040000 + EDBF4
> 0012DBD8: 7E43204D 7E410000 + 2204D (USER32.dll)
> 0012DBDC: 00400000 00400000 + 0 (vegas80.exe)
> 0012DBE0: 01445328 01150000 + 2F5328 (vegas80k.dll)
0012DBE4: 001B00D4 00150000 + 600D4
> 0012DBE8: 01213EC0 01150000 + C3EC0 (vegas80k.dll)
- - -
0013FFF0: 00000000
0013FFF4: 00000000
0013FFF8: 0083F20B 00400000 + 43F20B (vegas80.exe)
0013FFFC: 00000000

----------------------->8 ----------------

Regards,

Simonm.

PDXposed wrote on 7/31/2008, 7:59 PM

Here is a TEMP FIX to the problem.
TEMP FIX FOR *.M2t files in SONY VEGAS 8.0

The problem is if you have more then 30+ clips on the timeline that are *.m2t files Sony will give you an error. I have a temp fix below. Enjoy!

1.Add up to 30 *.m2t clips to timeline.
2.Save project. (Make sure you save as a HDV project)
3.Start new project, refresh so that the project you saved will show up in explorer in Vegas. (Make sure you start a HDV project)
4.DRAG-DONT OPEN the saved project to the timeline. Vegas will auto render a *.veg.sfap0 file, this will save you lots of time redering *.avi clips like Vegas website says to do. You can have AS MANY *.veg.sfap0 files on a timeline as you want unlike the *.m2t files. Please email with concerns or if you cant get it to work.

HOPE THIS HELPS YOU ALL OUT, I know it did me! -Joshua

SONY VEGAS 8.0 PRO EDITOR

blink3times wrote on 7/31/2008, 8:58 PM

"The problem is if you have more then 30+ clips on the timeline that are *.m2t files Sony will give you an error. I have a temp fix below. Enjoy!"

Let me be the first to shoot down your theory. I REGULARLY do M2T work with 250 or more scenes with no crashing issues. The other day I did 400 scenes (with the new HDV reader) and no crashing. But 2 weeks ago i did about 430 scenes with the OLD hdv reader with no crashing. I had LOTS of crashing when I used scene detect on the fly when capturing, but there has been no crashing at all since I started doing scene detections AFTER the capture.

I'm convinced that it has something to do with the scene divisions.

If you capture a 1 hour tape with no scene detection and place it on the time line and divide scenes manually, there is no crashing.

OR

Using HDVsplit and using the scene detect AFTER you capture the entire tape to the HDD, there will be no crashing.