How to work with shot-based luts?

General
1

[Ported from Discord. Question by @Danell, Answered by @fabiaserra

Have anyone worked with shot-based luts? So one lut per shot.
Any pipeline to deal with this so the preview file gets the correct lut applied to it?

1 Like
2

Answer by @fabiaserra :

we do, we have a config.ocio with search paths like this:

search_path: |
  /pipe/ocio/OpenColorIO-Configs/aces_1.2/luts:
  luts:
  grade:
  /pipe/ocio/luts:
  /proj/$SHOW/shots/$EPISODE/$SEQ/$SHOT/ocio/luts:
  /proj/$SHOW/shots/$EPISODE/$SEQ/$SHOT/ocio/grade:
  /proj/$SHOW/shots/$EPISODE/$SEQ/ocio/luts:
  /proj/$SHOW/shots/$EPISODE/$SEQ/ocio/grade:
  /proj/$SHOW/shots/$EPISODE/ocio/luts:
  /proj/$SHOW/shots/$EPISODE/ocio/grade:
  /pipe/ocio/identity/grade:
  /pipe/ocio/identity/luts

In this example luts: and grade: are relative to the location where the config is…
config.ocio will search for them with top-down priority.

and then a shot_lut look that applies a grade.ccc file if it finds it on those search paths. As long as the $OCIO and env vars are defined on the context of the process extracting the review, it automatically should apply it. that works for any DCC that supports OCIO really, Nuke, RV, Houdini…

For more info OCIO config environment variables distribution · Issue #4299 · ynput/OpenPype · GitHub