For those who are looking to have an 'easy' system install of OCIO on the mac, you can now do it using homebrew. http://mxcl.github.com/homebrew/ http://braumeister.org/formula/opencolorio Thanks to

That's excellent :D I know approximately zero about this, but based entirely on that page, but sounds like they have integrated OCIO. The wording is maybe a bit strange, but it sounds like a

Adding support for IRIDAS .look LUT's should be easy, but a few test files are needed. https://github.com/imageworks/OpenColorIO/issues/249 If you have access to a bit of IRIDAS software which can

https://github.com/imageworks/OpenColorIO/pull/251 On a slightly related note, there's a bug in cmake <2.8.7 which causes "make test" (or "ctest") to take about 30 seconds (instead of the ~30

Thanks everyone for all the suggestions! (Closing the pull request.) Until next year...??... -- Jeremy

Well played Jeremy! ///d@

I was in the middle or writing an angry letter and then realized what day it was :) -deke

I haven't done a thorough check but I'll bet there are some uses of the letter Z that don't conform to convention either. Speaking of... Hugh, shouldn't that be "nvisible" ? ;-)

This is an outrage. I'm immediately switching to Photoshop CS 6 beta for all of my color needs. -stevel

Should this be done with #ifdefs instead? Perhaps driven by a USE_COLOUR variable? -sean

No concerns from this side of the pond... ;-) I've been somewhat concerned about this bug for some time now, and it's glad to see it's now been addressed. Now if only The Foundry

This breaks ABI compatibility. Let me know if anyone has any concerns? https://github.com/imageworks/OpenColorIO/pull/250 Example

Yes, that should be possible. There may be some performance implications. Memory access has high latency, so ideally you want to read your data once, do all the math in registers, then write the final

I just noticed that you can edit any files (in your own forks) directly though github. (I presume this has been there for awhile, but this it's the first time I have used it). While editing *code*

I've put together a *very* rough document that describes how OCIO works internally. It needs a lot of work, but it's at least a start. I'll add it to the mainline docs later this week after some

Ah when you said you were processingt the whole frame in the GPU, I immediately thought OpenGL, not CUDA. Sorry for the confusion.

CUDA doesn't really have framebuffers as such. OpenGL textures are mapped to CUDA arrays, which you can copy into but can't write directly from a kernel. So there's at least one copy going in, and

Can't you just bind your target framebuffer as a texture? No copy required and everything stays on the GPU.

Not entirely true. If you base them both on an OpenGL context, you can create OpenCL images from OpenGL textures, and you can access OpenGL textures from CUDA as well. ///d@ On Fri, Mar 30, 2012 at

That was my recollection as well, but I can't find any documentation or examples of this. Maybe I'm missing something. Do you remember any details? All I can turn up are some 3rd-party tools which