Desired Premult

9 views

Skip to first unread message

PierreJasmin_REVisionEffects

unread,

May 14, 2020, 12:23:42 PM5/14/20

to ofx-discussion

We have a #PR 62 for Desired Premult property with 2 members approving but not a plug-in and an host.
Not surprising because at this point we know all the hosts that are members and have build over time per known host response...

As per motion adopted in our AGM in april and now in 30 days review (closing next week) before we officially add it to WIKI at github as protocol, we will now be able to use a non-member contribution to complete approval process (still with 2 members approval) for the plugin and host from a different code source branch test needed.

This property is sort of benign but was part of our 3 items list to start tagging OFX as v1.5 (ofxSetHost action is already in now). And would like to close this cycle.

Our application here is when the input is Opaque, and the plugin can render a non-full alpha, we add at end of plugin a boolean checkbox that when we know we set at parameter creation so users don't have to always set that.

Looks like this here:

   bool isHostPremult()
    {
        if (mHost->isToxik() || mHost->isSilhouette()) return false; // we understand toxik does not exist anymore, this code is old :)
        else return true;
    }

Looking at this, has me asking for example, for example Flame added OpenFX support last yer, when an OpenFX plugin in Flame are we expecting to return premulted or straight images? I don't think we ever reverse engineered that here.

Any volunteer host?
Testing is real simple, based on what you report, a boolean checkbox will be ON or OFF depending on what you report