Vegas Pro 11 (595) 64-bit crash when using...

FTech wrote on 2/29/2012, 4:34 PM

Hi all,

I've updated to the new Vegas build (595) and noticed it crashes when using these two transition effects: Spiral & Zoom. To recreate this issue turn on GPU acceleration and have NVIDIA driver version 295.73 installed. Place any clip either a video or image on the time line and create a fade in or out... your choice. Insert either a Spiral or Zoom transition in place of the fade. Press play to play the transition effect and Vegas will hang/crash. Keep in mind it won't crash when GPU acceleration is off.

I installed the latest NVIDIA Driver 295.73 a while back before I installed the new Vegas Pro 11 build 595. And Vegas DID NOT crash with build 521. Hopefully I'm not the only one that noticed this issue.

FTech

My system specs:
Windows Version:7 64-bit
RAM:12 GB
Processor:Intel® Core™ i7-930 Processor @ 2.80Ghz
Video Card:EVGA Nvidia Geforce GTX 465 (v295.73)
Sound Card:Auzentech X-fi Forte 7.1 (v6.0.1.1403)
Video Capture:VIA 1394 OHCI
CD Burner:ASUS DRW-24B1ST (Firmware 1.03)
DVD Burner:ASUS DRW-24B1ST (Firmware 1.03)
Camera:Panasonic AG-DVX100
Add. Comments:Asus Rampage Extreme III Mobo (Bios version 1502) Not overclocked

Back to post

Comments

johnmeyer wrote on 3/2/2012, 2:13 PM

Unable to reproduce here. I have build 595 (64-bit) running with an "older" nVidia GeForce 9800 GT running drivers dated 10/15/2011. I get no crash with either of these two transitions.

[edit]Further testing reveals that after playing this transition, timeline performance slows to a fraction of what it was before. So, no crash, but definitely something going on. This slow timeline performance is something I have been reporting since the previous build. When editing a project with 1/2 hour of 60p AVCHD footage from my Sony CX700V camcorder, everything is fine for a few minutes when suddenly the timeline performance becomes sluggish. If I quit and then re-start Vegas and return to the place on the timeline where I was editing, full-speed performance resumes.

So far, this only happens with GPU enabled, although I am trying to come up with a repo scenario that I can send to Sony, and as part of that work, am trying to see if I can get it to happen without GPU (this eliminates a variable and makes it easier to troubleshoot).

johnmeyer wrote on 3/2/2012, 2:44 PM

All sorts of unrepeatable weirdness going on.

I created a small test case consisting of 60p AVCHD footage from my Sony CX700V camcorder. I overlapped two small clips and added the spiral transition. I followed that with another short event, with some text on the track above, using the old text generator.

If I start Vegas, open the project, and play the second clip, with the text overlay, I get a full 59.94 fps preview at "Preview" resolution. This is true with both the 32-bit and 64-bit version, and with both the GPU enabled (my nVidia GeForce 9800GT using the 10/15/2011 drivers) and with it disabled. However, on the 64-bit version only, when I enable the GPU preview support, if I first play through the spiral transition (which does not crash) and then play the clip with the text overlay, I get only about half the fps playback speed. The only "cure" for this is to quit and re-start Vegas.

What is more, sometimes the system gets into the state that when I re-start Vegas 64-bit and try to load the test project, I get the following error message:

{0FE8789D-0C47-442A-AFB0-0DAF97669317} - Media Generator

0fe8789d-0c47-442a-afb0-0daf97669317 - Media Generator

{0FE8789D-0C47-442A-AFB0-0DAF97669317} - Media Generator

0fe8789d-0c47-442a-afb0-0daf97669317 - Media Generator

StereoRealist wrote on 3/3/2012, 10:23 AM

Same problem here. These effects worked on previous build. Thanks for posting, you saved me hours of troubleshooting.

Suvin111 wrote on 3/3/2012, 3:55 PM

I have reformted C and reinstalled Windows 7 64BIT, Motherboard chipset drivers, video drivers and updated Windows to Service Pack 1. Then I installed Norton, MS Office 10 and Sony Vegas Pro 11.
So for it is stable. I'll try some of the edits mentioned here to see how it reacts.

