OpenH3-IR Director

OpenH3-IR Director is the optional one, and it's the node people skip until they hit the problem it solves: you have a great sentence for your MiniMax H3 video, but the camera, the light, the pacing and the music are all left to the writer's taste, and the writer's taste isn't yours. Director packages a taste - framing, camera movement, camera height, lighting, color, pacing, performance, sound and music - and applies it to whatever your prompt left open.

Leave it disconnected and the pack behaves exactly as normal. Connect one and the writing model gets reusable direction for the decisions you didn't take yourself. That's the whole contract, and the README is unusually clear about its boundaries: Director steers what you left open, and never overwrites something you explicitly asked for. Say "a locked-off wide" and you get a locked-off wide whoever is directing; Director can still shape its light, sound and performance. Pin a shot count on Main and Director doesn't get to change it.

How it works

The direction itself is ordinary prose, fully visible on the node - the useful part of a director isn't the name, it's what they repeatedly do. The shipped pack ships seven editable examples, and you can change, rename, delete them or save your own. The name is for your library and the report; only the direction is sent to the writer. Nothing is selected behind the scenes - what you can read in the box is what gets used.

One genuinely clever piece: MiniMax H3 recognizes twenty camera moves by name, and Director exposes that closed vocabulary so a direction can use the exact term H3 knows - "track left", say - instead of an approximation that gets weaker adherence. The shipped directions use those names where appropriate, and can also say which moves to avoid.

What you touch

One input, profile - the direction's own state as text, written by the panel. It's a field rather than hidden state deliberately, so a saved workflow (and a rendered video carrying that workflow) carries the direction with it: drag the video back in and the direction comes back. Editing it by hand works. One output, director, wires into the director socket on OpenH3-IR Main - that's the only thing it connects to.

Saving is optional and often unnecessary. The graph already carries the text you wrote, so you never need to save a direction for it to work. Saving just makes it reusable across workflows on the same ComfyUI; saved directions live as plain files under user/default/openh3ir/directors/. Because a workflow carries the direction itself, not a pointer to a library entry, sending the graph to somebody else works even if they've never seen your Director library.

When to reach for it

If you render one-off clips from a sentence, you can skip this node entirely. Director earns its keep the moment you're producing a series and want a consistent look - the same lighting language, the same restrained camera, the same hand on the music across a whole batch. That's the pattern it's built for, and because it's just prose, stealing a friend's good direction is a copy-paste, not a conversation with their library. If a direction is fighting your explicit prompt, re-read your sentence first - stated things always win, so the fix is usually to state the thing.

Install

Search OpenH3-IR in ComfyUI Manager and install, or:

git clone https://github.com/ruashots/ComfyUI-OpenH3-IR.git ComfyUI/custom_nodes/ComfyUI-OpenH3-IR
/path/to/ComfyUI/python -m pip install -r ComfyUI/custom_nodes/ComfyUI-OpenH3-IR/requirements.txt

Director is purely additive - a Main node plus a Setup node is a working text-only graph without it, and nothing about it changes your install requirements. It's the rare custom node you can add to a workflow you already have without touching the render side at all.