Re: Review: added ociobuildicc app

Malcolm Humphreys <malcolmh...@...>

On 29/01/2011, at 5:17 AM, Jeremy Selan wrote:


This is awesome! I've wanted to have icc export for so long, this is
hugely appreciated. (We'll use it at SPI immediately)

* What are the command-line arguments used in your example? I'd like
to give it a shot.
ociobuildicc --description="spi-vfx log test" --workingspace compositing_log --viewspace sRGB /Users/malcolm/Library/ColorSync/Profiles/spi-vfx_compositing_log_test.icc

* Would you consider renaming this app? ocio2icc, ocioicc, etc.
sure, it depends on how comfortable you are with the output as the profiles are modelling the transform:
scene_linear -> sRGB (Film) D65 -> Lab D50 (chromatic adaptation tag, takes it back to D65)

ocio2icc would be my vote


-- Jeremy

On Thu, Jan 27, 2011 at 10:59 PM, Malcolm Humphreys
<malcolmh...@...> wrote:
Also added Little CMS to LICENSE file



On 28/01/2011, at 5:49 PM, Malcolm Humphreys wrote:

Attaching some slightly larger examples :)

On 28/01/2011, at 5:46 PM, Malcolm Humphreys wrote:

Added ociobuildicc app which will build a soft-proofing icc profile for a given working space.
(added LCMS2 into ext)


Attached is an example of two profiles in action.

From the left
* sRGB reference image (ocio cpu)
* matte paint allocation space
* log space image.

The visual difference in the log image is most likely caused by 16bit quantization errors in the
CLUT of the AToB0Tag. These errors are less with the matte paint allocation as the distance
to travel is less.

I did play around with supporting the new MPE D2Bx and B2Dx tags which should make this
problem go away ( but couldn't
get it too work reliably so I pulled it out till I can.



Join { to automatically receive all group messages.