![]() For example, the scene_linear role uses the ACEScg colorspace:ĪCEStransformID: urn:ampas:aces:transformId:v1.5:_to_ACES.a1.0.3 The name and family define which colorspace is associated with the role. The ! describes colorspace name and family. OCIO roles are stored in config files, some of which ship with Nuke in the following directory:įor example, the aces-v1.3 config file includes the following roles: ![]() All of the colorspaces in the OCIO config file are still accessible, but they have been grouped together into a Colorspaces menu under the roles. OCIO roles are the primary method for selecting colorspaces. For instance, if an element is coming from your matte painting department and should always be brought into Nuke as sRGB, you can create a matte painting role, which is associated with the sRGB colorspace for your artist to select. OCIO roles allow you to set custom role names for different colorspaces to make it easier for artists to instinctively know which transform to use for any shot. Instead, OCIO Color Management is automatically set in the comp’s Project Settings, and the correct OCIO colorspace is set directly into the Read and Write nodes. Nuke Studio-created comps no longer contain automatically injected OCIOColorspace nodes.For example, selecting an ACES config sets the working space to scene_linear (ACEScg). This defaults to the scene linear role defined in your OCIO config. This automatically sets the output transform colorspace of Write nodes, and the Input Transform colorspace for Read nodes. The working space dropdown sets the colorspace that Nuke uses internally for its image processing.See the following path for the default implementation that ships with Nuke: These defaults can be overridden using Python callbacks. The default value for each menu match the defaults in a project with the same config. The default LUT settings dropdowns are also populated with the list of colorspaces or display transforms defined in your OCIO config. ![]()
0 Comments
Leave a Reply. |