Hey Bob (Farss),

What do you reckon? New recruits to the 'Vegas Pro 8.0b Sux Bigtime' club? (Thanks for dropping in and checking out my project yesterday ... )

Hey AWinn and MichaelduS ... there are a number of us here at the forum hoping and praying that Vegas Pro 8.0c will resolve a range of memory related issues in b ...

Good Luck,

Darren Powell
Sydney Australia


, ....

What can I say that hasn't already been said. It's like watching a train wreck in slow motion. 50% increase in sales, 100% increase in disgruntled users, what a PR disaster. Maybe they can take a lead from our new PM and try a simple public "Sorry".

Was great to meet with Darren yesterday. His movie is looking and sounding world class, can't wait to see it on the big screen.

Bob.

Thanks Bob,

I'll get that 1TB back to you with some test Veg's and see if you can make some render magic happen.

Cheers,

Darren Powell
Sydney Australia

hey darren
thanks for your comment. Its good to know that we're not alone out here. for a moment i was thinking my brand new dell required returning or i needed a trip to the shrink. i forgot i am a shrink!reading your thread i can well appreciate your level of frustration. it sounds like you've found a "fix" with Bob's help. g'd on ya Bob.
so i spose we just sit and twiddle our thumbs while sony fiddles?

I think it's a bit premature to say we found a fix. At best we might find a way around the problem(s).

Bob.

I am hoping along with Darren, Bob etc... etc.. that we will see an improved 8.0c by this weekend. I do recall Sony stating they would release mid June...
I hope to read in the release notes of what is fixed in this version. "Fixed memory fill up, Vegas will no lnger crash by putting too many files on the timeline"

Bob, I am glad you are able to support Darren with his movie. Good luck.

Ted

For you guys/gals who are running two or more monitors and having crashes, you may want to try just plugging one monitor into your CPU, and see if the crashes cease. My new quad Dell with Vista 32 bit will crash and give me the BSOD if I run two monitors, and I don't even have to run a program to crash it. It just takes a notion to crash when it feels the need.

I am praying to all gods that 8.0c V64 or whatever will fix this memory management, mcencoder, videobuffer, bug especially making it more tolerant for M2t clips like are captured. Vegas needs a serious prayer group :-)

Might have solved my crashing issues with Vegas 8. My old system crashed constantly with it, Dell 340/ 2.0Ghz Pentium 4 /1 meg RAM, XP Pro - service pack 2, single monitor.
Bought a new Dell 690, Xeon dual core 2.0, nVidio FX550, XP Pro, 2 gigs RAM. So far (knocking an wood and everything else), no crashes with Vegas 8.0a yet. Haven't tried 8.0b yet on this new computer. The Dell 340 didn't like version 8.0b at all. The Dell 690 has a virgin install of Vegas 8.0a, no other software except Roxio on it. Planning on installing 2 more gigs of RAM this weekend for a total of 4 gigs. Might get brave and try 8.0b also.
Only have a short (12 min) project on the new install so far. All camera footage.

Thank you so much for all the replies. I will definitely try deleting the shared plug-ins folder. However, do to a deadline, I had to try something, so I have downloaded the 30 day trial of the Sony Movie studio, with hopes that I could copy and paste...it worked. Though I am very limited in what I can do with Movie Studio, it has not crashed and I have been able to go forward with the project (with limited capabilities). With that said, I look forward to Pro 8.0c and hope that it takes care of the memory/crashing problem.

Yeah.

Add me to the prayer circle. I've been trying to render out our feature for days now, for a transfer from an Avid or FCP timeline to Digibeta and Beta SP for three upcoming festivals in Philly San Francisco and Los Angeles.

I've broken it up into smaller segments of 10-15 minutes for reassembly at the post house, but I just keep getting freeze-ups/crashes/out of memory errors, etc. You all know the game by now, if you're working on projects of larger sizes.

Please, SCS, please, get this fixed. Soon. I, personally, am running out of time here. We are on deadline for festivals.

Oh Dear God,

We of the official 'Sony Forum Prayer Circle' hereby officially commend our brother Vegas Pro 8 to you ... that you may cleanse him of his foul messages ... that you may wash clean the errors of his ways ... that you may heal him of his hangups ... and restore him fully from his crashes ...

and God Speed to us all!

Amen.


PS. And forgive me for my recent message to Sony Tech Support which included the use of the 'F' word at least a dozen times...


