Hey Peter--

I was just trying to play back.
Have a session that uses a lot of realtime FX (EQuality, Roomverb, nothing crazy) and real time pitch and time shift.

Noticed that the crashes came most often on time stretched events...

C

And yes, I did get a crash report box thingy.

CRASH AGAIN!

Extra Information
File: C:\Users\Owner\AppData\Local\Sony\Vegas Pro\10.0\dx_video_grovel_x64.log
File: C:\Users\Owner\AppData\Local\Sony\Vegas Pro\10.0\svfx_video_grovel_x64.log
File: C:\Users\Owner\AppData\Local\Sony\Vegas Pro\10.0\dx_grovel_x64.log
File: E:\Projects\Adventures_of_Gordon_and_Grace_Fall_2011\Project Files\Ediit_12.veg

Problem Description
Application Name: Vegas Pro
Application Version: Version 10.0e (Build 738) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 10.0\sfvstwrap.dll
Fault Address: 0x000000000F9F2417
Fault Offset: 0x0000000000002417

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 10.0\vegas100.exe
Process Version: Version 10.0e (Build 738) 64-bit
Process Description: Vegas Pro
Process Image Date: 2011-06-29 (Wed Jun 29) 17:33:50

Looks to be a VST that is causing it.

What VSTs are you using in the project? Are they 32 bit or 64 bit?

How are you using them? Bus? Track? Event?

Peter

would you be willing to let me send you my project?

Since I'm using 64 bit Vegas, pretty much only VSTs are available to me.

64 bit EQuality
32 bit roomverb
64 bit speakerphone
32 bit RComp

I use them as Bus, track AND event, as well as sometimes assignable.
crashes seem to happen on time stretched events the most...

Can I send you my project file so you can look?

in another thread http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=792745 you say you are using "up to 30-40 instances room verbs, 7-10 instances of RComp, maybe 5 instances of speakerphone and several hundred instances of EQuality."

With that many VSTs loaded I'd surmise you are severely overloading either your CPU or Memory, ..... or have a dodgy VST loaded.
E.g., SpinAudio's RoomVerb series is notoriously unstable, even with just one instance ....

@ChristoC

Thanks for the thoughts! Maybe you can help me troubleshoot by looking at my project? If you'd like I can send you a copy of my project (with the associated media) and maybe you can tell me more about what's going wrong?

It would be more accurate to use my whole sentence:

"As many as I want" is up to 30-40 instances room verbs, 7-10 instances of RComp, maybe 5 instances of speakerphone and several hundred instances of EQuality.

'm a professional sound designer and re-recording mixer-- some feature films require hundreds of tracks and hundreds of plugins-- shouldn't Vegas be able to accommodate this?

I do a lot of projects with RoomVerb and have been using it for years no problem. I used to use the DX version of Roomverb, but Vegas 64 bit can't do 32 bit DXs. Is the VST less stable than the DX? is Vst less stable in general? If so, why doesn't Vegas support a DX wrapper?

Also, my system is still crashing with as little as 10 instances of EQuality and real time time stretch and pitch shift and nothing else.

In terms of computer being taxed-- ProTools (which I hate by the way) and Nuendo on the same system can run the same plugin-load fine. I

We just bought a brand spanking new system from ADK, and I don't think that this plugin load should tax things.

That really sounds like a significant load for any DAW on any platform !

Especially if what Cristo suggests is the case - that Roomverb is not the most stable plug in the world.

Maybe worth a try to do a test project on a similar scale with, say, the stock Sony track reverb to see how that works.....

geoff

I've done a test project with only 10 instances of EQuality and am having the crash. (0 RoomVerbs)

C

Also-- I work on narrative feature films--- need to be able to accommodate for 5.1, and lots of FX-- especially with fantasy and sci-fi films.

Maybe it's the a low EQuality. AGain, substitute the EQuality for stock Sony plug and see if fault goes. If not, then it's V, or your media.

geoff

My experience with RoomVerb is VST... don't know about DX version. The VST version can crash some DAWs just because the .dll is in the VST folder, and not even in use.
No use sending me your project file; I have none of those FX installed.

Simply, if PT or Nuendo run with that track & plugin load fine on your PC why not use either of them?; I agree Vegas gets pretty flakey with a lot of tracks + plugins - never understood why; I work with large track counts (orchestral music for Film) & just use another DAW in preference (not PT), which also has it's own hardware DSP cards so there are no issues with performance or latency.

cchoy...

64 bit EQuality
32 bit roomverb
64 bit speakerphone
32 bit RComp

From my experience do not waste your time mixing 32bit with 64 bit anything...

If you run in a 64 bit environment use 64 bit software...period...NEVER mix...the trouble shooting will drive you nuts and take away from you creating.

Remember just because you can doesn't mean you should.

HTH...

hrm--

sounds like the response is: Vegas can't handle what you want to do.

Not exactly what I've been looking for. After all, I feel like the "pro" in Vegas "Pro" aught to count for something....

