Vegas Pro 14 &15 Hangs On Start When Loading Plugins

Bart_Santello wrote on 2/22/2018, 12:47 AM

Both versions of Vegas Pro 14 & 15 will not launch (software up-to-date) hangs when loading VST Plugins in Windows 10. In particular program hangs at WAVESHELL1-VST 9.92.DLL This problem dates back years. This type of crash is UNACCEPTABLE in a professional software. The program is thus useless to me if I can't launch. Magix-Vegas team: "Where's the fix?!"

 

Comments

NickHope wrote on 2/22/2018, 1:19 AM

I've read of performance problems with WAVES plugins, but I don't remember reading of them preventing startup. Have you reported it?

Which WAVES plugins do you have?

How is your Options > Preferences > VST Effects configured?

Grazie wrote on 2/22/2018, 1:28 AM

Both versions of Vegas Pro 14 & 15 will not launch . . . This problem dates back years. This type of crash is UNACCEPTABLE in a professional software. The program is thus useless to me if I can't launch. Magix-Vegas team: "Where's the fix?!"

Well, this is your first post? Yes? So I can't get to view your previous posting history on this. Maybe you could try reinstalling those VSTs over a fresh install of either VP14 or VP15. Then rescan for ALL VST. Do you know if those VSTs are compatible with V14/15? Waves plugs need care and attention 😉. I have a few and they are working in VP 14/15

I'm assuming you've also tried them in VP13 and before, and have they launched?

Trying to help here.

Barton-Santello wrote on 2/22/2018, 8:54 AM

I've read of performance problems with WAVES plugins, but I don't remember reading of them preventing startup. Have you reported it?

Which WAVES plugins do you have?

How is your Options > Preferences > VST Effects configured?

Hi Nick. I'm the same person in the original post but different login. I have WAVES Scheps Omni Panel and Scheps 73. With regards to VST 'Preferences' in Vegas settings, I didn't know because the program simply won't load. I will submit an 'official' tech support ticket, but if you search this problem on Google, it's been an issue for years. The bottom line is that a program should not be held-up from starting because of a third party plug-in. The work around should be NOT to load the plug-in's on start, but wait until the program opens where - like you suggested - preferences can be adjusted. I have a DAW that when scanning plug-ins, if it has a conflict, it will ask to 'discard' that particular plug-in, so the program can continue to load other plug-ins that are compatible.

The bottom-line is that I have been unable to use both Vegas Pro 14 & 15. I purchased both program versions because I really wanted to get back into Vegas (the last workable version for me was Vegas Pro 11). I keep hoping that with each update this issue and other crash issues would be fixed. In the meantime I've been using Magix's Video Pro X.

 

Barton-Santello wrote on 2/22/2018, 9:10 AM

Both versions of Vegas Pro 14 & 15 will not launch . . . This problem dates back years. This type of crash is UNACCEPTABLE in a professional software. The program is thus useless to me if I can't launch. Magix-Vegas team: "Where's the fix?!"

Well, this is your first post? Yes? So I can't get to view your previous posting history on this. Maybe you could try reinstalling those VSTs over a fresh install of either VP14 or VP15. Then rescan for ALL VST. Do you know if those VSTs are compatible with V14/15? Waves plugs need care and attention 😉. I have a few and they are working in VP 14/15

I'm assuming you've also tried them in VP13 and before, and have they launched?

Trying to help here.

Hello Grazie. I like your idea, but or me to uninstall my plug-in's and reinstall would be a Herculean task. I would have to screw-around with license-activations, which would mean emails to WAVES support, so they could reset my plug-in license activations, etc. And what happens if I uninstall, then come to find that VEGAS hang's up on some other vendor's plug-in and I end up playing whack-a-mole with various plug-ins.

These plug-is work in my DAW's, so it's not a faulty plug-in. Why should I have to jump through these hoops in the firs place?

Also, see my reply post to Nick in this thread. I purchased version 14 and it crashed all the time, so I just went back to my other editor Magix Video Pro X. When version 15 came out I wanted to support the VEGAS platform and give that version a go. And now I can't even launch the program.

The bottom-line is I should not have THIS type of issue in a professional video-editing program.

Marco. wrote on 2/22/2018, 9:25 AM

Unfortunately it's true since many years the Vegas Pro Read Me list "certain" Waves 5.2 plug-ins to cause stability problems. While it is recommended to deselect "Track Buffer" in Options/Preferences/Audio Device, this would need Vegas Pro to be already started fine. Also I doubt this would help when the problem occurs by simply loading the plug-ins, it is more about using them in the project later.

Looking for a way to bypass them for the Vegas start-up in another way than moving the plug-ins to a different folder …

NickHope wrote on 2/22/2018, 9:50 AM

In my opinion the usual advice in part #6 of this post still applies here. There should be no need to uninstall anything. Just move all the files out of C:\Program Files (x86)\Vstplugins and C:\Program Files\Vstplugins, so that you can get Vegas running. Then go into your VST preferences and get control of those settings. My recommendation is to have only C:\Program Files\Vstplugins in your preferences as the default VST search folder. Keep C:\Program Files (x86)\Vstplugins out of it completely. Leave the "Alternate" folder field empty.

Then move your WaveShell files back in to their respective folders and restart Vegas. Then move the individual WAVES plugins in one by one, restarting each time until you find exactly which one causes the problem. But you might find that the problem is cured simply by doing what I said above.

If you have old 32-bit only VSTs then I recommend you put them in a sub-folder of C:\Program Files\Vstplugins, where Vegas will still find them. That should not include WAVES plugins, which I think should all be available as 64-bit.

Grazie wrote on 2/22/2018, 10:21 AM

@Bart_Santello I can’t agree more with your reply. You are spot-on. And it’s members/users like you who will, hopefully, keep the programmers at the task of keeping VP pro and honest.

No software is complete. It’s always a work in progress. Does nothing for my blood pressure. I’m still haunted by the dreaded crash on exit. This latest build is holding the line - I think 🤔 ?

sonicvision wrote on 9/23/2018, 5:38 PM

Going through this now. So frustrating, and you are absolutely correct, Barton-Santello, this is not acceptable in modern software. What makes it more bizarre for me is Vegas 14 I have plugins working but in 15 I had to remove pointing to folder. If it could just be smart enough, as you say, skip the troublesome ones, that would be great. I need to have a good bunch of my audio plugins in Vegas but am not going to create a new folder of duplicates to get ones to work in VP15.

gurksky wrote on 9/12/2020, 6:02 PM

Here's a fix that worked for me a couple of hours ago.

Vegas Pro 15 failed to launch. It chewed for a while on Softube's Amp Room VST plugin and then just died, repeatedly.

After renaming the VstPlugins directory under "C:\Program Files" Vegas Pro 15 completed its launch. While it ran, I reversed the directory name change, opened Vegas' preferences, "VST Effects" tab, where the original directory name was (still/already) stated, and hit "Refresh". This time, Amp Room was properly digested, along with everything else.

Since then, Vegas Pro 15 launches smoothly, with my VST ecosystem unaltered.

I think I mixed NickHope's approach (see above) with my typical laziness and had some not-so-typical luck. I had no opportunity to succeed with anything else in Vegas Pro 15, so if have no idea whether I'm fully operational now. I don't know if this works under other circumstances. I also don't know if this is common knowledge by now. I wasn't able to recognize this in anything I googled, so I thought I might just post it.