Vegas pro 14 is buggy as hell!

peterh337 wrote on 7/8/2017, 4:08 AM

Version 14 is a piece of JUNK.

It crashes all the time. Especially if you do any rendering which is, kind of, necessary!

This crash followed two renders of the same loop region, one at 30fps and one at 60fps, 1080P, XAVCS template. 4K source material.

It looks like the only way to run v14 is to render and then exit and restart the program.

But there are many other things which cause it to crash.

I will have to go back to v13, but that didn't seem to do 4K rendering (which I don't need much however).

Comments

john_dennis wrote on 7/8/2017, 8:34 AM

Vegas Pro 13 is quite able to render 4K.

Kinvermark wrote on 7/8/2017, 8:40 AM

Version 14 is a piece of JUNK.

Nope. Works fine here. Fix your system.

peterh337 wrote on 7/8/2017, 9:58 AM

Unfortunately my system is just fine. Top-end-everything, 6-core, runs all the other video stuff great e.g. Handbrake, 24GB RAM, tested on 20-50hr renders with all cores maxed out, CPU temp nice and low, rock solid with an uptime of months.

Movie Studio 11 was rock solid, winXP. v12 was also solid. Pro 13 was mostly OK and with just a few lock-ups.

I will have another go with v13. I hope my earlier Vegasaur and NewblueFX licenses still work with it...

OldSmoke wrote on 7/8/2017, 10:30 AM

Do you have the lates .Net installed?

peterh337 wrote on 7/8/2017, 11:06 AM

How can I tell, and why would Vegas not check the version and say if it is not supported?

BTW, windows 7 64-bit.

RealityStudio wrote on 7/8/2017, 3:13 PM

Are you overclocked by chance? I once had an issue with rendering in Vegas Pro is when I used to overclock, seems like Vegas Pro is extremely sensitive to that. Everything else would work fine (games, tools, apps, etc) but Vegas Pro would crash. The only other time I've had Vegas Pro crash on renders is when I used to use a generic power supply. Again every other app would work fine, but Vegas Pro was unreliable with it because it couldn't deliver consistent power. I switched to a somewhat more expensive name brand power supply years ago and haven't had an issue since. In both of the above cases everything else I did on those machines including intensive gaming would work fine, it was only Vegas Pro that brought out the issues with my systems.

peterh337 wrote on 7/9/2017, 12:50 AM

No overclocking. It's all top-quality hardware and while (having built many PCs) nothing can be ruled out, everything else runs fine, as do previous Vegas versions.

Vegas V14 doesn't crash during renders. V13 used to, every time, until I disabled everything to do with the GPU, in the rendering template and also in global settings. With V14 I am running the default settings and it completes the job, but then ends up being "unstable" - a euphemism for having crashed but it hasn't manifasted itself until you do something else. But maybe I need to disable all the GPU stuff also in V14.

The video card is a GTX750 Kalm http://www.palit.com/palit/vgapro.php?id=2378&lang=en

BTW I have just noticed that V14 doesn't have GPU enable/disable in the rendering template. Not all of the templates had it anyway but this one did in V13:

http://peter-ftp.co.uk/screenshots/2017-07-09_080143.jpg

So I disabled GPU in global prefs. And V14 bluescreened the computer (!!) when using the XAVC template so I am now doing another render with the one in the above screenshot. That is the one I normally used (mainconcept) in the past.

EDIT: I wonder if V14 removes the GPU config from all rendering templates if GPU is disabled globally? It would make 100.000% sense. The V13 system was weird because - obviously - disabling it globally should do anything anywhere else.

Next I will look at the GPU options in the NewblueFX lens correction. That also needed GPU disabled in V13. It does look like V14 doesn't have any better GPU support than V13; it just crashes in a more subtle way...