Comments

Grazie wrote on 12/7/2018, 12:50 PM

I've bought Vegas Pro 16.0 today. But I can't run it. The application shuts down when it is initializing the plugin factory.

Any idea.

@JeanPierre-Lugarini - Have you registered it yet? What's the Build number?

JeanPierre-Lugarini wrote on 12/7/2018, 1:07 PM

Sure, the application has been registered. It is the version 16.0.0.307. Since my last post, I have removed some plugins but nothing change. The application shuts down in the initializing phase. I have tried to re-install it 3 times.

NickHope wrote on 12/7/2018, 10:46 PM

There are some troubleshooting suggestions in this post: https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/

JeanPierre-Lugarini wrote on 12/8/2018, 4:10 AM

Hello

Thanks Nick. The problem is solved. It was the SeMW Extensions which cause the crash. However, it is running with the version 15.0.

 

karma17 wrote on 12/9/2018, 12:03 AM

Is SeMW not quite ready for V16?

NickHope wrote on 12/9/2018, 12:26 AM

Is SeMW not quite ready for V16?

I don't had a problem with version 1.0.11.0 in VP16.

@JeanPierre-Lugarini Which version of SeMW Extensions are you running? Can you isolate which of its extensions is causing the problem, by enabling/disabling them in Tools>Extensions>SeMW Extensions?

Unfortunately the SeMW site is down for me at the moment. Tagging the developer: @Satevis

Satevis wrote on 12/9/2018, 3:44 AM

Thanks for the tag, Nick. The site's server seems to not currently reply to ordinary http requests. https should work, though: https://www.semw-software.com.

I'm not aware of any major problems with V16 such as a crash during startup. I have V16 installed and the extensions work fine for me (Version 1.0.11 as well). There's that issue with the render progress bar being wrong mentioned in another thread (not necessarily related to V16). I haven't quite figured out yet when that occurs or what's causing it.

JeanPierre-Lugarini wrote on 12/9/2018, 8:59 AM

In fact, it was the autolevel module from SeMW which was using. I did'nt try to reinstall it.