ushere wrote on 3/3/2012, 5:42 PM

NORTONS!!??

Suvin111 wrote on 3/3/2012, 9:22 PM

Norton Internet Security - anti-virus software

Suvin111 wrote on 3/3/2012, 9:32 PM

After a couple of hours things started to happen - or make that not happen. I was using Deform - and after a while moving the sliders didn't make any difference any more. Also, Track Motion changes that I made - suddenly were not there anymore. Vegas "locked up" and stopped working - but this time without any error messages.
I tried it again - and the sliders stopped working again - but no errors. I closed and saved the project – and then got an error message. It created an error log which it sent in to Sony – but unfortunately – I didn’t keep a copy.
So now we have an install on a pretty vanilla system – and still Vegas Pro can’t run. Hard to figure out what to do next.

ushere wrote on 3/3/2012, 9:56 PM

i know what nortons is - and as an editor you should too ;-)

get rid of it, if you have to use anti-virus get something unobtrusive - i use mse on both my edit pc (have to connect to the net sometimes with it), and on my laptop that goes to some weird places on the net when my daughter uses it.

Suvin111 wrote on 3/4/2012, 2:47 PM

I'm sorry ushere - I just never know who I talking to in here. I'll check out mse - I guess I've been using Norton so long I never thought of anything else - besides I'm addicted Identity Safe. :-|

In any case, I moved over to Windows 8 and haven't have a crash so far. Don't really know how long this will last though.

Suvin111 wrote on 3/5/2012, 7:49 PM

I used SVP for 3-4 hours in Windows 8 - no crashes.
I have rebuilt back to Windows 7 and the crashes are back. In a very strange case - I had a new Project file with only two tracks - one with a Red Media Generator and one with Black. The Black track was active and I used the up arrow to get to the Red track - SVP stopped working. I tried to duplicated the error but have not been able to. Seems like - this version of SVP is just not useable - like many others, I guess I've got to go back to 10 to keep projects on schedule.

dlb wrote on 3/23/2012, 9:03 AM

I just purchased Vegas Pro upgrade from Movie Studio because I wanted more functionality. So far (and I know my computer is slow and tired) but I can't even do a chroma key as it crashes the program. This is a time critical video and I'm thinking of going back to Home Studio version to get it done and forget some of the fun effects as the program is very unstable.

I run Win 7 64 bit. I have an Nvidia GT9500 card. But I can't do anything in Pro with the program crashing. 12 times yesterday.

I don't think I can roll back to version 10 as I never had it to begin with. :(

Gary James wrote on 3/23/2012, 11:39 AM

Before build 595 GPU video was inoperative for me. I could only preview a few frames of video and then Vegas would lock-up or crash. 595 and the latest nVidia drivers fixed this.

I'm not experiencing the same problem with Spiral and Zoom that you're seeing. I'm using both (with multiple preset selections) throughout my slideshow project. And I can view these using either GPU or CPU video processing.

Maybe this is because I have an older GeForce GTS-250 video card. Less complex equals less to go wrong!

FTech wrote on 3/23/2012, 6:02 PM

dlb quote: "I run Win 7 64 bit. I have an Nvidia GT9500 card. But I can't do anything in Pro with the program crashing. 12 times yesterday".

@ DLB: I hate to say this but if you read the system requirements for Vegas Pro 11... in "Technical Specifications"... then look below and click on "GPU Acceleration Page" link... it says "Requires a CUDA-enabled GPU and driver 270.xx or later. GeForce GPUs: GeForce GTX 4xx Series or higher (or GeForce GT 2xx Series or higher with driver 285.62 or later)." Your card unfortunately doesn't fit the requirement. All you can do is disable GPU acceleration in Vegas and hopefully it will stop the crashes.

@ Gary James: If you want... you can do the Spiral & Zoom transition again and this time set the preview quality to BEST or GOOD. This made it crash for me. If you set preview quality to DRAFT or PREVIEW... it won't crash. Thanks to JasonATL for pointing this out.

