Paul Miller

Well, this is interesting! It pretty much handles everything we have been discussing recently regarding Metadata as well. Anyone else want to take a look and comment?

One key design difference I see is this API requires loaders to "create" properties, where the new proposal is inteded to be merely a wrapper around potentially-lazily-evaluated metadata. It would...

OK I didn't see you had added an Action. That's an interesting approach. I encourage others to chime in.

Alexandre's implementation seems pretty robust, but for what we're trying to achieve in terms of simplicity I propose we go forward with my proposal for now. Would like to hear...

I have this so far: ``` typedef enum OfxPropDataType { kOfxPropDataTypeNone = 0, kOfxPropDataTypePropSet, kOfxPropDataTypePointer, kOfxPropDataTypeBytes, kOfxPropDataTypeString, kOfxPropDataTypeDouble, kOfxPropDataTypeInteger, kOfxPropDataTypeBoolean } OfxPropDataType; ``` Proposed new methods in OfxPropertySuiteV2: ``` OfxStatus...

Some OFX hosts don't have the concept of a parameter "slot" for an input (they just use input noodles or what-not), so I assume it's ok to ignore this parameter...

Dennis- Yeah I do remember that, and I don't know either whether that was implemented in Vegas. But Vegas was the first host I thought of where this would make...

Yes. For example, if you have a Session in Silhouette that starts at frame 1001, and you launch the Mocha Pro OFX UI, it shows the frame range starting at...

This could probably be done with the Timeline suite. I thought adding a property is less "heavy" than adding a function to a suite. Would be good to discuss.

I don't think there is a need for kOfxImageClipPropDisplayOffset as this can be implemented as part of the Timeline suite