Paul Miller
Paul Miller
We should add a list of predefined colorspace "roles" that match up with OCIO roles tha provide generic names such as "linear", "srgb", "data".
We should probably set up another meeting to hash out the OCIO spaces/roles vs "generic" spaces/roles thing.
I prefer Alexandre's term of "Bytes" instead of "BinaryData"
For Bytes *parameters*, we can avoid adding to or changing the API by doing it like this. Any comments? ``` #define kOfxParamTypeBytes "OfxParamTypeBytes" typedef struct OfxBytes { const uint8_t *data;...
Yes, that is what I was thinking. The plugin could do its own decoding directly off that data pointer if it's done within the same call.
I removed some discussion around supporting a Bytes property type in the general sense. That concept will be moved into the Metadata discussion regarding a Bytes metadata type.
The Bytes param type really works exactly like String or Custom, just with a length.
My use-case for Bytes is purely for binary "sequence data", like Mocha or Silhouette project data when running as a plugin, or for custom Lens Flare data, or anything else...
I don't think it would be a huge burden to make them animatable. They currently are NOT in Silhouette, but it would be possible. If we mandate that String, Custom...
Would this be requesting a default interpolation type for the parameter instead of just getting whatever the host decides? Or do you want to set specific key values and interpolation...