ACES IO — Config Info

ACES IO - Config Info is the pack's reference manual in node form. It doesn't transform a single pixel - instead you feed it an OCIO_CONFIG (from the Config Loader) and it spits out a text listing of what that config actually contains. That's more useful than it sounds, because an ACES config's flat dropdowns hide hundreds of colorspace names, and "does this config even have a looks entry called that?" is exactly the question that stops you dead mid-workflow.

Inputs and output

Two inputs: ocio_config, and list_type with five options:

• Colorspaces - every colorspace in the config, the exact list you see in the ColorSpace node dropdowns.
• Displays + Views - grouped by display device, which is the fastest way to find the view name you want for the Viewer or Display Transform (and how you'd confirm a view like ACES 2.0 - SDR 100 nits (Rec.709) exists).
• Looks - look names plus their process_space, for the Look Transform node.
• Roles - the role → colorspace mapping, e.g. scene_linear and compositing_log. Relevant if you're about to use Log Convert and want to check what those roles resolve to.
• Config Info - the meta view: OCIO profile version, counts of colorspaces/looks/displays, and what the key roles resolve to.

The single output, info, is a STRING. Wire it into a text/note display node (or anything that shows a string) to read the listing, and it's also printed to the ComfyUI console. Because it's an output node, nothing else plugs out of it - it's a terminal inspection tool.

When you'd actually use it

Honestly, most of the time you don't need this node - you'd reach for it when things stop making sense. Two recurring scenarios:

• You loaded a custom studio .ocio and have no idea what it names its camera-log spaces. Run Config Info → Colorspaces and read the actual names instead of hunting through a dropdown.
• You switched the Config Loader between ACES versions and some node fell back to defaults. Config Info → Displays + Views tells you what the new config genuinely offers, so you can repoint your Viewer/Display nodes at real names.

Install

It's in BISAM20/ComfyUI-ACES-IO, installed like the rest of the pack: ComfyUI Manager → Install Custom Nodes → ComfyUI-ACES-IO, restart, or git clone https://github.com/BISAM20/ComfyUI-ACES-IO into custom_nodes plus pip install -r requirements.txt. The pack's one real install hurdle is PyOpenColorIO - pip installs it as opencolorio, not under the "PyOpenColorIO" name, and Manager's install hook handles that automatically. No model downloads; ACES 2.0/1.3 configs come built into OCIO itself.

Small note: it's a utility node, not a glamorous one - but the next time a colorspace error message names a space you've never heard of, this is how you find out whether you typed it wrong or the config genuinely lacks it.