Accessing non OFX Effects vis scripting

nonam3 wrote on 3/30/2025, 5:35 AM

Hello,

I run into issue accessing Effect parameters for non OFX effects.
Strangely even simple "Effect.IsOFX" throws an exception:

System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
   at ScriptPortal.Vegas.IOFXPlugCOM.GetUniqueID(String& val)
   at ScriptPortal.Vegas.Effect.get_OFXEffect()

So my question is: is it possible to access non OFX Effects parameters from script?

@jetdv Probably You know an answer to that question :).

Thanks in advance for answer best regards

EDIT: from quick look at API it seams like this is not possible as there is no parameters for non OFX Effects...

Comments

zzzzzz9125 wrote on 3/30/2025, 5:53 AM

Strangely even simple "Effect.IsOFX" throws an exception:

System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
   at ScriptPortal.Vegas.IOFXPlugCOM.GetUniqueID(String& val)
   at ScriptPortal.Vegas.Effect.get_OFXEffect()

See: https://www.vegascreativesoftware.info/us/forum/bug-in-effect-isofx-when-an-effect-is-not-an-ofx--146784/#ca921860

 

For non-OFX effects, you can only save presets for them in advance. After that, you can use presets on them (or on their keyframes). However, you can also add new keyframes between their two existing FX keyframes as keyframe interpolation.

In short, you can't directly get or modify parameter values for non-OFX effects like you can for OFX effects.

Last changed by zzzzzz9125 on 3/30/2025, 5:55 AM, changed a total of 1 times.

Using VEGAS Pro 22 build 248 & VEGAS Pro 21 build 208.

Information about my PC:
Brand Name: HP VICTUS Laptop
System: Windows 11.0 (64-bit) 10.00.22631
CPU: 12th Gen Intel(R) Core(TM) i7-12700H
GPU: NVIDIA GeForce RTX 3050 Laptop GPU
GPU Driver: NVIDIA Studio Driver 560.70

nonam3 wrote on 3/30/2025, 6:03 AM

Thank You for the info.

That's a bummer ;/

IMHO This should be unified for all Effects either to OFX API or by exposing internal non OFX compliance one.

The deeper You go into Vegas the more these dark corners surface and that's a shame, because I don't see an alternative for quick video editing (and yes I tried AE, Premiere, Davinci and all are not suitable for my needs, to "slow" and I'm on 4090 + 14900K).

To me it seams like these core functionality level features are freeze on Sony code base and no improvement has been made ;/

 

jetdv wrote on 3/30/2025, 7:56 AM

OFX added the ability to reference specific parameters via scripting and have each parameter have separate keyframes. Previous to that, the only way is to select presets. It's definitely much better to use OFX effects than the older DirectX effects because you have much better control.