Comments

ushere wrote on 10/27/2012, 4:50 AM
what's on your tl?

this can occasionally happen with bad media.
Richard Sword wrote on 10/27/2012, 7:54 AM
Media is ok. The problem is the sudden closing of the Vegas 12 pro This sometimes happens when you least expect. I had to run autosave, so as not to lose too much of the project.
Enerjex wrote on 10/27/2012, 8:45 PM
Random crashing can happen for a number of reasons. Please provide some more information about what you're doing because at the moment you're not giving us a lot to work with.
ushere wrote on 10/27/2012, 9:39 PM
blow out the dust?
Richard Sword wrote on 10/29/2012, 2:35 AM
It happened while working with a small project.
I used him short video samples in *. Mov.
The project was almost completed when he suddenly stopped in Vegas 12 and Windows displays a window with a report to be sent, this situation has become 3 times. The project was not burdensome for either the computer or the program. It was a 4-track video including text path.
Project time of 15 seconds. Fortunately, I was able to finish it up with audio tracks, but for me it is a worrying state. In Vegas 11 pro such problems rarely occurred and in rather large, for example 30 minutes project.
Grazie wrote on 10/29/2012, 2:41 AM
Was the project started in VP11?

Do you have GPU acceleration turned on?

G
Richard Sword wrote on 10/29/2012, 2:55 AM
I do not know if I understood you well. The computer is in great shape and do certain tasks in other programs for video. If it was a problem with my computer, I'd have a total reboot of the blue screen, inclusive. So not happening. This indicates to me Windows 7 software problem and shows me a window to send the report. I worked on a tiny 15-second project with video samples * mov format. 4-track video and already showed problems. Of course unutterable fortune I got to the end of the job, but the whole time I was worried that once again I will not have problems with the ending.
Richard Sword wrote on 10/29/2012, 2:57 AM
Yes, video acceleration is enabled.
When working with Vegas Pro 11 such cases were very rare, and when large projects. But this time, I began working with the latest version of Vegas Pro 12 with a very small project.
Grazie wrote on 10/29/2012, 3:16 AM
1] Turn off acceleration.

2] Establish if your video cards are recommended to work with VP12.

G

mikkie wrote on 10/29/2012, 4:49 PM
Purely FWIW, since Vegas 11 introduced GPU assist it can work not as expected. When problems have occurred for me turning off GPU acceleration has made little or no difference for the most part -- an exception is MC AVC Blu-Ray encoding in Vegas Pro 12, where GPU assist on in the MC dialog causes non-compliant AVC to be rendered. Recently the ATI 12.9 driver broke mpg2 encoding in Vegas Pro 11 32 & 64 -- ATI's Cat v. 12.10 just broke it in the 64 bit version, though in Vegas Pro 12 it works fine.

Unless an error message shows up in Windows' Event Viewer, or unless it's a common problem that's widely reported, you're flying a bit blind. Do try turning GPU assist on/off, but if it doesn't help don't assume your problem's unrelated to your graphics hardware, & maybe consider backing up & trying a different graphics driver version if you don't find anything else suspect. If Vegas Pro hasn't completely shut down from a crash, Sysinternals Process Explorer can give a clue, particularly in the Threads tab of the Properties window for the vegas' .exe file, where in the past Dxing a problem I've spotted conflicting files appearing & closing rapidly. Sysinternals Process Monitor OTOH can show what was happening just before it crashed. I've used Process Monitor to see what files are called or opened by Vegas with whatever project, noted those that weren't part of Vegas, then after closing Vegas disabled those files -- that can help when you have a conflict, e.g. AFAIK Vegas doesn't officially support Intel OpenCL, yet it calls/opens it, &/or it may use external files for decoding whatever you've got on the timeline. And of course if an app like Vegas Pro is working properly, then it doesn't, obviously any changes made to your system are suspect.