Larry, yes, I think it should definitely be a kind of fish, lol. Then we can change our Slack status to "Gone fishin'". :)
I don't have time to cast a line in the water at the present moment, but I can at least describe the OCIO side of the problem for someone who would like to try. The interface for an OCIO FileTransform is here: https://github.com/AcademySoftwareFoundation/OpenColorIO/blob/454b502cce596bd01b57651d313f0cb96324aee1/include/OpenColorIO/OpenColorTransforms.h#L1026 OIIO already supports transform direction, so the remaining options are for CCCId, CDLStyle, and Interpolation. The first one is a string and the other two are OCIO enums that are defined in OpenColorTypes.h. The CCCId is used to match up against the "id" attribute of the CDLs inside a file that contains more than one. The CDLStyle is used to control whether the CDL math should clamp (following the ASC spec) or not clamp (as is often done in VFX). The Interpolation gives control over the interpolation method used for LUTs. On the OIIO side, I think it's just a matter of passing in the arguments and then calling the setters on the FileTransform. It looks like the setters would be called here: https://github.com/OpenImageIO/oiio/blob/e47e501eb0d98fac572fa63b216275fb31512d06/src/libOpenImageIO/color_ocio.cpp#L1860 I should point out that even OCIO's own command-line tool for processing images (ocioconvert) does not allow controlling these options, so I don't want to fault OIIO for not allowing it either. But as we've just seen, people may occasionally want to adjust them. cheers, Doug > Can somebody spell out exactly what additional information > --ociofiletransform needs, and then what arguments they correspond > to in the underlying OCIO calls, and if anything needs to also change in > ImageBufAlgo::ociofiletransform() or its internals? _______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
