Hi Jeremy, All that we've done has been adding something into oiiotool to support an extra set of arguments to convert colour spaces.
You can find the changes that we made in this commit: https://github.com/Nvizible/oiio/commit/f98cf51f5a0796938caea98e0babec634f974328 So it's not really a proper integration - just a link inside oiiotool. Hugh Macdonald nvizible – VISUAL EFFECTS [email protected] +44(0) 20 3167 3860 +44(0) 7773 764 708 www.nvizible.com On 15 Oct 2011, at 01:31, Jeremy Selan wrote: > Hugh, > > Sorry for not responding sooner. > > Hugh Macdonald <[email protected]> wrote: >> We've done our own link between OCIO and OIIO (as a part of oiiotool). > > Excellent! Any chance on sharing what you've done? (not as a formal > pull request necessarily, even as a branch, or a conceptual overview > would be appreciated). I'm curious what route you've taken. > > I just pushed an initial implementation to maketx which adds (limited) > ocio support: > https://github.com/jeremyselan/oiio/tree/ocio > > I haven't yet commit the makefile support. I'm looking into the > cleanest way to add OCIO as an optional dependency. > > My current plan is that no matter whether OIIO is built with OCIO > support, the OIIO header / public symbols would remain identical. And > that the OCIO classes would not be exposed other than as opaque > predeclarations. We'll see if this is possible. > > (i'll address data window questions in another email). > > -- Jeremy > _______________________________________________ > 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