Kindest regards Patrick!


Darren Powell
Sydney Australia

Guys, I am certain this is a GUI issue. I said this right from the very beginning when I got Vegas 8. I stuck with Vegas 8.0a build 179 when version b came out, as I had finally got it running stable, but my issues were also when I had two screen running. I switched back to one once I got past the editing and grading stage of my current project. I can guarantee it will be a simple stack error or something else equally mundane that has caused all these problems. The crashes occur at different points in the screen redraw cycle depending on your particular setup. Hence for some people dropping media onto the time line causes a bunch of redrawn that exceed whatever buffer. For some people (like me) it happens when you switch from different applications, or you go to a menu option.

I will also point out, I got banned from another very popular forum without any warnings because I was complaining about how unreliable Vegas 8 was. Those guys were even telling me that I must have pirated copy, and that there must be something wrong with my computer, even though I had no problems with the large range of other software I was using! And failing that they were just like "oh, so really, you are the oooonnllly person having a problem with this software" like I was being some kind of trouble maker, or even making it up. I was suprised to find the official Sony forum is so much more impartial, and much more critical than that den of fawning merchants! :)

Edit: I will add, these issues would never have happened if there had been a proper Beta cycle, which there obviously was not.

Mmm ... I'm not sure I understand what you're suggesting is the fix for the this Robert W ...

Are you saying just take out our dual monitors and go back to one monitor and everything will work again?

Or change the screen res of a single monitor??

I don't know if that helps me because I've tried Vegas Pro 8 with a single monitor when I first bought it in Oct / Nov last year ... now I have three monitors via a TripleHead2Go from Matrox which is just a single monitor out of the computer which is split into three via the splitter box that comes with the package ...

I think it's memory management as we've discussed many times before ... but then again ... I'll give anything a try if it might make Vegas more stable ...

Cheers,

Darren Powell
Sydney Australia

Hi Robert_W,

Below is another crash from this morning ... does this look like it's caused by what you're talking about?

Let me know if you know what's causing this ... then Sony can fix it!

Cheers,

Darren Powell
Sydney Australia

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

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x33BB3B5B
In Module 'mcplug.dll' at Address 0x33BB0000 + 0x3B5B
Thread: GUI ID=0xB64 Stack=0x13E000-0x140000
Registers:
EAX=00000000 CS=001b EIP=33bb3b5b EFLGS=00010246
EBX=00000000 SS=0023 ESP=0013e340 EBP=00000002
ECX=00000000 DS=0023 ESI=0013e3a8 FS=003b
EDX=00000000 ES=0023 EDI=0013e390 GS=0000
Bytes at CS:EIP:
33BB3B5B: 8B 13 8D 44 24 24 50 6A ...D$Pj
33BB3B63: 40 56 8D 4C 24 24 51 8B @V.L$Q.
Stack Dump:
0013E340: 3C2693B0 3A2C0000 + 1FA93B0
0013E344: 00000000
0013E348: 2DA3F388 2B560000 + 24DF388
0013E34C: 00000000
0013E350: 00000000
0013E354: 00000001
0013E358: 00000000
0013E35C: 00743BD4 00400000 + 343BD4 (vegas80.exe)
0013E360: 2DC12B08 2B560000 + 26B2B08
0013E364: 0013E390 00040000 + FE390
0013E368: 00000000
0013E36C: 00000001
0013E370: 00000000
0013E374: 2DA3F5E8 2B560000 + 24DF5E8
0013E378: 00000000
0013E37C: 2DA3F388 2B560000 + 24DF388
> 0013E438: 00744EBB 00400000 + 344EBB (vegas80.exe)
0013E43C: 2DA3F388 2B560000 + 24DF388
0013E440: 00000000
0013E444: 00000001
0013E448: 00000000
> 0013E4B0: 7C910945 7C900000 + 10945 (ntdll.dll)
> 0013E4B4: 7C91094E 7C900000 + 1094E (ntdll.dll)
> 0013E4C8: 7C914190 7C900000 + 14190 (ntdll.dll)
> 0013E4D0: 7C901005 7C900000 + 1005 (ntdll.dll)
> 0013E4E0: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 0013E4E4: 7C910970 7C900000 + 10970 (ntdll.dll)
> 0013E4E8: 7C97E4C0 7C900000 + 7E4C0 (ntdll.dll)
> 0013E4EC: 7C913E6F 7C900000 + 13E6F (ntdll.dll)
> 0013E4F0: 7C913E62 7C900000 + 13E62 (ntdll.dll)
> 0013E524: 00BC00BA 00400000 + 7C00BA (vegas80.exe)
0013E528: 2DA3F634 2B560000 + 24DF634
0013E52C: 00000000
0013E530: 00000000
0013E534: 2DA3F634 2B560000 + 24DF634
> 0013E55C: 01000000 00400000 + C00000 (vegas80.exe)
0013E560: 0013E61C 00040000 + FE61C
0013E564: 44000000 43D00000 + 300000
0013E568: 00000000
0013E56C: 00000000
> 0013E574: 7C910945 7C900000 + 10945 (ntdll.dll)
> 0013E578: 7C91094E 7C900000 + 1094E (ntdll.dll)
> 0013E58C: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 0013E59C: 7C91402E 7C900000 + 1402E (ntdll.dll)
> 0013E5A8: 7C910970 7C900000 + 10970 (ntdll.dll)
> 0013E5AC: 7C97E4C0 7C900000 + 7E4C0 (ntdll.dll)
> 0013E5B0: 7C9140EF 7C900000 + 140EF (ntdll.dll)
> 0013E5B4: 7C9140BB 7C900000 + 140BB (ntdll.dll)
> 0013E5DC: 7C913E88 7C900000 + 13E88 (ntdll.dll)
> 0013E604: 00BC00BA 00400000 + 7C00BA (vegas80.exe)
0013E608: 2DA3F634 2B560000 + 24DF634
0013E60C: 0013E61C 00040000 + FE61C
0013E610: 00000002
0013E614: 05C959D8 05AD0000 + 1C59D8
> 0013E618: 01000000 00400000 + C00000 (vegas80.exe)
- - -
0013FFF0: 00000000
0013FFF4: 00000000
0013FFF8: 0083F20B 00400000 + 43F20B (vegas80.exe)
0013FFFC: 00000000

