andyprobst wrote:What is the concept of ofx when it works in one app but not good in the other?
Ofx api describes a plugin interface that host softwares can implement. It means that an ofx plugin has standardised access methods for exchanging parameters and data, so host supplies input data and params, plugin does its thing and gives results back. But host has no control over how exactly plugin itself is doing its stuff.
Resolve is somewhat special case because it heavily relies on gpu processing. If plugin has only cpu processing path, this means doing a device>host copy, plugin does work, host>device copy. In softwares where processing engine is mainly relying on cpu paths it can be faster. And there are lots of ways how to “do effects” so it isn’t as simple as “gpu good mkay” and “cpu slow yes”, processing engines are built with assumptions about needs of workflow etc and with these assumptions come specific constraints.