Phil Barrett

Suggest CI builds are amended to include this as a normal test case so this doesn't keep happening.

A few questions - this is all host-side. Is there any desire for a plugin to be able to request its inputs are in a specific colour space (or to...

"clips which are color managed by OCIO" makes a requirement that the host uses OCIO. Hosts which have their own colour management may want to use this OFX mechanism without...

> > * what defines the colour space of the output image? > > It's assumed to be in the same colourspace as the input image No, that won't do....

Actually should the viewer properties really be set per-clip (indeed in the current header, per-input-clip)? Surely any viewer is effectively global (and needs to be accessible by a Generator plugin...

Looks better now thanks. I don't know OCIO but I gather all the colour space names are locally-defined in the config file so there's no globally-agreed name for any globally-defined...

Yes I think that makes sense. Can't make it a host property, because in a host that doesn't use OCIO but instead fabricates an OCIO config at runtime, the config...

So my interpretation is that in OCIO a role is a reasonably well-defined (but not guaranteed?) name which OCIO resolves to a real locally-defined OCIO colour space. The actual colour...

> All this data is simply preprocessor definitions done in a very simple way > and needs supporting code to make it usable. I would encourage this to be >...

Which of the many strings in `ofxColourspaceList.h` need to be used? For example the well-known ACEScct space would appear to be represented by `kOfxColourspaceRoleColorTiming`, `kOfxColourspaceRoleCompositingLog`, `kOfxColourspaceRoleTexturePaint`, `kOfxColourspaceACEScct`, `kOfxColourspaceACEScctAliasACESACEScct` and `kOfxColourspaceACEScctAliasAcescctAp1`....