1. Messages
  2. Shot luts and different monitor calibrations

Re: Shot luts and different monitor calibrations

Simon Björk
 

Thanks Blake and Kevin for the explanations, really appreciated.

The whole thing with having multiple displays seems really nice and seems to work well in Nuke at least.

I guess one problem might be that User A (sRGB monitor) saves his Nuke script and when it's opened by User B (Rec709 monitor) the sRGB view is missing and Nuke
will give an annoying error. I see that the old spi configs use the same name for views across displays which would help with this, but it might also be confusing for the user.
Maybe there's a way to check for color spaces via a Nuke callback before the error is thrown.

Still, wouldn't it be nice to be able to set colorspace with an environment variable? That way I wouldn't need to have register multiple views/displays for a situation like this.
- !<View> {name: Grade, colorspace: ${DEFAULT_VIEW}, looks: PreGrade_LUT | nolook}

-------------------------------
Simon Björk
Compositor/TD

+46 (0)70-2859503


Den ons 25 nov. 2020 kl 19:12 skrev Kevin Wheatley <kevin.j.wheatley@...>:

Why the ACES and Nuke configs only have a single display, mostly for
legacy reasons. There were tools which didn't work well with the
situation of having different lists of views for different displays,
so the ACES config structured all the views under a single display,
Ideally tools would be able to handle this case better.

e.g. if you have:

Display 1 with views A, B and C
Display 2 with views A, C, D

When the user selects Display 1 with View B all good, but selecting
Display 1 from a drop down which choice should be shown for the view,
etc.

the ACES config basically combined them to say

Display ACES, with views 1A, 1B, 1C, 2A, 2C, 2D

It is more in keeping with how OCIO is intended to be used, to use
multiple displays to represent different display devices.

Kevin
Join ocio-dev@lists.aswf.io to automatically receive all group messages.