I'm looking at using OCIO as the basis for a photo editing applications CMS, but I need support for ICC profiles found embedded in image files and used as monitor profiles. Currently I use lcms for

I feared as much, but I'm surprised that with all the flexibility and uniformity that OCIO provides, there's no method to share LUTs. We've asked the vendors to provide their config.ocios along with

Neither of those can really be determined automatically from the LUT file alone Determining the interpolation requires visually inspecting the results of the LUT on various images.. but using linear

Hi as far as I know, no. 'allocation' too cannot be deduced. The only solution i can think of is having a file attached to the LUT specifying these parameters.

Hi, I'm new to OCIO and this forum, and I have what I think is probably a pretty common issue, although after searching for a solution for a couple days, I haven't come up with anything. My problem is

Looks like it fixed my problems! Thanks! I've dropped the patched based on pull request 300 as this version seems to incorporate SOME of the changes. The rest are not needed for linux but can anyone

Sorry took me ages to get back to this, version v1.0.9 has been tagged again with the doc system changes and the ExponentOp fix is also in there. Let me know if this doesn't work for you. **Version

Hi, Just wondering if there was any further feedback on my pull request - https://github.com/imageworks/OpenColorIO/pull/329 . Cheers, Mark

Excellent, much appreciated! -- Jeremy

Hello ! OpenColorIO.dll and ociobakelut.exe : 1.0.8 1.0.9 Built with msvc10 on win7 (64 bits). No time right now to do a full build but I'll try next time I'm on Windows. ++ Marie

Does anyone have an OCIO build already made for Windows that they're willing to share? Specifically, we're interested most in the OpenColorIO.dll and ociobakelut.exe, but it would be great to get ALL

Howdy, Any further feedback on this? Cheers, Mark

On Tue, Oct 8, 2013 at 6:15 PM, Malcolm Humphreys <malcolmh...@...> wrote: I just pushed a change which switches back to setuptools as the distribute fork has long been merged back into setuptools. I

I just pushed a change which switches back to setuptools as the distribute fork has long been merged back into setuptools. I have also pushed the versions

On Thu, Sep 26, 2013 at 3:14 PM, Malcolm Humphreys <malcolmh...@...> wrote: Sorry in the middle of a house move. It was part of the python 3 pull request someone sent. I thought it was a requirement

Sorry in the middle of a house move. It was part of the python 3 pull request someone sent. I thought it was a requirement to get it to work with 3. Once I'm back up and running I'm happy to revert it

Not sure why distribute was added. I'm very comfortable switching back if we believe it to be appropriate. -- Jeremy

On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote: Yah, I'm seeing that too. Looks like the docs build target is hosed for 1.0.9; looking into it... Can you confirm that everything

Hi! Just tested and added a link to buildlog in #318 issue. Hope it helps, somehow. Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A

On Mon, Sep 23, 2013 at 3:36 PM, Jeremy Selan <jeremy...@...> wrote: > 2. I got an error here: > Building CXX object > src/core_tests/CMakeFiles/ocio_core_tests.dir/__/core/GroupTransform.cpp.o > --