Comments

malowz wrote on 6/14/2012, 3:38 PM
this is happening to me also. last time i was just exporting small video, not even recompressing. on exit, "vegas crashed"

will wait to happen again and try to find similarities with the other times to find the cause...
ritsmer wrote on 6/16/2012, 5:24 AM
Grazie has some posts about this here in the forum - it seems that (for some users) closing Vegas by clicking the red X in the upper right corner sometimes leads to this error while closing Vegas by using the menu File and Close does not.
Could you please check on your machines?

BTW: On my machine Vegas 11 always ends normally by pressing the red X. Strange!
malowz wrote on 6/26/2012, 5:02 PM
today happened 2 times, now remembering back, i believe this problem showed up after i installed canopus codecs and cedocida DV codec (using this one instead internal dv codec)

if is the codecs, likely to be cedocida (i use canopus codecs for a long time)

the problems is that does not happen every time, so will take a long time to "diagnose"...
RobertVL wrote on 7/3/2012, 2:57 PM
I'm using Vegas Pro 64 bit and have had the EXIT error - "Program not responding".
It seemed to me, I would get this error after applying OFX and other VFX plugins.
I changed the UAC to it's lowest setting and have not had this error for a few months.
I always close Vegas using MENU-EXIT.
Changing the UAC might help other Vegas users.

Robert.
Kimberly wrote on 7/3/2012, 3:30 PM
Windows 7 32-bit, VP Pro Build 682.

I get the crash with the Red X as well as closing from the file menu. I have noticed the crash does not occur when I have not edited a file. For example, I open a file, view it and play it, but make no edits.

I've noticed I can add media, FX, and transitions that are not GPU enable, save, and close with the Red X and no crash occurs. But if I use any FX or transitions that hint at GPU enabled, save, and close with the Red X, then I get the error message. I've tested this by creating a .veg file and incrementally adding media, saving, closing, reopening, adding FX, etc.

I'm able to use all my NewBlue stuff without any crashes upon close as long as I don't select "upgrade" on the GPU enabled feature.

I am able to use NewBlue Titler Pro without problems (runs slow on my old machine) and I can successfully render. Okay here is the weird part with NewBlue Titler Pro. Before the Windows update yesterday, this plug-in caused a crash 100% of the time. Post Windows update, I can save and close with the Red X and sometimes to often I get the crash, but sometimes not. My error messages point to nvogl32.dll in the System32 folder of Windows.

I have a theory that if you uncheck the box that tells Vegas to automatically open the last file edited, this somehow minimizes the crash upon closing. I cannot really explain why so this is just a theory.

Running in the compatibility mode and closing via the file menu does not make a difference for me.

I have some available time for testing right now so would love to help identify a workaround on this.

Regards,

Kimberly
Zeitgeist wrote on 7/3/2012, 3:38 PM
If I let vegas sit for bit of time before I close it, I am less likely to get the crash on exit.