I am starting to worry about OSC. It is not an official way of doing things and more of a workaround or hack. So my worry is that if filter or code changes in the future will OSC continue to work as intended? Hacks are great, but as I have learned, they are not always future proof.
I have just started to take a look at OSCs as I found some plugins I have been using fascinating with nice controls exposed in FCPX for easy manipulation...
Agreed with the FxPlug path, that’s the holy grail of unlocking all the underlying power that FCPX/Motion have to offer, including the Metal API... however this is advanced stuff.
Regarding your published OSCs question, if Apple decides one day to get rid of some of the filters/features I think it would not matter? I mean, as it is right now even when using a filter in a project it keeps the old instance, if the controller or effects gets updated it needs to be dragged again on the clip and that effect is pretty much baked, nothing outside would be able to change it barring saving back again the Title/Effect motion file?
I say this because, personally, even if one day I manage to get all the knowledge that be regarding FxPlug, I think I would still create some proxy filters that just expose parameters and widgets of all sorts (but do nothing themselves on images) whose sole purpose is to be dragged on a group and be linked via parameters behaviors to other graphics targets..