Re: Using environment variables/context to point to a colorspace
donat...@...
Hi, Thanks for the ticket. I could indeed implement a callback for the OCIO colorspace nodes. I already have some code that sets the context variables of the OCIO ColorSpace node. The problem is then for the viewer dropdown menu. It would not be very convenient in Nuke's UI to have to add somewhere a button to control the viewer dropdown menu. In my previous implementation of OCIO I created different colorspaces such as "ShotViewAlexa", "ShotViewRedGamma3". These colorspaces were meant for Nuke's viewer. They convert from linear to the cam colorspace, then add a 3d lut specific to the shot. This was kind of problematic because users sometimes were using the wrong colorspace. I'd rather have a single colorspace for showing the shot specific grade. In the meantime I did find a workaround. I'm defining my 'shotView' colorspace as being a transfrom from Linear to the Camera Colorspace, then I apply a shot specific 3dl lut. In my config file it's like this : - !<ColorSpaceTransform> {src: Flat, dst: linear} # Flat is a balanced linear colorspace - !<FileTransform> {src: Camera/$CAMERA/$CAMERA_main.spi1d, interpolation: linear, direction: inverse} - !<FileTransform> {src: Camera/$CAMERA/$CAMERA_post.spi1d, interpolation: linear} - !<FileTransform> {src: $EVENT_Grade.3dl, interpolation: linear} So I think pointing to colorspaces using context variables would make OCIO much more flexible. I hope this makes sense... Regards. Donat Van Bellinghen
On Thursday, June 12, 2014 3:10:34 PM UTC+2, dbr/Ben wrote:
|
|