No...this is a response to my experience with Sony and cakewalk products...Don't let the B.S. hype fool you...DO NOT MIX...

-64 bit OS...64 bit APP...64 bit plugins...thats it...PERIOD...anything else you are on your own...too much to type sorry I'm tired...just take my advice...

If there is a bug in the above setup then trouble shooting and finding/fixing will be easier...

You have been warned...good luck...

HTH...

thx for the heads up.

should I move back to the 32bit version of Vegas?
Will it run okay on a 64 bit system?
anyone else have any thoughts on this?

Again if you are going to run vegas in 32 bit...What did I say to do?

example...Vista/Win7 32 bit...Vegas 32 bit...32 bit vst plugins...for the best results...

You are completely wasting your time doing anything else...I have limited experience with the audio side of vegas as of recent to tell you if there is any advantages running in a 64bit environment...my gut is telling me no...I trust my gut...stay in 32 bit...If you were running virtual instruments then sure you might need it...but for audio track count and plugins???

HTH...

Ed.

I am getting a crash in Vegas Pro 8 when opening a recently-edited .VEG file. I have just upgraded to a Win7 64-bit PC, but the Vegas version is 32-bit. Since you advise against mixing 32/64 bit plugins, do you think this could be my problem?
Here are details of the crash message:

Sony Vegas Pro 8.0
Version 8.0 (Build 144)
Exception 0xC0000094 (integer divide by zero) IP:0x11CCC819
In Module 'mcmp4plug.dll' at Address 0x11BE0000 + 0xEC819
Thread: ProgMan ID=0x16E4 Stack=0x472E000-0x4730000
Registers:
EAX=00000000 CS=0023 EIP=11ccc819 EFLGS=00010246
EBX=077a4984 SS=002b ESP=0472ec88 EBP=077a48a8
ECX=00000000 DS=002b ESI=00000002 FS=0053
EDX=00000000 ES=002b EDI=00000000 GS=002b
Bytes at CS:EIP:
11CCC819: F7 F1 8B 44 24 0C F7 F1 ...D: 8B C2 33 D2 4F 79 4E EB ..3.OyN.
Stack Dump:
0472EC88: 00000000
0472EC8C: 077A4984 075B0000 + 1F4984
0472EC90: 11BF28A5 11BE0000 + 128A5 (mcmp4plug.dll)
0472EC94: 00000002
0472EC98: 00000000
0472EC9C: 00000000
0472ECA0: 00000000
0472ECA4: 077A4980 075B0000 + 1F4980
0472ECA8: 077A4984 075B0000 + 1F4984
0472ECAC: 00000000
0472ECB0: 00000000
0472ECB4: 077A48A8 075B0000 + 1F48A8
0472ECB8: 077A48D8 075B0000 + 1F48D8
0472ECBC: 0472F0E8 04630000 + FF0E8
0472ECC0: 00000000
0472ECC4: 00000000
> 0472ECE0: 7777F8C1 77760000 + 1F8C1 (ntdll.dll)
> 0472ECE4: 75120816 75110000 + 10816 (KERNELBASE.dll)
> 0472ECF0: 75120849 75110000 + 10849 (KERNELBASE.dll)
> 0472ED40: 75145EE0 75110000 + 35EE0 (KERNELBASE.dll)
> 0472ED4C: 75120849 75110000 + 10849 (KERNELBASE.dll)
> 0472ED50: 768D1194 768C0000 + 11194 (kernel32.dll)
> 0472ED5C: 11BF30B7 11BE0000 + 130B7 (mcmp4plug.dll)
> 0472ED94: 11BF2579 11BE0000 + 12579 (mcmp4plug.dll)
> 0472EDD4: 7511D117 75110000 + D117 (KERNELBASE.dll)
> 0472EE00: 00B2186C 00400000 + 72186C (vegas80.exe)
0472EE04: 033F31B8 033B0000 + 431B8
0472EE08: 00000000
0472EE0C: 3FF00000
> 0472EE10: 7697410E 768C0000 + B410E (kernel32.dll)
> 0472EE38: 00480000 00400000 + 80000 (vegas80.exe)
> 0472EE3C: 00480000 00400000 + 80000 (vegas80.exe)
0472EE40: B5112287
0472EE44: 4047F9DC
0472EE48: 0012003B 00090000 + 9003B
0472EE4C: 00000045
> 0472EEB4: 0041005C 00400000 + 1005C (vegas80.exe)
> 0472EEB8: 00640075 00400000 + 240075 (vegas80.exe)
> 0472EEBC: 006F0069 00400000 + 2F0069 (vegas80.exe)
- - -
0472FFF0: 00000000
0472FFF4: 00524C90 00400000 + 124C90 (vegas80.exe)
0472FFF8: 00AD7658 00400000 + 6D7658 (vegas80.exe)
0472FFFC: 00000000
The problem does not arise with all .VEG files, but with the one I have been working on for over a week, and it's going to be a real hassle going back to square one. Can abyone help me recover this file?