MiniMax Director — Report

The worst kind of video bug is the one you find out about after the render. With a 33B omni-modal model like MiniMax H3 that picture-plus-audio pass is expensive, so a workflow that only surfaces problems at queue time costs you both patience and VRAM. MiniMaxDirectorReport (display "MiniMax Director - Report") is the pack's answer to that: a panel that shows the linter's findings on the timeline while you edit, so the gap in the shot list is a red line on screen rather than a mystery in the finished clip.

It's the same argument as its sibling MiniMaxDirectorPrompt, one step further. That node shows you what H3 is being told; this one shows you what's wrong with it. Every check the linter makes is free - pure text logic, no model needed - so there's no reason to learn about a problem from a finished video when the answer was sitting in a panel the whole time.

What the linter actually catches

The MiniMaxDirector node runs a real lint pass on every edit pause, and this node surfaces its report. The checks mirror the rules in MiniMax's published prompt guides, so they're worth taking seriously rather than treating as decoration:

Keyframes vs references conflict. MiniMax documents first frame / last frame and reference images/videos/audio as mutually exclusive. A timeline holding both gets a hard error here - core would silently drop the keyframe otherwise.
Reference token hygiene. A shot citing <Picture 1> or <Subject n> when the numbered card doesn't exist, or when the file behind it isn't on this machine.
Missing files. The editor marks a missing file in the browser, but a queue from another tab, the API, or a workflow loaded after you moved a folder never sees that. The node validates it before a single frame is sampled - a message on the node instead of a FileNotFoundError stack trace that names eleven files at once.
Frame lattice and camera-vocabulary slips. Durations that miss H3's length % 17 == 5 rule, and camera moves that don't match the vocabulary H3 was trained on.

Inputs and outputs

One input, no outputs, output node by design:

source - a STRING, always the director's report output. Display-only; there's nothing to wire downstream.

That's it. Misconfiguration is basically impossible beyond wiring it to a non-report string.

Installing it

No separate install - it ships inside ComfyUI-MiniMaxDirector:

cd ComfyUI/custom_nodes
git clone https://github.com/imbutus/ComfyUI-MiniMaxDirector.git

restart, then load the shipped examples/minimax-director.json, which wires the director's report output here for you. The node itself needs no models.

When to trust it

Treat this as your first stop, not your last. The README says it plainly: almost every "why did it do that" is answered by the report and the prompt panels together. What the linter won't tell you is everything the guides don't state - aesthetic judgment, whether the motion will actually look good, whether the fast-motion shot is beyond the 4-step Turbo LoRA's v0.1 limits. It catches structural errors and format violations; it can't save you from an uninspired shot list. Read the report, fix what it flags, and save your render budget for the choices only you can make.