Paul Miller

This needs further discussion. I believe Pierre's example is he wants to do some analysis which then sets some keyframes, and instead of getting the default host linear or smooth...

How about something like this? ``` enum OfxParamInterpType { kOfxParamInterpTypeConstantStep, // hold until next key kOfxParamInterpTypeLinear, // linear kOfxParamInterpTypeSmooth, // some type of smooth curve kOfxParamInterpTypeCustom // get-only, since this...

Proposed new API: ``` typedef enum OfxParamPropInterp { kOfxParamPropInterpConstant, kOfxParamPropInterpLinear, kOfxParamPropInterpSmooth } OfxParamPropInterp; OfxStatus (*paramGetInterp)(OfxParamHandle paramHandle, OfxTime time, OfxParamPropInterp interp); OfxStatus (*paramSetInterp)(OfxParamHandle paramHandle, OfxTime time, OfxParamPropInterp *interp); ```

On 2/27/18 10:10 AM, GaryO wrote: > > @fxtech (Paul), any opinions on this? > > To flesh out Pierre's suggestion: > > * A new function, probably in a...

On 2/27/18 3:47 PM, GaryO wrote: > > Host vendors: what are you doing now about those functions Pierre > mentions? Returning errors? Could you create a list of functions...

interactSwapBuffers probably isn't needed at all. I'm guessing an interact update is all part of some existing double-buffered update/display cycle that the plugin would have no control over anyway. That's...

Some thoughts on this: 1. This API should be contained entirely in a new file: ofxMetadata.h 2. It would be useful for metadata to be available at the Clip and...

Some standard metadata: - media file path (as a URL) - source frame number - source timecode (OTIO uses HH:MM:SS;FRAME or HH:MM:SS.MS) Vendor-specific metadata keys should be prefixed with the...

We agreed that metadata property keys should be prefixed with 'where it came from', and define a common set with the ofx prefix.

In order to support "unknown/binary blob" types of metadata we should add a try "raw data" type to PropertSet and while we're at it, parameter support. I'll work up a...