Considering switching to Premiere Pro


jeff92k7 wrote on 2/24/2015, 9:18 AM
Thought I would post back. I've been working on a project the last few days and haven't had any crashes in Vegas Pro 11 at all. It's been weird. So I got to thinking about what is different and I realized that I hadn't loaded any 3rd party audio plugins in this project. Plugins is one area that I have noticed a lot of crashes. So I'm wondering now if a big part of my crashing is the way Vegas handles plugins.

I can always, always force a crash by trying to add certain 64 bit audio plugins. Because of that, I have resorted to using all 32 bit vst plugins. However, I have other 64 bit plugins that work fine, even though I don't load them because I don't want to confuse Vegas further by mixing plugin types.

So does Vegas prefer 32 bit plugins in general? Is there something wrong with mixing 32 and 64 bit plugins in Vegas?
John222 wrote on 2/24/2015, 7:05 PM
I've been running Vegas pro 11 64 bit with Win 8.1 without any problems. But other than Vegasaur and deshaker, I don't have anything else installed within Vegas. All my other stuff is independant packages like Mocha Pro, Fusion and Hitfilm 2 Ultimate.
VidMus wrote on 2/24/2015, 7:49 PM
I recently upgraded to windows 8.1 from Window 7 Ultimate. I was occasionally having strange crashes with Vegas and Windows.

The problem turned out to be the latest version of GPU-Z. I set it not to run on start-up and not at all and now the system and Vegas is 100% stable.

Problem with Vegas was a not responding message after x amount of time and edits, etc.. Windows 8.1 would boot up with no icons and not even the metro. I had to click on the lower left to get it to jump in.

Somebody at TechPowerUp blew it big time!

There are a lot of things that can trip-up a system. This one was a bit on the obvious side and was easy to fix. There are more details that helped me figure it out, but I am too tired to type them all right now.