FTech

Gary James wrote on 3/24/2012, 10:34 AM

"@ Gary James: If you want... you can do the Spiral & Zoom transition again and this time set the preview quality to BEST or GOOD. This made it crash for me. If you set preview quality to DRAFT or PREVIEW... it won't crash. Thanks to JasonATL for pointing this out."

I have an older GeForce GTS-250 graphics card, and I am using Best(Full) in Preview mode. I've also set my Project Full-resolution rendering quality settings to Best. In my case, before build 595, GPU preview and rendering was completely non-functional. After build 595 and updating my nVidia driver to v296.10, my GPU now works for both Preview and Rendering; although GPU rendering is about 40% slower than using the CPU. So I wont be using it for that. But it does allow me to preview my project at full resolution where the CPU only works in Preview resolution mode.

However, I still experience random crashes when manipulating FX settings on multiple Events, but this is not related to using GPU acceleration.

FTech wrote on 3/25/2012, 4:09 PM

@ Gary... Very interesting... **scratching chin** that it didn't crash for you with the Nvidia driver v296.10 with Vegas Pro 11 build 595. I'm curious in what manner did you upgrade Vegas to build 595. Did you install the update over your previous installation? Or did you first uninstalled Vegas 11... then installed build 595?

FTech

Gary James wrote on 3/25/2012, 6:24 PM

"@ Gary... Very interesting... **scratching chin** that it didn't crash for you with the Nvidia driver v296.10 with Vegas Pro 11 build 595. I'm curious in what manner did you upgrade Vegas to build 595. Did you install the update over your previous installation? Or did you first uninstalled Vegas 11... then installed build 595?"

Actually, I upgraded Vegas to 594/595 and then saw the notice about new nVidia drivers. So I also upgraded them. So I can't really say if it was one or the other or both that fixed my GPU rendering problem.

Whenever I've upgraded Vegas, I've always done it as an update to an existing install. I've done it this way since Sonic Foundry Vegas v3.0. I never un-install the software unless the software installation program specifically instructs me to do so. There are technical reasons why this is needed in some cases. But for most software installations this is unnecessary. And since the Vegas Setup software does not state this is a requirement, I don't bother.

I should mention that I also have 32 & 64 bit Sony Vegas Pro version 9. And 32 bit Sony Vegas Pro v8 installed on my Windows 7 PC.

Suvin111 wrote on 4/13/2012, 11:33 AM

I am using a Asus P8Z68-V PRO
Stock Clock
All other software is stable

MonteMedia wrote on 4/17/2012, 11:46 PM

My very stable (otherwise) PC crashes on me just creating a simple title using static text on a solid background.
Editng video and sound is smooth going.

Vegas Pro 11 - build 595 (64-bit)
Intel Core based PC
3 drives for editing
8GB RAM
nVidia GeForce GTX 550 Ti (driver version: 296.10)

Royce1 wrote on 4/27/2012, 8:06 AM

I have Vegas Pro 11 (64 bit) - running on Windows 7 64 bit machine.

The program kept crashing when using things like Title & Text, Chroma Keyer and even Color balance. It also crashed with NewBlue Plug in for Vegas.

Sony had me do all sorts of things - and it kept crashing.

On April 27, 2011, - I suddenly tried changing Vegas Pro 11 by using WINDOWS compatibility feature. (Right click the Icon of Vegas, choose Properties and then choose the Compatibility Tab) - The compatibility options are:

Windows Service 2008
Windows Vista
Windows Vista (Service Pack 1)
Windows Vista (Service Pack 2)
Windows 7

I decided on "Windows Vista"

THEN when I ran Vegas Pro 11 - both the Chroma Keyer and Color balance worked - and so far the program did NOT crash. I got it to render out too. I also tried “Titles & Text” and Vegas did NOT crash. NewBlue plug in also did NOT crash.

Could all this verify that Window 7/64 bit and Vegas Pro 64 bit are in conflict? I just sent off an email to Sony Support.