color picking role, used in Nuke?
Let me start by introducing myself, I currently work at Image Engine, Vancouver and previously I was at Framestore, London.
I'm looking at doing comp work with wider gamut sources and I'm wondering about the color picker color management in Nuke.
Does anyone have found if the color picking role is ever being used by Nuke?
Should I do transformation myself if not?Anyone has tips to do that elegantly?
Cheers
Lucien
Hi everyone,--
Let me start by introducing myself, I currently work at Image Engine, Vancouver and previously I was at Framestore, London.
I'm looking at doing comp work with wider gamut sources and I'm wondering about the color picker color management in Nuke.
Does anyone have found if the color picking role is ever being used by Nuke?
Should I do transformation myself if not?Anyone has tips to do that elegantly?
Cheers
Lucien
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.
Greetings Lucien. Fellow Vancouverite here.
I made a simple OCIO configuration to test whether or not colour pickers are colour managed. It is only a rotation of sRGB primaries so that it is deadly obvious whether or not the application is colour managing correctly.
If you are using a wider gamut reference, the colour primaries will be quite different, and as such, the pickers would need to be properly transformed to whatever display is currently in use. Chances are, the picker isn't, and is instead dumping ambiguous RGB values direct to the display, putting the primaries in whatever the display currently happens to be.
The test config should reveal it quite quickly. If the pickers aren't colour managed, then artists have no real clue what they are picking. This would, for example, result in picking rough sRGB display values by eye, while the RGB triplets represent something else entirely in the reference space.
Feel free to email me privately if you have issues with the configuration.
https://github.com/sobotka/OpenColorIO-Colour-Management-Test
With respect,
TJS
Nuke does not use the colorpicking role and it selectively uses the roles in general as there is no direct mapping for some of them.--On Mon, Nov 9, 2015 at 11:17 AM, <lucien...@...> wrote:Hi everyone,--
Let me start by introducing myself, I currently work at Image Engine, Vancouver and previously I was at Framestore, London.
I'm looking at doing comp work with wider gamut sources and I'm wondering about the color picker color management in Nuke.
Does anyone have found if the color picking role is ever being used by Nuke?
Should I do transformation myself if not?Anyone has tips to do that elegantly?
Cheers
Lucien
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.
thanks for you answers!
So one would grade aces material in Nuke by only looking at his viewer rather than picking a shade from the color wheel I guess.
Anyone wants to chime in, production experience of comping in Aces/AcesCG?
Cheers
Le lundi 9 novembre 2015 12:47:45 UTC-8, Troy James Sobotka a écrit :
Greetings Lucien. Fellow Vancouverite here.
I made a simple OCIO configuration to test whether or not colour pickers are colour managed. It is only a rotation of sRGB primaries so that it is deadly obvious whether or not the application is colour managing correctly.
If you are using a wider gamut reference, the colour primaries will be quite different, and as such, the pickers would need to be properly transformed to whatever display is currently in use. Chances are, the picker isn't, and is instead dumping ambiguous RGB values direct to the display, putting the primaries in whatever the display currently happens to be.
The test config should reveal it quite quickly. If the pickers aren't colour managed, then artists have no real clue what they are picking. This would, for example, result in picking rough sRGB display values by eye, while the RGB triplets represent something else entirely in the reference space.
Feel free to email me privately if you have issues with the configuration.
https://github.com/sobotka/
OpenColorIO-Colour-Management- Test With respect,
TJSOn Mon, Nov 9, 2015, 11:39 AM Deke Kincaid <deke...@...> wrote:Nuke does not use the colorpicking role and it selectively uses the roles in general as there is no direct mapping for some of them.--On Mon, Nov 9, 2015 at 11:17 AM, <luci...@...> wrote:Hi everyone,--
Let me start by introducing myself, I currently work at Image Engine, Vancouver and previously I was at Framestore, London.
I'm looking at doing comp work with wider gamut sources and I'm wondering about the color picker color management in Nuke.
Does anyone have found if the color picking role is ever being used by Nuke?
Should I do transformation myself if not?Anyone has tips to do that elegantly?
Cheers
Lucien
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.