kOfxPluginPropFilePath not being reported correctly by Vegas

Charles_uk wrote on 6/9/2022, 10:39 AM

Vegas is not correctly reporting the kOfxPluginPropFilePath property.

It reports the actual location of the <mypluginname>.ofx loadable library file instead of the <mypluginname>.ofx.bundle location.

So now I have to do some special coding in the plugin just for Vegas or else detect this error in the naming!

<SIGH>

Could this be fixed?

Anyone else seeing this?

Comments

Musicvid wrote on 6/9/2022, 10:54 AM

Since Vegas does not report this problem with other third-party plugin libraries, you may want to take this up with that vendor's developers. Frankly I have never heard of kofx.

Vegas does not purport or claim to support "nonpartnered" effects packages, although some vendors have tested their products with Vegas.

Charles_uk wrote on 6/9/2022, 10:58 AM

Thank you for that. Will be doing so. Have just done a test and the OFX host implementation looks a bit troublesome by the looks of it. Just getting my head around how Vegas is handling the OFX standard. I am still searching for docs at the moment.

Thank you again for your fast reply!

Musicvid wrote on 6/9/2022, 12:10 PM

Where did you get your plugins? I can't find them on the internet.

Charles_uk wrote on 6/9/2022, 3:10 PM

I am writing a plugin and have already got it going on other platforms. Not quite ready to release yet but almost there. Will reply here when ready - which is Real Soon Now. There are also test plugins for OFX one can build that come with the API files.

Musicvid wrote on 6/9/2022, 3:31 PM

There is a scripting forum here and the older SDKs are still available.

jetdv wrote on 6/10/2022, 7:08 AM

Writing OFX plugins isn't the same as scripting. I did a quick search and couldn't find the OFX information anymore on the website. I thought there used to be OFX information there.