ID 219603 - Custom OCIO configuration Default Color Transforms are not populated on launch causing 'No valid project setting' error on export/create comp

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
Setting the OCIO environment variable to a custom configuration file before launching NukeStudio or Hiero does not sync the Color Management Default Color Transform values to the appropriate colorspace LUTs, causing errors when exporting or creating comps due to missing default project settings.

Steps to reproduce
1) in a Terminal execute
export OCIO=/usr/local/Nuke10.0v1/plugins/OCIOConfigs/configs/aces_1.0.1/config.ocio
2) launch NukeStudio from that terminal as /usr/local/Nuke10.0v2/Nuke10.0 --studio
3) ignore the Recent projects and select the Untitled 1, then select Project->Edit Settings->Color Management. You should see:
 
  • Color Management set to OCIO and locked to any edits
  • OpenColorIO Config set to nuke-default and locked to edits
  • Default Color Transforms blank (8 Bit Files, etc) only Working Space is set


4) import a sequence/video, drag it onto the timeline to create a sequence and try to export it as a sequence. You will get:
 

Task 'TranscodeExporter' reported errors:
No valid project setting for 8Bit LUT

 
Also in the terminal I also get
 
Traceback (most recent call last):
  File "/usr/local/Nuke10.0v1/pythonextensions/site-packages/hiero/core/FnNukeHelpers.py", line 312, in _Clip_addToNukeScript
    colorspace = nukeColourTransformNameFromHiero(colourTransform, project)
  File "/usr/local/Nuke10.0v1/pythonextensions/site-packages/hiero/core/FnNukeHelpers.py", line 35, in nukeColourTransformNameFromHiero
    projectsettings = project.extractSettings()
  File "/usr/local/Nuke10.0v1/pythonextensions/site-packages/hiero/core/__init__.py", line 253, in _Project_extractSettings
    'lutSetting8Bit'             : _projectSetting(self, self.lutSetting8Bit),
  File "/usr/local/Nuke10.0v1/pythonextensions/site-packages/hiero/core/__init__.py", line 243, in _projectSetting
    raise e
RuntimeError: No valid project setting for 8Bit LUT
[15:05.59] ERROR: Bad value for out_colorspace :
[15:05.59] ERROR: Bad value for in_colorspace :
 
4) For the same sequence try and go Effects->Create comp special, you get:
 
hiero.exporters.FnNukeShotExporter.NukeShotExporter
No valid project setting for 8Bit LUT
hiero.exporters.FnExternalRender.NukeRenderTask
No valid project setting for 8Bit LUT
hiero.exporters.FnNukeAnnotationsExporter.NukeAnnotationsExporter
No valid project setting for 8Bit LUT
hiero.exporters.FnExternalRender.NukeRenderTask
No valid project setting for 8Bit LUT

 

 
Reproduced by support
Reproduced on Linux CentoOS 6.7 in 9.0v1, 9.0v8, 10.0v1 and 10.v2. Also reproduced on Windows 10 and Mac OSX 10.11 on 10.0v2.

Expected behaviour
Setting the OCIO env var should also sync the default color transform settings for all LUTs, (8, 16, floating point) to avoid error due to Nuke missing the default LUT project settings.
In normal Nuke the behaviour is slightly different in the sense that setting OCIO doesn't lock the Color Management and OCIO Config and nothing is loaded by default on launch from the custom OCIO config used.
The user needs to manually force the load by changing the Color Management from Nuke to OCIO when the LUT values get populated automatically.
 

Actual behaviour
NukeStudio doesn't load the individual default LUT settings when using the OCIO environment variable to declare a custom configuration file.
 

    We're sorry to hear that

    Please tell us why