On Mon, Apr 8, 2013 at 10:31 AM, Paul Griswold <[email protected]> wrote: > Wouldn't the solution be to update the FXTree so it can use OFX plugins? > > That opens a lot of doors
We could have done that; the last time we looked at the OFX API (I was involved in its early definition) OFX plug-ins were very expensive, so nobody would have bought one for the fxtree. OFX vs AE APIs allows plug-ins vendors to set different prices for Studio vs prosumer. Now in 2013, it's too late to bother putting work on that, xsi clients are using other compositors already. Note that Composite/Toxik... again... you know what's coming... wait for it... . . . supports OFX plug-in. It does everything except have a modern UI, that thing.
