ACES Config Manager

What it is

An admin node. Pick one of four actions from a dropdown, run the workflow, read the string outputs. It finds an existing ACES OpenColorIO config on your machine, downloads the official ACES 2.0 one if you don't have it, lists what colour spaces it contains, or reports its details.

There are no pixels in or out. It's the node you run once, when you're setting up colour management, and then forget about - except it's also useful as a lookup when you need the exact name OCIO expects for a colour space, which is a genuinely annoying thing to get right from memory.

The four actions

Detect Config searches, in order: the OCIO environment variable, a list of conventional install locations (C:\ACES\config.ocio, C:\Program Files\ACES\config.ocio, C:\Users\Public\ACES\config.ocio on Windows; /opt/ACES/config.ocio, /usr/share/ACES/config.ocio, ~/ACES/config.ocio elsewhere), then models/ACES/config.ocio inside your ComfyUI install, then the config Radiance bundles in its own ACES/ folder. That last one is why the pack's colour nodes work out of the box - Radiance ships a config and falls back to OpenColorIO's built-in ACES studio config at startup if nothing else is found.

Download ACES 2.0 fetches the official config from the Academy Software Foundation's OpenColorIO-Config-ACES release - specifically cg-config-v4.0.0_aces-v2.0_ocio-v2.5.ocio, the ACES 2.0 / OCIO 2.5 build. List Colorspaces dumps every colour space name in the active config. Get Config Info reports on it - path, version, what it found.

Inputs and outputs

action is the only required input. Optional custom_config_path lets you point at a specific .ocio file instead of auto-detecting; optional install_path says where a downloaded config should land, defaulting to the pack's own ACES/ folder.

The three string outputs are config_path, colorspaces_list and status_info. Only one or two are populated depending on the action - the others come back empty, which is normal and not an error.

This is an output node (OUTPUT_NODE = True), so setting the action and hitting Run is enough to execute it even if nothing downstream consumes its strings. That's deliberate; otherwise you'd have to wire it to a preview just to trigger a download.

Why you'd bother

Because OCIO configs are the thing every colour-managed node in this pack quietly depends on, and getting one used to mean going to GitHub, finding the right release asset among a dozen, downloading it, and figuring out where it's supposed to live. This collapses that into a dropdown.

The catch that makes it worth doing properly: OpenColorIO's built-in ACES studio config is a subset. It's enough for the common transforms, and plenty of pipelines never need more. But if a node asks for a colour space that isn't in there, you get an error naming a space you can't find anywhere in the UI. That's the moment to run List Colorspaces and see what you actually have, then Download ACES 2.0 and re-run.

Install

ComfyUI Manager → search Radiance → install → restart → refresh the browser. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/fxtd-studios/radiance.git
cd radiance
python -m pip install -r requirements.txt

This one genuinely needs its dependencies: opencolorio (the Python package is PyOpenColorIO) is what does the work, and the pack's install.py checks for it along with OpenEXR, diffusers and accelerate, installing anything missing. Windows portable users should use ComfyUI's bundled python_embeded\python.exe. If the manager reports no config and no OCIO, the Python package didn't land in ComfyUI's environment - the classic case of pip running against the wrong interpreter.

Gotchas

• Downloads are opt-in at the pack level. Radiance respects RADIANCE_ALLOW_DOWNLOADS=0; if you've set that (or your install does), the download action won't fetch anything. Set the variable to 1 or unset it before starting ComfyUI.
• Empty string outputs are normal. The action you picked determines which of the three actually carries data.
• A successful download doesn't change the running process's config. Radiance resolves OCIO at startup. Restart ComfyUI after installing a config, then re-run Detect Config.
• Setting $OCIO wins over everything. If detection keeps returning a path you don't expect, check your environment before you check the node.
• Config licensing. OCIO config files carry their own terms separate from Radiance's GPL-3.0. The official ASWF configs are permissively licensed, but check before shipping one inside a product.