Vegas Effects opens then closes

Marco. wrote on 8/10/2020, 11:22 AM

Which version of Vegas Effects is this?

John-Andrus wrote on 8/10/2020, 11:30 AM

It was the newest version that came with Vegas Post Suite, that was released last week I believe. Please excuse my ignorance. New to the forums.

set wrote on 8/10/2020, 11:32 AM

Probably OFX incompatibility

John-Andrus wrote on 8/10/2020, 11:43 AM

Please correct me if I'm wrong, but OFX is OpenFX? Is that something that I can correct on my own?

set wrote on 8/10/2020, 5:11 PM

Yes, OpenFX

The Plug-in is located in 'C:\Program Files\Common Files\OFX'

Now, you can move it to temporarily, say to 'C:\Program Files\Common Files\OFX off' ~ This is just an out of made-folder, so you can move it back.

Or, if you wish to only able to use it on Vegas Pro 18 environment, you can move it to 'C:\Program Files\VEGAS\VEGAS Pro 18.0\OFX Video Plug-Ins'

John-Andrus wrote on 8/12/2020, 9:54 AM

Thank you! I will try this AS SOON AS I get off work!

Jack S wrote on 8/12/2020, 2:45 PM

@set Aren't these Vegas Pro 18's own plug-ins? What would happen in VP18 if these weren't available?
I've been struggling to get Effects 2 activated and have scoured all the folders looking for and renaming those containing 3rd party plug-ins. I never thought to disable VP18's own plug-ins.

set wrote on 8/12/2020, 5:08 PM

@Jack S, you are not removing or modifying any of included effects that are placed in Vegas Pro's 'internal OFX folder, but rather just adding the 3rd party OFX that supposed to be placed on Common Files\OFX.

By doing this, it will prevent Vegas Effects 2 (or other application that also using OFX) on reading the Common Files\OFX.

I have other editor that also trouble on reading some of the OFX (crashing that application, and the next time restarting that, I have a notice that OFX needs to be disabled - including that application's internal OFXs)

Jack S wrote on 8/12/2020, 5:31 PM

@set I'm finding it difficult to get my brain around this. Are you saying that I should try disabling all the plug-ins in the 'Program Files/Common Files/OFX/Plugins' directory? I'm sure that I've tried that some time ago without success. I renamed every folder under this folder with the word 'old' at the end.

If this is what you mean I'll have a go again.

set wrote on 8/12/2020, 5:36 PM

instead of renaming 'old', I move it out from 'C:\Program Files\Common Files\OFX' to self-made folder 'C:\Program Files\Common Files\OFX off', I assume this will totally disconnecting it from system.

I personally never tried just renaming the subfolders.

Ken-Cox wrote on 8/12/2020, 7:20 PM

This worked perfectly! Thanks!!

instead of renaming 'old', I move it out from 'C:\Program Files\Common Files\OFX' to self-made folder 'C:\Program Files\Common Files\OFX off', I assume this will totally disconnecting it from system.

I personally never tried just renaming the subfolders.

Jack S wrote on 8/13/2020, 4:31 AM

@set Thanks for that. I did exactly what you suggested and it worked, Effects now opens normally. Now I have to re-introduce each plug-in one at a time to see which is the offending one.
I personally never tried just renaming the subfolders. You were absolutely correct with that statement.
Thanks again.

set wrote on 8/13/2020, 5:01 AM

glad to hear @Jack S.

Let us know which OFX that is conflicting with VE2.

As said above, if you want the OFX to be able to be used only in Vegas Pro environment, then move it to 'C:\Program Files\VEGAS\VEGAS Pro 18.0\OFX Video Plug-Ins'

Jack S wrote on 8/13/2020, 5:49 AM

@set It was the NewBlue TotalFX 360 pack. I haven't checked out which of the sub-packs in this pack was causing the conflict, I'm just glad you solved the problem for me. Maybe I'll do a little more investigating to see which of the elements in this pack was the culprit. Meanwhile I've done as you suggested and copied them into the respective 'OFX Video Plug-ins' folders for the other Vegas applications.
Things are looking good now, thanks a lot.