Darren-
Below is the error message that I just received when I opened my project. Now, it took me a few times to reproduce this error, because Vegas crashed a few times before getting this error. However, if anyone is able to help with this, please let me know what I can do. Thanks so much.
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: VideoRender ID=0x19CC Stack=0xD89E000-0xD8A0000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010206
EBX=00000000 SS=0023 ESP=0d89ea5c EBP=0d89ea74
ECX=0d89ea34 DS=0023 ESI=00000010 FS=003b
EDX=773c0f34 ES=0023 EDI=0000334c 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:
0D89EA5C: 0D89E9FC 0D7A0000 + FE9FC
0D89EA60: 000001B8
0D89EA64: 2A0B00E6 2A0B0000 + E6
0D89EA68: 003FFC00
0D89EA6C: 003FFC00
0D89EA70: 00002D00
0D89EA74: 0D89EB04 0D7A0000 + FEB04
0D89EA78: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
0D89EA7C: 003FFC00
0D89EA80: 00000010
0D89EA84: 12EEFDE0 12AF0000 + 3FFDE0
0D89EA88: 17F48C60 17E70000 + D8C60
0D89EA8C: 000001E0
0D89EA90: 000002D0
0D89EA94: 00000008
0D89EA98: 17F48C60 17E70000 + D8C60
> 0D89EAD8: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 0D89EADC: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0D89EAE0: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 0D89EAE8: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 0D89EB08: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 0D89EB18: 23028344 23000000 + 28344 (mcmpgvdec.dll)
> 0D89EB38: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0D89EB70: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0D89EB74: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 0D89EB7C: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 0D89EB88: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 0D89EBB8: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
> 0D89EBD8: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
> 0D89EC08: 23026179 23000000 + 26179 (mcmpgvdec.dll)
> 0D89EC28: 23216DFD 23200000 + 16DFD (mcmpegin.dll)
> 0D89EC68: 23218527 23200000 + 18527 (mcmpegin.dll)
> 0D89EC98: 2323A5C2 23200000 + 3A5C2 (mcmpegin.dll)
> 0D89ECCC: 00569604 00400000 + 169604 (vegas80.exe)
0D89ECD0: 00000000
0D89ECD4: 001B7E48 001B0000 + 7E48
0D89ECD8: 00000000
0D89ECDC: 0D89ED0C 0D7A0000 + FED0C
> 0D89ED94: 038E8F84 037D0000 + 118F84 (CFHD.dll)
0D89ED98: 00000000
> 0D89ED9C: 038E8F84 037D0000 + 118F84 (CFHD.dll)
0D89EDA0: 00000000
0D89EDA4: 00000000
0D89EDA8: 00000000
0D89EDAC: 00000000
> 0D89EDD8: 773C1843 77360000 + 61843 (ntdll.dll)
> 0D89EE14: 01AB0013 01850000 + 260013 (vegas80k.dll)
0D89EE18: 00000652
0D89EE1C: 00000000
0D89EE20: 001B79B8 001B0000 + 79B8
0D89EE24: 0AE4C898 0AC30000 + 21C898
> 0D89EE44: 773C86CD 77360000 + 686CD (ntdll.dll)
> 0D89EEBC: 75DD49CE 75DB0000 + 249CE (kernel32.dll)
> 0D89EED0: 773C18C3 77360000 + 618C3 (ntdll.dll)
> 0D89EEE4: 75DD489A 75DB0000 + 2489A (kernel32.dll)
> 0D89EF5C: 00569604 00400000 + 169604 (vegas80.exe)
0D89EF60: 00000000
0D89EF64: 00000000
0D89EF68: 00000027
> 0D89EF6C: 75DD3D39 75DB0000 + 23D39 (kernel32.dll)
> 0D89F37C: 75FA390A 75EF0000 + B390A (RPCRT4.dll)
> 0D89F388: 744F92C4 744D0000 + 292C4 (WINMM.dll)
> 0D89F38C: 75FA3928 75EF0000 + B3928 (RPCRT4.dll)
> 0D89F3D8: 33BB679F 33BB0000 + 679F (mcplug.dll)
> 0D89F3F4: 33BB6D4C 33BB0000 + 6D4C (mcplug.dll)
> 0D89F43C: 75DF9BE2 75DB0000 + 49BE2 (kernel32.dll)
> 0D89F458: 33BB88B6 33BB0000 + 88B6 (mcplug.dll)
> 0D89F494: 006B553B 00400000 + 2B553B (vegas80.exe)
- - -
0D89FFF0: 00000000
0D89FFF4: 0059EE70 00400000 + 19EE70 (vegas80.exe)
0D89FFF8: 0ADE9340 0AC30000 + 1B9340
0D89FFFC: 00000000

