Nuke OCIO Info
See exactly what color spaces this pack can use
- STRING
This one is a debug node, and it's honest about it. NukeOCIOInfo takes no image input and outputs a single string describing your OpenColorIO setup - the OCIO version it found, the ACES 2.0 Studio Config the pack is built around, and the full list of color spaces, camera spaces, displays, and views available to the other Nuke OCIO nodes. If you're staring at NukeOCIOColorSpace or NukeOCIODisplay wondering what a "Linear BMD WideGamut Gen5" actually is, this is where you look.
Why it exists
The pack hardcodes 55 color space names from the ACES 2.0 Studio Config directly into its dropdowns. That's a deliberate design choice - ComfyUI's frontend doesn't dynamically populate dropdowns from a runtime OCIO config, so the author baked the full ACES 2.0 Studio list in to make every color space available to everyone, on every install, with zero config files to manage. The trade-off is that you have to trust the hardcoded list, and this node is the thing that shows you what's actually in it. Think of it as the manifest for the other OCIO nodes: the list of camera IDTs (ARRI LogC3/LogC4, Sony S-Log3, RED Log3G10, CanonLog2/3, Blackmagic BMDFilm and DaVinci spaces, Apple Log, DJI D-Log…) is printed out right here so you can find your camera's space by name before you go hunting through dropdowns.
What it does
No inputs, no wiring required - just drop it on the canvas and read the STRING output. You can feed that string into a text display node to read it in the UI, or check the console. It reports:
- Whether OpenColorIO is installed at all, and which version.
- The config name the pack is using (ACES 2.0 Studio Config).
- The full hardcoded list of 55 color spaces.
- The available displays and views for
NukeOCIODisplay.
If opencolorio isn't installed, the output says so plainly and tells you to run pip install opencolorio - which is also the single most common reason the OCIO nodes fail, so this node doubles as the first diagnostic you run when color space transforms error out.
Using it in a workflow
It's a utility, not a stage in your pipeline. Wire its string output to a ShowText-style node if you want the list in front of you, or just run it once and read the console. Mostly it's there so that when you look at the 55-space dropdown in NukeOCIOColorSpace and think "what is all this," you have a single node that prints the answer.
Installing it
It's part of the Nuke Nodes pack:
cd ComfyUI/custom_nodes
git clone https://github.com/sumitchatterjee13/nuke-nodes-comfyui.git nuke-nodes
cd nuke-nodes
pip install -r requirements.txt
Or search "Nuke Nodes" in ComfyUI Manager and restart. The category is Nuke → Color. For this node to report anything useful, make sure opencolorio is installed - it's in the pack's requirements.txt, so a fresh install gets it, but if you skipped that step, pip install opencolorio is the fix.
Common issues
- It just says "OpenColorIO not installed" - that's the node working as intended. Install opencolorio (version 2.2+ is what the code checks for) and restart.
- The output is a wall of text - yes, that's the point. It's a manifest, not a summary.
For anyone who's ever squinted at an OCIO dropdown and wondered what half the entries meant, this node is a genuinely useful map.
Inputs (0)
No inputs
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |