Vegas Bugs - A neverending story [Archive]

View Full Version : Vegas Bugs - A neverending story

Axel Scheffler

November 9th, 2007, 07:38 PM

Hi Guys,

I think I will be number 100.000.000 on the "bugs in Pro 8" list but I have tried already everything to figure out what is going wrong with Pro8 and I'm getting sad with spending $300 for the upgrade which is not working.
At first the project:
HDV 1080 60i material. The material is OK, to exclude the material as a bug I have tried material from a second source but the effect was the same!

The machine:
Duo E6850 3GHz, 2GB Ram, NVidia 8800GTS 640MB, Asus motherboard, Windows XP Pro, checked, updated and everthing (inclusive Vegas 7.0 which is running fine) is working and running fine.

The Problem:

When I put HDV clips in the timeline I can see how the PFUsage in the Task Manager is raising, at around 28 to 32 clip I reach 1.72GB and I get this:

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: VideoRender ID=0xCFC Stack=0xAA7E000-0xAA80000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010206
EBX=00000000 SS=0023 ESP=0aa7ea5c EBP=0aa7ea74
ECX=0aa7ea38 DS=0023 ESI=00000010 FS=003b
EDX=7c90eb94 ES=0023 EDI=00002c18 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:
0AA7EA5C: 0AA7E9FC 0A980000 + FE9FC
0AA7EA60: 00000014
0AA7EA64: 0AA7E9C0 0A980000 + FE9C0
0AA7EA68: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EA6C: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EA70: 00005A00
0AA7EA74: 0AA7EB04 0A980000 + FEB04
0AA7EA78: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
0AA7EA7C: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EA80: 00000010
0AA7EA84: 0288E418 02790000 + FE418
0AA7EA88: 0288E3F8 02790000 + FE3F8
0AA7EA8C: 77C2C2E3 77C10000 + 1C2E3 (msvcrt.dll)
0AA7EA90: 0287AC80 02790000 + EAC80
0AA7EA94: 0AA7EB58 0A980000 + FEB58
0AA7EA98: 00000001
> 0AA7EAA8: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EAAC: 2182FB70 212F0000 + 53FB70
> 0AA7EAB0: 231C7370 23000000 + 1C7370 (mcmpgvdec.dll)
0AA7EAB4: 0AA7EAC8 0A980000 + FEAC8
0AA7EAB8: 2182FB80 212F0000 + 53FB80
> 0AA7EAD8: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 0AA7EADC: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0AA7EAE0: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 0AA7EAE8: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 0AA7EB08: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 0AA7EB28: 0C380B4F 0C370000 + 10B4F (mcmpgdmux.dll)
0AA7EB2C: 616E7E48 5E060000 + 3687E48
0AA7EB30: 61733E48 5E060000 + 36D3E48
0AA7EB34: 0AA7EBBC 0A980000 + FEBBC
> 0AA7EB38: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0AA7EB70: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0AA7EB74: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 0AA7EB7C: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 0AA7EB88: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 0AA7EB98: 232135CA 23200000 + 135CA (mcmpegin.dll)
> 0AA7EBB8: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
> 0AA7EBD8: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
> 0AA7EC08: 23026179 23000000 + 26179 (mcmpgvdec.dll)
> 0AA7EC28: 23216DFD 23200000 + 16DFD (mcmpegin.dll)
> 0AA7EC68: 23218527 23200000 + 18527 (mcmpegin.dll)
> 0AA7EC98: 2323A5C2 23200000 + 3A5C2 (mcmpegin.dll)
> 0AA7ECAC: 7C931C41 7C900000 + 31C41 (ntdll.dll)
> 0AA7ECB0: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 0AA7ECF4: 01050104 00400000 + C50104 (vegas80.exe)
- - -
0AA7FFF0: 00000000
0AA7FFF4: 0059E390 00400000 + 19E390 (vegas80.exe)
0AA7FFF8: 0571BDB8 05570000 + 1ABDB8
0AA7FFFC: 00000000

After playing around with Dynamic RAM, Render Jobs, page file size in WinXP, Process Focus in XP and so on I´m getting beside the above message sometimes:

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: VideoRender ID=0xFAC Stack=0xAA7E000-0xAA80000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010206
EBX=00000000 SS=0023 ESP=0aa7ea5c EBP=0aa7ea74
ECX=0aa7ea38 DS=0023 ESI=00000010 FS=003b
EDX=7c90eb94 ES=0023 EDI=00002a14 GS=0000
Bytes at CS:EIP:
2303B990: 89 3B EB 95 8D B6 00 00 .;......
2303B998: 00 00 8D BF 00 00 00 00 ........

and this:

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=0xA8C Stack=0x3DDE000-0x3DE0000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010212
EBX=00000000 SS=0023 ESP=03ddeff4 EBP=03ddf00c
ECX=03ddefd0 DS=0023 ESI=00000010 FS=003b
EDX=7c90eb94 ES=0023 EDI=000023c8 GS=0000
Bytes at CS:EIP:
2303B990: 89 3B EB 95 8D B6 00 00 .;......
2303B998: 00 00 8D BF 00 00 00 00 ........