Hi AWinn and everyone ...

I think I know what's going on here ... Sony have decided that Vegas isn't going to be an NLE anymore for making videos and stuff ... it's now going to be a 'Stack Dump Generator' to be used in error research ... ?

By the looks of this thread that seems entirely possible ...

Darren Powell
Sydney Australia

I am getting very similar crash messages - I feel a post traumatic response coming on when I see those words "access violation". Here's what Jesse at Sony has suggested I do and if any of you are brave enough follow his instructions and then please confirm with this forum the outcome. Prayers to you all. Here's the "fix":Hi Michael,

Thank you for contacting Sony Creative Software. The mcmpgvdec.dll refers to the MainConcept MPEG coded (plug-in). There have been instances of plug-ins not updating properly when the software is updated to the current build, so I wonder if perhaps your disc has the 8.0a build, and whether uninstalling the program and reinstalling the current 8.0b build all at once would be beneficial.

Please follow these instructions, making sure to pay close attention when working in the registry and when ending processes. Performing these steps will result in all presets and transitions you may have saved being wiped clean, so you will want to back these up beforehand using our Preset Manager program. This is available free of charge from our website at http://www.sonycreativesoftware.com/download/step2.asp?DID=469

First, safely disconnect any any external USB or Firewire devices like hard-drives or dongles.

Please go to Start > Control Panel and open the Add/Remove Programs control panel. (In Windows Vista, click Start and then type "Programs and Features" in the Start Search box. In the Programs list, click Programs and Features).

Remove anything with a name containing Sony ACID, Sony Sound Forge, Sony Vegas, Sony DVD Architect, Sony CD Architect or Sony Media Manager, as well as any other Sony Creative Software programs.

Also, remove the Microsoft SQL Server Desktop Engine, any Microsoft .NET Framework versions, and the Microsoft C++ 2005 Redistributable software if it is listed.

