Vegas Pro 13 crashes on render, but 11 works fine

NCARalph wrote on 4/26/2014, 10:13 PM

I've got an 18 minute 1080 30P clip with no FX or pan/crop modifications which I'm trying to render as an MPEG 2 on a Window 7 machine with a Nvidea GTX 570 This works without problem using Vegas Pro 11. It always crashes on rendering with Vegas Pro 13 and the estimated time to do the rendering is just about twice the time for Vegas Pro 11.

I think their support for GPU rendering, at least for the GTX 570 is pretty broken. The same clip renders flawlessly in Vegas Pro 13 with the GPU turned off.

Back to post

Comments

NCARalph wrote on 5/21/2014, 5:10 PM

Almost all DVD players work fine with this and it has the advantage of allowing cropping with far fewer artifacts.

What do you mean by resetting VP13? I rebooted the machine before trying this.

OldSmoke wrote on 5/21/2014, 5:19 PM

If you mean 24P I can see that but 30p (29.97p) is not a DVD standard. I believe if you bring that into DVDA it will be re-rendered to 29.97i.

Resetting Vegas Pro means holding down CTRL+SHIFT while double clicking to launch it. This will however reset any customization you have done to it too.

NCARalph wrote on 5/21/2014, 5:24 PM

No, DVDA doesn't rerender it. I've done this on many disks without ever rerendering.

I'll try the CTRL+SHIFT and report back.

OldSmoke wrote on 5/21/2014, 5:25 PM

[I]No, DVDA doesn't rerender it. I've done this on many disks without ever rerendering[/I]

Interesting... I must give that a try and see if my oldest DVD player can handle it too.

NCARalph wrote on 5/21/2014, 5:38 PM

Starting with CTRL+Shift and using the stock DVD 24P template it crashed at about 9:30 with about 9 minutes estimated remaining. It not only crashes, it's very slow, over twice the time for VP11.

NCARalph wrote on 5/21/2014, 5:42 PM

The reason I do the 30P DVD rendering is because I do a lot of post processing zooms and pans. It's OK in 24P, but I like the look of 30P. Normal 30i results in really bad motion artifacts if the crop height isn't an integral fraction of 1080, 540 is fine but 600 is awful if something like an actor's arm is moving rapidly through the scene.

48snapper wrote on 6/6/2014, 5:43 PM

I upgraded from Movie Studio 11 to Pro 13 Build 310. Everything was lovely until I wanted to render. (GTX 470 /.mp4 file / Win 7). Vegas crashes everytime but the same project will be fine in Movie Studio.

I have tried the suggestions in this thread without success. This is a real pain, please help!

OldSmoke wrote on 6/6/2014, 6:12 PM

Which driver are you using for the GTX470? If you can, go back to driver 296.10 or if you need a later version, try 334.89. These are the most stable versions only system with 2x GTX580.

48snapper wrote on 6/7/2014, 11:26 AM

Many thanks for your reply.

The driver was 9.18.13.3165. After two roll backs it is now 9.18.13.697. The list of drivers I can find via device manager are all in a similar numbering scheme. Therefore I'm afraid I don't recognise the drivers you mentioned.

48snapper wrote on 6/7/2014, 11:35 AM

My apologies. After looking properly I can see those details on the Geforce site. Now downloading version 334.89.

OldSmoke wrote on 6/7/2014, 1:03 PM

@48snapper
Also make sure have "Windows Automatic Update" disabled, that is never a good thing anyways!

ChrisDolan (SCS) wrote on 6/9/2014, 1:52 PM

A useful nvidia fact is that the version number "9.18.13.3165" is generally the same as "331.65" (look at the last 5 digits). I don't know if that's always true, but I've noticed the pattern a couple of times.

48snapper wrote on 6/19/2014, 7:31 AM

i eventually had a fix from Sony. Vegas Pro 13 must be installed on your system drive, not as I had done on a different one. Once re-installed on my C drive the problem was sorted.

Strange though as most of my programs, including various Movie Studio versions, are working well on the F drive.

NCARalph wrote on 6/21/2014, 9:47 AM

That's interesting, mine is on the C drive and crashes on a lot of renders. I've tried uninstalling it and reinstalling it with no improvement as well.