MiniMaxDirector 0.1.0
First release.
MiniMaxDirector adds one node to ComfyUI. You lay out shots, camera moves and audio cues on a
timeline, and it compiles them into the single structured prompt MiniMax H3
actually reads — then hands the sampler its conditioning and a clip length it will accept.
What it does
- A timeline, not a prompt box. Three tracks: what happens on screen, how the camera moves,
what is heard. Each segment carries its own text and its own span. - Compiles to the documented format. H3's guide specifies three fields —
integrated_multimodal_descriptionwith[Shot N]markers and cut timecodes,
overall_soundscape, andnon_diegetic_music. Camera work and timed sound are written
inside the shot they belong to, which is the part of the prompt the model demonstrably follows. - Valid clip lengths only. H3 accepts
length % 17 == 5at 24 fps; the node snaps to the
nearest legal count so a run cannot fail on an arithmetic detail. - References wired, not typed. Drop an image, audio or video on a segment and it becomes
<Picture n>/<Audio n>/<Video n>, numbered from the graph — so the prose and the
wiring cannot disagree. promptandreportoutputs show exactly what was built and what the linter thinks,
before you spend a GPU on it.
Install
Via the Comfy Registry:
comfy node install minimax-director
Or clone into ComfyUI/custom_nodes/. No dependencies beyond ComfyUI ≥ 0.30.0, where the
MiniMax H3 nodes landed.
Notes
An example graph is in examples/, and docs/GUIDE.md walks through building a clip.
Camera vocabulary follows MiniMax's own documented terms, so the model receives wording it
was trained on rather than enum values.
MIT licensed.