Vegas POST, Vegas Effects does not start.

diLuciana-Marcis wrote on 11/12/2019, 5:04 AM

Hi, I just bought VEGAS POST suite. ๐Ÿ™‚
I have carefully followed the installation and activation instructions: ๐Ÿ‘€
Vegas Pro 17 (OK) ๐Ÿ‘
Vegas Effects (OK) ๐Ÿ‘
Vegas Image (Not Required ?)

Unfortunately, Vegas Effects does not start. ๐Ÿ˜•

ย 

ย 


It was successfully activated by starting Vegas Pro, right click on timeline -> edit in vegas effects, but at this point see the Vegas Effects startup logo, but immediately after that the software window closes and does not even appear in the activity management list ...๐Ÿ˜Ÿ

I tried to restart the computer, but the problem remains. ๐Ÿ˜•
The system: I7 8850 - 32GB - NVIDIA QUADRO p3200 6GB - WIN10 64 ๐Ÿ’ป

Please help!

ย 

Comments

set wrote on 11/12/2019, 7:20 AM

Do you have additional OFX installed?

If so, try moving them temporarily and see if it helps

ย 

Go to C:\Program Files\Common Files\OFX

Move the content to, perhaps like C:\Program Files\Common Files\OFX off

ย 

diLuciana-Marcis wrote on 11/12/2019, 8:51 AM

yes, I had HitFilm express installed, of course I removed it before writing the post.

before asking for help I usually try them all ....

By the way, it is quite strange that the folder in which VEGAS EFFECTS is installed is the same as HITFILM: "/ FXHOME"

diLuciana-Marcis wrote on 11/12/2019, 9:04 AM

yes, I had HitFilm express installed, of course I removed it before writing the post.

before asking for help I usually try them all ....

By the way, it is quite strange that the folder in which VEGAS EFFECTS is installed is the same as HITFILM: "/ FXHOME"

In the folder \Program Files\Common Files\OFX, however, there were 3 plugins:
HitFilmVegasBasic.ofx.bundle (removed along with HitFilm)

but they still existed:
BCC_OFX_3DObjects.ofx.bundle
is
BCC11_OFX.ofx.bundle
I tried to remove them individually, and going by exclusion it seems that the problem is due to the presence of BCC11_OFX.ofx.bundle
in fact removing this folder now VEGAS EFFECTS starts correctly.
Thanks ๐Ÿ˜Š

alextudm95 wrote on 11/12/2019, 9:19 AM

Hi, I just bought VEGAS POST suite. ๐Ÿ™‚
I have carefully followed the installation and activation instructions: ๐Ÿ‘€
Vegas Pro 17 (OK) ๐Ÿ‘
Vegas Effects (OK) ๐Ÿ‘
Vegas Image (Not Required ?)

Unfortunately, Vegas Effects does not start. ๐Ÿ˜•

ย 

ย 


It was successfully activated by starting Vegas Pro, right click on timeline -> edit in vegas effects, but at this point see the Vegas Effects startup logo, but immediately after that the software window closes and does not even appear in the activity management list ...๐Ÿ˜Ÿ

I tried to restart the computer, but the problem remains. ๐Ÿ˜•
The system: I7 8850 - 32GB - NVIDIA QUADRO p3200 6GB - WIN10 64 ๐Ÿ’ป

Please help!

ย 

I have the same problem. Contacted Magix but still unable to resolve the error. But they did said "repair each installation of C++ redists" which is Im not so sure how

alextudm95 wrote on 11/12/2019, 9:19 AM

Do you have additional OFX installed?

If so, try moving them temporarily and see if it helps

ย 

Go to C:\Program Files\Common Files\OFX

Move the content to, perhaps like C:\Program Files\Common Files\OFX off

ย 

Done this, still wont load up

fr0sty wrote on 11/12/2019, 10:04 AM

I'm in the same boat, and I already had to repair my C++ redists to get Vegas working very recently (had to uninstall it, then it wouldn't re-install until I did all that). I'm looking forward to trying this software out!

diLuciana-Marcis wrote on 11/12/2019, 1:16 PM

are you talking about the same version? VEGA POST?
What exactly does not start?
Vegas Pro (version 17?)
Vegas Effects?

[...] A common solution there was to make sure there are no issues with C++ redistributable packages from Microsoft.

Start > Control Panel > Programs > Programs and Features.

Once the list of installed apps is populated, use the search box in the top right to search for "Redistributable"

Find the latest version of each redistributable, for both x86 and x64

Select Microsoft C++ Redistributable, right-click and click on Change.

On Microsoft C++ Redistributable Setup, click on Repair.

Click on Close once setup is successful.

repeat for all - I'm not actually sure which versions Acid Pro 8 uses, but my system had updates for 2012, 2013, and 2017 installed on the same day as I installed Acid Pro 8, so start with those.

reboot

try installing again [...]

Then repair installation of VEGAS and restart Windows

set wrote on 11/12/2019, 4:15 PM

I'm in the same boat, and I already had to repair my C++ redists to get Vegas working very recently (had to uninstall it, then it wouldn't re-install until I did all that). I'm looking forward to trying this software out!

errr... so... the steps is:

  1. uninstall any Vegas Pro / Vegas Post
  2. install overwrite the new C++ redists
  3. restart Windows
  4. reinstall Vegas Pro & Vegas Post ?

ย 

diLuciana-Marcis wrote on 11/13/2019, 6:48 AM

Maybe I was luckier, there were no problems with MS C ++ REDIST.
it was enough to delete (or rename) the BORISFX folder BCC11_OFX.ofx.bundle into main folder \Program Files\Common Files\OFX. no additional software editing / installation was required

ย 

erkki-halkka wrote on 11/18/2019, 12:03 AM

I had the same issue - and cleaning up the OFX folder worked for me too.

Deleting BCC11_OFX.ofx was not enough though, there was still something else that was crashing Vegas Effects in my OFX folder. Clearing everything except Neat Video worked. I didn't go through the trouble to isolate the specific offending plugin.

alextudm95 wrote on 11/18/2019, 8:33 AM

Do you have additional OFX installed?

If so, try moving them temporarily and see if it helps

ย 

Go to C:\Program Files\Common Files\OFX

Move the content to, perhaps like C:\Program Files\Common Files\OFX off

ย 

Oh damn this does fix the crashing error. But the problem now plugin inside VEGAS Pro also is disable. Anyway to separate it?

fr0sty wrote on 11/18/2019, 11:30 AM

An update will be required either to Vegas Effects or to the plugins causing the issue, most likely. The above did fix my problem as well, with NewBlue being the offending plugin folder.

Now I'm rendering a 30 second animation using atomic particles... it's been rendering since last night and it's still only half way done. Definitely slower than After Effects doing the same task, though the plugin suite needed to make After Effects do what Atomic Particles does costs an additional $1000, so, I'll take it.