MiniMax H3 Motion Director Inputs

MiniMax H3 Motion Director Inputs is the external prompt and media gateway for the Director - the way to feed the big H3 node from somewhere other than its own timeline UI.

The Director is great when you're hand-driving shots on its internal timeline. But the moment you want a prompt to come from a text node, an LLM, or a workflow you load as a template, typing into the fat Director node is the wrong move. That's what this node is for. It packages prompts and media into a single director_inputs socket you plug into MiniMax H3 Motion Director.director_inputs, and the Director treats it as just another source of truth for the current run.

It ships in the same j955229/ComfyUI-MiniMax-H3-Motion-Director pack as the Director itself, so installs are shared - see the Director article for the full walkthrough.

How it works

The interesting part is that this node has no fixed input sockets in its schema. The Director decides the mode and group count, and the Inputs node's dynamic sockets appear to match - ComfyUI's frontend creates them from whatever the connected Director expects:

• T2V → prompt_N (string) only
• I2V → prompt_N + a direct IMAGE
• FL2V / R2V / RV2V → prompt_N + a mode-specific Assets bundle from MiniMax H3 Motion Director Assets

So the chain is always the same three nodes:

MiniMax H3 Motion Director Assets
        ↓
MiniMax H3 Motion Director Inputs
        ↓
MiniMax H3 Motion Director

At execution, pack() collects whatever is actually connected and bundles it into a single MMX_MOTION_DIR_INPUTS payload. The one output is that director_inputs socket - no images pass through it, no inference happens here. It's plumbing, done cleanly.

Using it

Connect it to the Director's director_inputs input and set the mode on the Director - the Inputs node doesn't have a mode widget of its own. If you don't see prompt or image sockets, that's expected: they only materialize once the Director knows what it's running. This makes the node great for templates - one Inputs node, swap the Director mode, and the sockets reshuffle to match.

One thing to know before you reach for it: Mixed mode v1 doesn't use this node at all. The timeline's media lives in the Director's native UI, so the external group system stays quiet there. This is purely for standalone t2v / i2v / fl2v / r2v / rv2v jobs.

Install

Same pack, same steps. ComfyUI Manager: search "MiniMax H3 Motion Director", or:

cd ComfyUI/custom_nodes
git clone https://github.com/j955229/ComfyUI-MiniMax-H3-Motion-Director.git
cd ComfyUI-MiniMax-H3-Motion-Director
python -m pip install -r requirements.txt

Then restart ComfyUI. It adds no model files of its own - it's a wrapper around the Director, which still needs the H3 UNET, video/audio VAEs and minimax CLIP loaded in your graph. If the Director node isn't working, no amount of Inputs tweaking will help; fix that first.

The honest take: you don't need this node for your first H3 video. But once you start routing prompts from elsewhere, or rebuilding the same project structure with different inputs, it's the difference between a reusable workflow and a wall of copy-pasted timeline JSON.