Is it perhaps an idea to include OCIO with OIIO statically, and allow the
user to provide an external OCIO at compilation?
That way we can keep the code paths the same, and never have to worry about
the user not having OCIO :)

> but it happens to not include a sRGB color space, what should happen?
If they don't provide a color transform, and there isn't one that matches
the detected one in oiio:ColorSpace, then we can print a warning and fall
back on an internal one we define for that file type (our own "sRGB" say).





On Tue, Aug 5, 2014 at 11:27 PM, Larry Gritz <[email protected]> wrote:

> Yes, that's exactly what I mean. Out of the box (i.e., without a full VFX
> color pipeline installed), oiiotool ought to be able to read a JPEG (sRGB),
> convert it to linear for some image math that expects linear math, then
> convert back to sRGB for output. Or convert an sRGB to a linear EXR
> (happily blind to the true meanings of the primaries, but just wanting to
> linearize, dammit). And other similarly straightforward examples. Yes, it's
> "wrong" if you don't know what those colors really are, but at the same
> time it seems silly to not be able to make a best guess at the obvious
> thing.
>
> Slight wrinkle: If you do have a full OCIO setup, but it happens to not
> include a sRGB color space, what should happen? Should OIIO employ OCIO
> only when a color space that OCIO knows about is mentioned, but make its
> best guess otherwise? Or if there's an OCIO config present, should anything
> not explicitly defined by it be considered an error?
>
>
> On Aug 5, 2014, at 3:05 PM, Pete Black <[email protected]> wrote:
>
> > Currently, there are  linear, sRGB and rec709 transforms available in
> OIIO if we don't have OCIO at compile time, and it seems a little strange
> (for someone working with a VFX pipeline it is obvious OCIO expects a
> user-supplied config, but this may not be so for many of OIIO's users ) not
> to have at least the same capability 'out of the box' when compiled with
> OCIO.
>
> --
> Larry Gritz
> [email protected]
>
>
>
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to