or this:

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) WRITE:0x1 IP:0x50002CA
Thread: GUI ID=0x4B0 Stack=0x12A000-0x130000
Registers:
EAX=00000001 CS=001b EIP=050002ca EFLGS=00010206
EBX=0012a104 SS=0023 ESP=0012a0dc EBP=0012a118
ECX=050002ca DS=0023 ESI=7d57aae8 FS=003b
EDX=474e5543 ES=0023 EDI=3f072480 GS=0000
Bytes at CS:EIP:
050002CA: 00 00 00 00 00 00 00 00 ........
050002D2: 00 00 00 00 00 00 00 00 ........

The most messages are the render stuff.

The 1.72GB are the mystical part, Vegas 7.0 never reached this, even with an hour HDV, in Pro8 1.72Gb are reached with in 2.5 minutes HDV material.

With SD material I can fit 4hours and up in less than 1.0GB PF Usage.

To exclude the machine I have tried it on three different computer:

HP slimeline PC WinXpMediaCenter
EMachines with Windows Vista :-(
Emachines with Windows XP Home

Everytime I´m getting the same messages with two different HDV materials. A friend tried already my projects on his computer with one of the HDV sources and it was working. The only real difference (since the hardware does not matter according my own experiments!!!) he is running on a German Windows XP! OK, they have 230Volts in Germany :-)

Who can help before I send the software back and try to get my money back?

Thanks

Axel, San Jose, CA

Douglas Spotted Eagle

November 10th, 2007, 08:54 AM

From where do the HDV files originate?

Axel Scheffler

November 10th, 2007, 11:13 AM

I have done tests with my own files that are captured by HDVSplitt and I got one file where I have no idea where it comes from.
If you ask in regard to dropped frames or things like that, they are fine. HDVSplitt would stop at dropped frames. Also when I check the properties of the files the amount of dropped frames is 0.

Axel

Mark Stavar

November 11th, 2007, 07:00 AM

There was another similar thread recently, people having crashes such as this.

The common theme there seemed to be the video card - Nvidia 8800 - which I notice you also have.

Perhaps there is a driver problem here.

Hope you find a solution.

Ciao,

marks

Lars Siden

November 11th, 2007, 12:14 PM

For me, FFDshow and HajiMediaSplit gets my pooter to give up whe I use NLE:es.

I can play files just fine in the OS - but not edit them in NLE. FFDShow can make program exceptions - so in theory I could tell it not to touch premiere / vegas....

// Lz

Joel Chappell

November 11th, 2007, 12:32 PM

Axel Scheffler

November 11th, 2007, 05:54 PM

Hi Guys,

I got a solution for my problems. Since I have captured my videos via HDVSplitt Sony Vegas screwed up with these files. The files are still fine but Vegas can not handle them. I needed to recapture all files and after that it was working.
Since this seems to be a Vegas glitch I would recommend to everybody to check with which application the files are captured. It looks like that there are probably several different applications where Vegas is screwing up. Cross check every file in regard to the capture source and think than it will work. My problems are solved by that.

Thanks

Axel

Ian Stark

November 12th, 2007, 03:57 AM

There was another similar thread recently, people having crashes such as this.

The common theme there seemed to be the video card - Nvidia 8800 - which I notice you also have.

Hi Mark,

Can you point us to the thread please. I am an Nvidia 8800 GTX user and I would be interested to see what others are saying about their problems. I searched the forum for '8800' but couldn't find any threads with a common 8800 theme as you described. Cheers.

For what it's worth, I have only experienced problems/crashes when using the new Titler and I do suspect these are related to the graphics card. I've turned off all the 'extra' bits that were installed along with the original driver(something called Movie Mode, as I recall, as well as other bits of junk) and have upgraded to the latest drivers. Still having those glitches in the Titler, though (or rather I would be having those glitches if I actually used the Titler, which I don't!).

Matthew Chaboud

November 13th, 2007, 11:03 AM

So, Alex, you're largely right. The issue here is that Vegas' high-performance low-memory mpeg mechanism doesn't understand every file out there. If it doesn't understand a file, it hands it off to a more comprehensive reader that has a larger memory footprint and lower performance.

Unfortuantely, most (if not all) of your files are getting handed off.

This can happen if you capture over clip boundaries from some source types (different cameras do different things, as do different capture applications).

Another fix, instead of re-capturing, would be to re-render all of the clips in question in a batch process in Vegas. It's not ideal, but the number of things that you can find in an "MPEG-2" file is pretty dizzying.

-Matt

Axel Scheffler

November 13th, 2007, 02:24 PM

Matthew Chaboud

November 14th, 2007, 10:30 AM

Axel,
If you're wondering if you'll get the same quality after doing an intermediate render, you won't.

If you're wondering if the readers produce identical output regardless of stream oddities in the files, they *should*. There may be discrepancies, but the representation of compressed content is supposed to be identical.