◎ Radiance Manager

The node is called "Radiance Manager" in the menu, which tells you more about Radiance's ambitions than about what the node does. It doesn't manage anything - it's a cinematic prompt generator with a stack of real-world camera and lens profiles. You pick an ARRI Alexa 35, slap a Master Anamorphic on it at 50mm, T2.0, 180° shutter, 800 ISO, and it hands you back a ready-to-use prompt string plus a second string with the technical data baked in.

The point of it is the 2026 discovery that naming a physical camera is the single highest-leverage phrase you can put in a prompt, because modern text encoders were trained on real captions and actually know what "shot on an ARRI" means. The Manager just industrializes that trick - instead of typing "shot on ARRI Alexa 35, 50mm, shallow depth of field, 180 degree shutter" from memory, you pick it from dropdowns and get consistent, correctly-spelled output every time.

What you're actually setting

Seven required dropdowns, and they map one-to-one to a real camera spec sheet:

• camera - 20 bodies, from ARRI Alexa 35/LF/65 (IMAX) through RED, Blackmagic, and Panavision. This is the phrase the model keys on hardest.
• lens_series - 18 lens families, from Master Anamorphic to vintage Canon K-35 and Cooke Panchro. Anamorphic vs. spherical genuinely changes the character the model draws.
• focal_length - 22 options, 8mm fisheye through 200mm+. Watch this one: a 135mm telephoto "compresses" the background, and the model knows it.
• aperture - T-stops with honest descriptions ("T0.95 dreamy razor thin" to "T22 everything in focus"). This is your depth-of-field control.
• shutter - angle-based: 180° standard motion, 90° staccato action, 360° maximum blur. Mostly flavor for stills, genuinely useful for video prompts.
• iso - 50 through 12800, the ISO entries map to grain/noise character.
• base_prompt - your actual subject. The dropdowns are the seasoning, this is the meal.

Optional shot_type (Extreme Wide through Macro) and camera_movement (static, handheld, dolly, whip pan...) round it out. Set those and the framing language appears in the output.

Outputs

Two strings: prompt - the full assembled cinematic prompt to paste into a text encoder - and technical_data_str, a second string carrying the camera/lens/ISO data for when you want to append the spec sheet as a prompt suffix or keep it as metadata. Wire prompt into your CLIP Text Encode (or into Radiance's own Cinematic Encoder if you want it auto-encoded) and run.

Where it sits in the pack

This is the string-builder; the separate ◎ Radiance Cinematic Encoder is the string-builder-plus-CLIP-encoder that outputs conditioning directly. If you're on SDXL you'll usually reach for the Encoder. If you're on Flux, where the manager's dropdown vocabulary also reads great, grab the string and drop it into your normal text encode node. Keep in mind the pack's own community reception: the launch thread praised the ambition but the reception for the 32-bit claims was mixed, and the docs were flagged as thin - the prompt nodes, at least, do exactly what they say.

Install

Search "Radiance" in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/fxtdstudios/radiance.git
cd radiance
pip install -r requirements_linux.txt   # or windows/mac_silicon variants

Restart after installing. Linux needs libopenexr-dev first, and the dependency set (OpenEXR, OpenColorIO, colour-science, transformers) makes the first boot slow. If Manager's security level blocks it, the manual clone is the documented workaround.