1. Messages
  2. Remap ocio config colorspaces to match nuke's defaults

Re: Remap ocio config colorspaces to match nuke's defaults

L P
 

Thanks a lot for the link. That really helped.

This is what I added to my init.py file:

------------

def OCIOColorspaceMapper(colorspaceRec709, dataTypeHint):
    if nuke.thisNode()['file'].value().endswith('.mov'):
        return 'Output - Rec.709'
    else:
        return colorspaceRec709

nuke.addDefaultColorspaceMapper( OCIOColorspaceMapper )

--------------

Seems to work fine while importing a rec709 .mov file.
I know nothing about Python, so I appreciate any suggestions to improve this little code

Thanks again,


Deke Kincaid wrote on 1/5/2022 10:18 PM:

you can either:

- Use python and remap these to colorspace names to known colorspaces in the ocio config with the colorspace callbacks.
https://learn.foundry.com/nuke/developers/131/pythondevguide/callbacks.html#default-colorspaces
- Add fake colorspaces with those names to your ocio config that reference existing colorspace.

On Wed, Jan 5, 2022 at 5:03 PM L P <sitiospam@...> wrote:
Hi All,
Nuke default's colorspaces are named differente than OCIO's colorspaces.
For instance, if color management is set to Nuke, it's called Rec709,  but if color management is set to OCIO, it's named Rec709 (ACES).
So if the project is managed by OCIO, when you import a MOV with Rec709 on it's metadata, Nuke can't find the correct colorspace and some times it completely crashes Nuke.
I've been trying with no success to remap Nuke's Rec709 to ACES Rec709. Also tried to duplicate OCIO's Output-Rec709 and rename it to Rec709 but can't make it work.
Any help on how to accomplish this would be much appreciated!
Thanks,
Join {ocio-dev@lists.aswf.io to automatically receive all group messages.