This pull request addresses the limitations of the Baking preset Viewer process override input field. Previously, the field was restricted to accepting only display and view type names for presets, leading to potential confusion among users. With this update, we have expanded the functionality to include colorspace names, thereby enhancing the user experience and aligning with industry-standard practices.
Key Features Implemented:
Extended input validation to accept colorspace names in addition to display and view type names.
Integrated anatomy template formatting support, allowing names to be tied to specific contexts within the pipeline.
Ensured compatibility with upcoming OCIO config publications that will feature baked-in looks such as LMT (Look Modification Transform), ODT (Output Device Transform), and Display & View transforms, where naming conventions are context-specific.
Revised settings architecture for Viewer/Monitor and Baking color space targets.
Implemented settings conversion from legacy structure for the copy settings and project overrides tool.
The implementation has been thoroughly tested to confirm that it meets the desired specifications and behaves as expected across various scenarios. This enhancement is a step forward in our ongoing efforts to streamline our color management workflow and provide robust tools for our users.
Additional info
Some debug logging were removed and f-string conversions done
Testing notes:
To replicate this test case, ensure that the configuration with context-specific names is loaded within a Nuke task session. Reach out on Discord to coordinate a joint testing effort.
ynbot
commented
1 month ago
Changelog Description
This pull request addresses the limitations of the Baking preset Viewer process override input field. Previously, the field was restricted to accepting only display and view type names for presets, leading to potential confusion among users. With this update, we have expanded the functionality to include colorspace names, thereby enhancing the user experience and aligning with industry-standard practices.
Key Features Implemented:
The implementation has been thoroughly tested to confirm that it meets the desired specifications and behaves as expected across various scenarios. This enhancement is a step forward in our ongoing efforts to streamline our color management workflow and provide robust tools for our users.
Additional info
Some debug logging were removed and f-string conversions done
Testing notes:
To replicate this test case, ensure that the configuration with context-specific names is loaded within a Nuke task session. Reach out on Discord to coordinate a joint testing effort.