It's been a long time since our last release! There have been a bunch of updates that have not made it into any tagged release, and seeing as how we have a bunch of development work in progress it

Thanks for bringing this to our attention. I'll contact the foundry and see if we can find out what they've done. -- Jeremy

There are one, or two, more steps that need to be performed in Photoshop so that you can see the .icc in action. Unfortunately these aren't documented on the link. I can write it up and email it if

Hey guys, been a while but things seem to be going well with my Fedora package of ocio so I haven't needed to ask any questions lately. I was going through my packages and noticed I have two patches

I was reading the release notes for Nuke, http://thefoundry.s3.amazonaws.com/products/nuke/releases/7.0v1/7.0v1_ReleaseNotes.pdf ..and noticed a few items mentioning bug-fixes to OCIO nodes, like: >

That's correct! This guide should hopefully explain everything: http://opencolorio.org/userguide/baking_luts.html#icc-profiles-photoshop If you have access to a Linux machine, you could run

I'd be happy to assist. I don't a wealth of experience with compilers or porting from Mac but I'll be happy to assist and test. I can also help build an installer for Windows.

A very useful reference, great work Jeremy et al.

A shameless plug: For those who may be interested, the VES just released a white paper on motion-picture color management: Press

We dont yet have a how to on the windows build process, though we certainly would like to get one going! (Are there any volunteers on the list to assist with this?) In the long term, I think it

Hello, Is there a step by step guide to compile ocio for windows. I have been reading thru the articles. Not clear on how exactly to go about. -- Thanking You, Nishith P Singhai | Senior

yup, please clean up that error code too, thanks! We should also try to take advantage of github for code-checkin specific comments and discussions. I dont want to overwhelm people with minutia of

Should I pull out the code path in main.cpp that returns an error if --copyright is not set? It seems vestigial at this point.

Your last sentence is right, it does not error because there is a default value for 'copyright': std::string copyright = "OpenColorIO (Sony Imageworks)"; Whereas others like description are

i'd recommend also looking at oiio-tool (part of openimageio) as a command-line image utility. ocioconvert is super bare bones, and i'm actually consider moving into the oiio project itself. (I dont

*Adding*

Thanks all. Yes, I was able to get the desired result by add a colorspace to the config that applies the grade and the display LUT. We're trying ocioconvert as a way to make LUT-baked jpeg proxies of

I've been building various .ICC files and not once have I set the --copyright flag and not once has an error been thrown. After looking in the main.cpp for ociobakelut I see that it should be throwing

If you look at the spi-vfx configuration, the srgb8 and p3dci8 color spaces incorporate a film look using a 3D LUT. That's why you can use them as an output space but not an input space (the 3D LUT

It would be easy to add an "ocioconvert --look blah" argument. Made a ticket for that: https://github.com/imageworks/OpenColorIO/issues/292 I think ocioconvert is mainly intended as an example of how