-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuke: Enhance Viewer process override with colorspace, display-view #613
Nuke: Enhance Viewer process override with colorspace, display-view #613
Conversation
…actor ExtractReviewIntermediates settings.
Added ColorspaceConfigurationModel for baking target selection and override in various settings to enhance flexibility and customization.
…tion notice for 'Baking' setting in ImageIOSettings. - Update descriptions for 'View' and 'Colorspace' settings to include information about using Anatomy context tokens. - Add a deprecation notice for the 'Baking' setting in ImageIOSettings, recommending the use of 'Baking Target Colorspace'.
…rocess-override-with-colorspace-display-view
Refactor settings conversions for better viewer configuration handling. - Added `_isGroup` attribute to models - Implemented functions to extract display and viewer from strings - Updated conversion functions for imageio settings
…rocess-override-with-colorspace-display-view
handle imageio_nuke dictionary, refactor ExporterReviewMov class to support different colorspaces for baking, and adjust settings in PublishPluginsModel.
Remove unused imports, refactor knob creation and updating functions, improve logging messages for better clarity, update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested with/without the colorspace override. Extract review can publish accordingly with or without colorspace override. When I loaded the mov back to the scene, the video appears to show my preferences of display and view with the colorspace override. It also stays with default Rec709 which can be set in baking target colorspace.
The left green read node is the one which publishes without enabling colorspace override, and the right one is with colorspace override enabled and setting the display as ACES, views as sRGB.
Co-authored-by: Jakub Trllo <43494761+iLLiCiTiT@users.noreply.github.com>
Co-authored-by: Jakub Trllo <43494761+iLLiCiTiT@users.noreply.github.com>
refactor functions for consistency.
…rocess-override-with-colorspace-display-view
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.