Is MAGIX going to release a development kit for Vegas effects?

jonny-w wrote on 9/23/2017, 9:47 PM

I'm pretty sure Sony released an SDK for visual effect development previously. I was wondering if anyone at MAGIX could answer whether or not Vegas 15 was going to have the same. I know that you can create scripts but they're not as useful to me as creating effects. And no, I don't mean presets or extensions. I mean video effects, like in NewBlue.

After Effects has an SDK.

Comments

TheHappyFriar wrote on 9/24/2017, 7:23 AM

No need, OFX is a public API so you can start w/o anything from Magix: https://en.wikipedia.org/wiki/OpenFX_(API)

Sony/SCS did release SDK's for their stuff years ago but OFX kind of makes that pointless now.

jonny-w wrote on 9/24/2017, 2:00 PM

No need, OFX is a public API so you can start w/o anything from Magix: https://en.wikipedia.org/wiki/OpenFX_(API)

Sony/SCS did release SDK's for their stuff years ago but OFX kind of makes that pointless now.

But OpenFX is bad

TheHappyFriar wrote on 9/24/2017, 4:12 PM

NewBlue integrates in to Vegas via OFX.

What's your reasoning OFX is any worse then the old SF/SCS SDK?

NormanPCN wrote on 9/24/2017, 5:10 PM

OpenFX is pretty commonly used. Vegas, Blackmagic Resolve/fusion, Nuke, Edius

 

set wrote on 9/24/2017, 5:34 PM

Even the great FXs: GenArts Sapphire, are also OFX.

NormanPCN wrote on 9/24/2017, 7:39 PM

Even the great FXs: GenArts Sapphire, are also OFX.

Yes, but Sapphire supplies their effects in many plug-in formats. Like Adobe proprietary. OpenFX does not work with Adobe.

Largely, OpenFX, Adobe proprietary and Avid proprietary are the plug-in formats a plug-in vendor has to worry about supporting.

TheHappyFriar wrote on 9/24/2017, 9:14 PM

Adobe sets standards & is big enough to say how you play ball with them.

I understand standards formats can not always be the best (DirectX is Windows only, Quicktime doesn't play well with non-apple products, etc) but I still want to know why he would rather have another SDK for Vegas.

Could very well be the old SDK will run just fine in Vegas 14/15, maybe with a little tweaking.

jonny-w wrote on 9/25/2017, 1:20 AM

Adobe sets standards & is big enough to say how you play ball with them.

I understand standards formats can not always be the best (DirectX is Windows only, Quicktime doesn't play well with non-apple products, etc) but I still want to know why he would rather have another SDK for Vegas.

Could very well be the old SDK will run just fine in Vegas 14/15, maybe with a little tweaking.

OpenFX is very faulty despite how many popular editors shill it. It's bloated and lags a lot. I can't tell you how many times Vegas has crashed due to issues with the API.

It's also unintuitive. Releasing an SDK would give users more control over custom effects and whatnot and their integration into Vegas because it would be better suited to do so. I like the idea of having this one sort of API that could be used cross platform with most editors but I always think it's a good idea to tweak the source to make it more optimized for the program you're using. It just makes sense

Peter_P wrote on 9/25/2017, 3:21 AM
Could very well be the old SDK will run just fine in Vegas 14/15, maybe with a little tweaking.

It does. At least the OFXs I wrote using the old SDK are running in Vp14/15 without any change.

TheHappyFriar wrote on 9/25/2017, 7:51 AM

It does. At least the OFXs I wrote using the old SDK are running in Vp14/15 without any change.

SF/SCS released a SDK for writing non-OFX, DirectX, plugins.

I always think it's a good idea to tweak the source to make it more optimized for the program you're using. It just makes sense

OFX is source based. I have the C++ code on my computer. Searching online about the SDK (Magix doesn't have it any more from the looks of it) it was DX based, could only work on video events frame by frame, where as the OFX plugins can't manipulate the image specifically but can do manipulations across time. The OFX plugins reminds me of the limits of GPU shaders.

I should have the old SDK on DVD somewhere.

VEGASDerek wrote on 9/25/2017, 8:38 AM

OFX is the way to create custom effects to be used in Vegas. While some of our effects are still using a legacy DX framework, we intent to have everything converted over to OFX in the future.

jonny-w wrote on 9/27/2017, 8:16 PM

Well, I guess my question has been answered, but I'd still love to have a debate about the pros and cons of OFX as well as using OpenGL in Vegas :/ I'm sure I'm not the only one who finds the whole thing hard to handle? There's a reason you never really see any custom effects out there besides from big companies like NewBlue and Boris - who pay people to make them.

TheHappyFriar wrote on 9/27/2017, 8:38 PM

DX (or OGL) plugins have limits just like OFX does, just different ones.

There's lots of FX out there but for dedicated FX packages like Boris, After Effects, etc. To me, Vegas letting me do that stuff is a huge bonus.

BTW, I normally use Blender for my FX program. Still on 2.49b because that's the one I know.