Paul Miller
Paul Miller
This might be better as **kOfxImageClipPropDisplayTimeOffset**
On 10/20/19 4:48 PM, GaryO wrote: > * This is in frames, not seconds, correct? > Yes. Same units and format as *kOfxPropTime*. > > * Should it always be...
As per list discussion perhaps this should get rolled into the updated timeline suite.
Could we take advantage of the current set of properties? What if the host sets kOfxImageEffectPropPreMultiplication on the output clip to specify its desired premul output. The plugin can read...
I'm in favor of either adding a unique instance ID property to the effect that can be used as a hash, OR introduce a new integer parameter hint that indicates...
Right - each effect "instance" would get its own ID. I'm sure many (all) hosts already have some kind of identifier or GUID for each instance. It would just be...
It's worth pointing out the Alembic file format camera is defined by these properties: - Focal Length - H/V Aperture - H/V Film Offset - Lens Squeeze (aspect) - Overscan...
Looks well-defined to me.
I've run into something like this before, where we had an old node that did task X, but it was replaced by a different node that handled task X in...
I guess my point is I don't think it's up to the host to enforce this. If I find an obsolete plugin and the new, non-obsolete one "didn't get installed...