Would FileTransform::setOptionString(...) introduce the same complexity? Say you wanted to create the OCIOFileTransform in nuke. In this system, would you expect to see a single knob,

Am 15.09.11, 17:50 -0700 schrieb Jeremy Selan: That looks like cmake output. But littleCMS (alias lcms) uses autotools and is written in C not C++. Did you check with lcms' native build system? Btw.

I leave it up to you to decide what makes it into 1.0. At the end of the day I would just be happy to somehow replace these: FileTransform::getCCCId() FileTransform::setCCCId(const char * id) But I

Hey Jeremy,

Malcolm, Sorry for the delay in responding. First, I agree with you that dynamically defined FileTransform options would have more elegant. (prman is a great example of how such an API can stay

Hey, Just giving my two cents but having ocio support icc transforms would be a killer feature. Would this be too invasive a change to make it into 1.0? Cheers, Andrew

Hi, As we are fast approaching 1.0 I know it's a bit late in the day for some API changes. But I noticed these while doing the JNI wrapping for the android port some things which would be really good

With "mylut.csp", and the following saved as "example.yaml" (http://pastie.org/2523829 incase the formatting is screwed up): ocio_profile_version: 1 # Look in current working dir for

Hi Jeremy, Thanks very much for your response and it would be absolutely amazing if you could add that option into to specify a 3D lut path. If that's a fairly substantial amount of work, is there a

<gresham...@...> wrote: Let me clarify. The colorspace we work in for texturing is partially (but not totally) neutral. Our rendering is in HDR linear, and the way our pixels get to the scene

Hey all, This exact issue has been on my to do list for a long time. Previously I looked at spaceman icc (http://www.lightillusion.com/spaceman.htm) but never had enough time to get it working

Thanks! Currently, no. Both ociobakelut and ocio2icc require an ocio profile. However, it would be a pretty simple change to add the functionality to allow you to specify a single lut (or luts) on

First off, major congrats and thanks for open-sourcing this as it's something I'm very interested in embedding in our studio. That said, I was wondering if there was a way to create an ICC profile

As promised, OpenColorIO 1.0 Release Candidate 1 is now available for testing. (No branches necessary, it's the top of the master repository.) https://github.com/imageworks/OpenColorIO We will

https://github.com/imageworks/OpenColorIO/pull/162 Exposes additional build options Allows more flexibility at cmake build time, including... - build unittests without building library - build

0.9 / 1.0 branch only https://github.com/imageworks/OpenColorIO/pull/161 Addresses issue #150 -- Jeremy

0.9 / 1.0 branch only https://github.com/imageworks/OpenColorIO/pull/160 Addresses issue #154 -- Jeremy

OCIO 0.8.6 has been released. This will be the final 0.8 release before the 1.0 release candidate later this week. The biggest change in 0.8.6 is the config reading / writing has been updated to

https://github.com/imageworks/OpenColorIO/pull/159 Fixed some misspellings and re-enabled all the NukeWrapper features, redoing the knob layouts. I did remove some knobs rather than use the

https://github.com/imageworks/OpenColorIO/pull/158 -- Jeremy