Pro 8 c crashing, first time ever. at DVinfo.net
DV Info Net

Go Back   DV Info Net > Windows / PC Post Production Solutions > What Happens in Vegas...
Register FAQ Today's Posts Buyer's Guides

What Happens in Vegas...
...stays in Vegas! This PC-based editing app is a safe bet with these tips.

Reply
 
Thread Tools Search this Thread
Old November 23rd, 2009, 11:09 AM   #1
Trustee
 
Join Date: Nov 2007
Location: Bristol UK
Posts: 1,273
Pro 8 c crashing, first time ever.

I'm trying to import some footage into vegas pro 8 c but it keeps crashing.
It only does it from my Sony hard drive camera, which records in mpeg-2 sd, only after i've loaded quite a few clips onto the timeline ,about 50 clips.
This has never happened before.
I can use my EX1 files fine, i can also use my Canon avchd files fine.
The little sony camera is about 4 years old and i've edited loads of stuff from it before.
It's just my little play about camera, this time i took it on holiday to record some stuff.
I tried to burn a disc from the footage using nero, even that footage can't be seen by my pc or vegas or even my dvd player.

the message i get when the pc crashes is this

Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2303B990
In Module 'mcmpgvdec.dll' at Address 0x23000000 + 0x3B990
Thread: VideoCache ID=0x1550 Stack=0x867F000-0x8680000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010216
EBX=00000000 SS=0023 ESP=0867f760 EBP=0867f778
ECX=0867f738 DS=0023 ESI=00000010 FS=003b
EDX=77879a94 ES=0023 EDI=00003f3c 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:
0867F760: 0867F700 08580000 + FF700
0867F764: 5258FBB0 52440000 + 14FBB0
0867F768: 0867F77C 08580000 + FF77C
0867F76C: 004CA400 00400000 + CA400 (vegas80.exe)
0867F770: 004CA400 00400000 + CA400 (vegas80.exe)
0867F774: 00002D00
0867F778: 0867F808 08580000 + FF808
0867F77C: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
0867F780: 004CA400 00400000 + CA400 (vegas80.exe)
0867F784: 00000010
0867F788: 5277A5C8 52440000 + 33A5C8
0867F78C: 5276AF98 52440000 + 32AF98
0867F790: A6F9698E
0867F794: 2ADDAF10 2ADA0000 + 3AF10
0867F798: 0867F85C 08580000 + FF85C
0867F79C: 00000001
> 0867F7AC: 004CA400 00400000 + CA400 (vegas80.exe)
0867F7B0: 5277A6D8 52440000 + 33A6D8
> 0867F7B4: 231C7370 23000000 + 1C7370 (mcmpgvdec.dll)
0867F7B8: 0867F7CC 08580000 + FF7CC
0867F7BC: 5276B038 52440000 + 32B038
> 0867F7DC: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 0867F7E0: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0867F7E4: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 0867F7EC: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 0867F80C: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 0867F83C: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0867F874: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0867F878: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 0867F880: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 0867F88C: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 0867F8BC: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
> 0867F8DC: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
> 0867F8F0: 33BCE077 33BB0000 + 1E077 (mcplug.dll)
> 0867F90C: 23026179 23000000 + 26179 (mcmpgvdec.dll)
> 0867F92C: 33BCDF36 33BB0000 + 1DF36 (mcplug.dll)
> 0867F99C: 33BCECE2 33BB0000 + 1ECE2 (mcplug.dll)
> 0867F9C4: 33BCF21B 33BB0000 + 1F21B (mcplug.dll)
> 0867FA00: 006B583B 00400000 + 2B583B (vegas80.exe)
0867FA04: 34729D28 33DE0000 + 949D28
0867FA08: 000000AC
0867FA0C: 00000000
0867FA10: 0867FA40 08580000 + FFA40
> 0867FA44: 77369F78 77320000 + 49F78 (kernel32.dll)
> 0867FA74: 0191B664 01860000 + BB664 (vegas80k.dll)
- - -
0867FFF0: 00000000
0867FFF4: 0059B990 00400000 + 19B990 (vegas80.exe)
0867FFF8: 00AE9C84 00400000 + 6E9C84 (vegas80.exe)
0867FFFC: 00000000

Can anyone explain ?
Paul.
__________________
Round 2
GH5,FZ2000
Paul Kellett is offline   Reply With Quote
Old November 24th, 2009, 02:11 PM   #2
Inner Circle
 
Join Date: Jan 2006
Posts: 2,290
I had problems like this with some old mpeg2 footage I was capturing from tape.
It was killing my Vegas 9c.
I eventually used Vegas 6 to capture and convert to cineform. It was stable but not all the data was retrievable. Btw, Vegas 5 is considered by some as THE most stable version. As you know, once you've got the footage stabilized with CF, it should easily import to V8.
Brian Luce is offline   Reply With Quote
Old November 24th, 2009, 02:50 PM   #3
Trustee
 
Join Date: Nov 2007
Location: Bristol UK
Posts: 1,273
I've found a workaround.
I imported 10 clips at a time and rendered them out as 1 mpeg-2 clip, then did another 10 and so on, so now i have about 6 new files and they work fine.
I've never had this issue before, do you think some footage was corrupted ?
Could it be something to do with a hard drive camera going through an airport scanner ?

Paul.
__________________
Round 2
GH5,FZ2000
Paul Kellett is offline   Reply With Quote
Old November 24th, 2009, 04:23 PM   #4
Inner Circle
 
Join Date: Jan 2006
Posts: 2,290
Who or what to blame

My first instinct is always blame Dell. Even on Mac problems, it must something to do with Dell. My next instinct is to blame my other nemesis, Windows Vista. Were I a logical person though, I'd probably agree with your suspicions: corrupted footage.
Brian Luce is offline   Reply
Reply

DV Info Net refers all where-to-buy and where-to-rent questions exclusively to these trusted full line dealers and rental houses...

B&H Photo Video
(866) 521-7381
New York, NY USA

Scan Computers Int. Ltd.
+44 0871-472-4747
Bolton, Lancashire UK


DV Info Net also encourages you to support local businesses and buy from an authorized dealer in your neighborhood.
  You are here: DV Info Net > Windows / PC Post Production Solutions > What Happens in Vegas...


 



All times are GMT -6. The time now is 01:24 AM.


DV Info Net -- Real Names, Real People, Real Info!
1998-2024 The Digital Video Information Network