Look Transforms

[Derek]

@jmgilbert

If we’re going to go down the road of providing default look transforms, I would prefer to call them sample look transforms and also provide a library of them. Providing a single one would trick novice users into thinking that there is single blessed way and railroad us down the ACES 1.0 path of everything looking the same.

+1 for me on this!

@ChrisBrejon has also mentioned this in regards to the contrast of the tone mapping in the look. I think it makes sense to have at least 3 in the library:

• Legacy ACES current “high contrast” legacy look,
• Neutral the OpenDRT neutral tonemapping (i.e. no look),
• Default A less aggressive tone mapping with slightly lower default contrast, as per the VWG proposal:

“Look is too strong-contrast and saturation are frequently reported as too high as a starting point for color gradingand look development” and “Slightly lower default contrast”

Does that sound reasonable?

In terms of things like HK compensation or the “glow” modifier, I wonder if this could be in the form of modules in OCIO look so one could have a combo of tone mapping combined with what ever extra things are desired in a “flavor + toppings” kind of structure.

- !<Look>
    name: beauty
    process_space: ACES
    transform: !<GroupTransform>
      children:
        - !<Flavor> {src: vanilla ice cream}
        - !<Toppings> {src: chocolate sprinkles}