Avoid OCIO 2 exception by setting strides correctly (#2911)
Avoid OCIO 2 exception by setting strides correctly (#2911)

For the case of applying a color transformation to just one color, we
were sloppy and set the strides to 0 (just one color means we are not
iterating from point to point using the strides).

OpenColorIO 1.x didn't care, but OpenColorIO 2.0 throws an exception if
the strides don't look valid.

Thanks to Thomas Metais for the fix suggestion.
OpenImageIO/oiio,lgritz/oiio,lgritz/oiio,OpenImageIO/oiio,OpenImageIO/oiio,lgritz/oiio,OpenImageIO/oiio,lgritz/oiio