Close the Control Panel and go to My Computer. Open the C:\ drive and open the Program Files folder. In this folder, if you see the Sony Setup folder, please delete the entire folder along with any of its contents.

If you have a Sony folder remaining in Program Files, please open this as well. If there are any folders corresponding to a Sony Creative Software or Sony Media Software program, such as ACID, Vegas, DVD Architect, Media Manager, Shared Plug-Ins, or any of our software you may have installed, please remove these folders. If these are the only folders in C:\Program Files\Sony, please remove the enitre Sony Folder.

Disable everything under Services and Startup in the System Configuration Utility. Do this by going to Start > Run, then type MSCONFIG (in Windows Vista, click Start and then type MSCONFIG in the Start Search box). Click the Services tab, checkmark Hide All Microsoft Services. Now click Disable All and Apply. Now click the Startup tab and click Disable All. Click Apply and Close. Choose to restart the computer.

Once again, go to Start > Run and type REGEDIT. This will take you into the Registry Editor.

**Before making changes to your registry, we advise that you save a backup. If you are unfamiliar with this operation you may want to contact your IT personal or take a look at this article: http://support.microsoft.com/kb/322756 - How to back up and restore the registry in Windows XP and Windows Vista**

Locate the following keys and delete them:

HKEY_CURRENT_USER\Software\Sonic Foundry
HKEY_CURRENT_USER\Software\Sony Media Software
HKEY_CURRENT_USER\Software\Sony Creative Software

HKEY_LOCAL_MACHINE\SOFTWARE\Sonic Foundry
HKEY_LOCAL_MACHINE\SOFTWARE\Sony Media Software
HKEY_LOCAL_MACHINE\SOFTWARE\Sony Creative Software

Now download the latest update for your software. You can find the latest update for any program at http://www.sonycreativesoftware.com/updates
When this has finished downloading, please install the software directly from these downloaded updates and not from any previous updates or discs you may have.

yikes! that is certainly the cleanest un/install i've read about!

i don't want to defend scs, but (and not only touching but eating wood), 8b has been incredibly reliable - yes, ive had m2t's crash vegas, but after running them through mpeg2repair (or as laurence also suggested, womble), vegas itself has behaved impeccably.

i'm running xp pro, sp3, dual monitors (via ultramon), 3gb ram, ex hd's, etc

i'm angry about m2t's crashing vegas when anything else sails through the 'error'. this might not even be their fault, could be main concepts problem - either way, it's a pita, big time.

i too hope for answers in 8c.....

leslie

Version 8 is to Vegas what Vista is to Microsoft.

Darren,

I think it is a memory management issue, but it is centered around the GUI code.It is not necessarily directly related to to running dual screens, but dual screens make the problems happen for me in my particular case.

The thing that got me was that I was getting menus hang just by on them or clicking in their window. The bar would turn white and just sit there doing nothing. This suggests that while the procedures that redraw the menus are executing, something has gone wrong. I don't know Windows very well on a coding level, but I would assume this is an unusual fault as you would expect Windows to handle the basic GUI functions of the windows within the program. It suggests to me that there is something wrong happening with the areas of memory reserved by the program to allow basic GUI operations to happen.

If there is a conflict between the GUI and the way memory is handled, the chances are it is caused by some other operation writing into a reserved space. That would also mean that that operation causing the conflict would itself be likely to fail and cause exceptions.

The practical upshot could be that when I use two screens, that conflict is brought into play. When I use one screen, the GUI memory usage is less and it may not write to the conflicted area..

This is all reasoning from my knowledge of Amiga. I've never really written anything for Windows so it could all be hogwash. But anything that stops the gui mid redraw has to be a pretty fairly fundamental problem.

One other thing, I am pretty amazed about reports of "damaged" .m2t files crashing Vegas. What is going on with the error handling? It gets an unexpected value in the file and then it sprays enough garbage across the memory o cause an exception? Seriously guys, that is very poor.

MichaelduS,

Don't waste your time. Sony provided me with the same instructions which I followed to the letter. As I expected, since I had installed 8b on a new computer, It made no difference at all. Same problem after the reinstall as before.

Two steps that others have recommended that might try: (1) use 7d if you have it...never had a problem with HD in 7d; (2) capture for 8.0 using the Sony capture utility instead of third party capture utilities such as HDVSplit. Again I have had no problems using clips captured with HDVSplit in 7d. The same clips crash in 8.0.

Peter