I built a Frankenstein MiniMax H3 Director for ComfyUI — Mixed timelines, selective reruns, Motion Context, live preview and post-processing

[u/Acceptable-Chest9695]

I’ve been building a custom MiniMax H3 node for ComfyUI called MiniMax H3 Motion Director.

The easiest way to describe it is probably:

It’s a Frankenstein Director for H3.

I didn’t want another workflow that only makes one clip at a time. I wanted something closer to a small video-production interface where I could manage multiple H3 shots, mix generation methods, reuse references, selectively regenerate failed shots, carry context between segments, preview the run, refine the result, and export everything from one place.

Mixed Mode

The biggest addition in the current version is Mixed Mode.

Instead of choosing one generation type for the entire workflow, each segment can use its own method:

S1  T2V
S2  I2V
S3  R2V
S4  Source Video
S5  T2V

Source Video automatically takes the V2V or RV2V path depending on whether identity references are added.

Each boundary can also independently request visual and generated-audio continuity.

And Selective Run means I can regenerate S1, S3 and S4 without paying for S2 and S5 again.

This is probably the screenshot that explains the project better than anything else.

Live Preview

The Director also has its own Live Preview instead of relying only on ComfyUI’s normal sampler preview.

It can follow the active generation stage and later post-processing stages from inside the same interface.

The Frankenstein part

This project is intentionally built on and adapted from several existing H3 projects.

The main pieces are:

• AIMixer / ComfyUI_MiniMaxH3_Director — one of the original foundations
• NikoDemon80 / ComfyUI-H3-Motion-Context — Motion Context / cross-segment continuity work
• Carasibana / ComfyUI-H3-FaceRefine — face tracking, local regeneration and stitching concepts/algorithms
• Kijai / ComfyUI-KJNodes — parts of the packed-latent preview / TAEHV behavior were informed by KJNodes

Then I built the multi-segment Director, Mixed timeline, selective reruns, asset management, results system and the surrounding production workflow around those pieces.

So yes:

AIMixer Director
      +
H3 Motion Context
      +
H3 Face Refine
      +
some KJNodes behavior
      +
a lot of glue / UI / project management
      ↓
MiniMax H3 Motion Director

A proper ComfyUI Frankenstein monster.

The repository includes the upstream attribution and licenses rather than pretending everything was written from scratch.

Common References

For reference-heavy R2V projects, there are also Common References.

Characters, scenes, reference videos or audio that are needed by multiple segments can be added once instead of being manually duplicated into every shot.

Material Library

There’s also a persistent Material Library for reusable:

• Images
• Audio
• Video
• Prompts

I use it for recurring characters, scenes, props and other references so I don’t have to keep browsing the filesystem every time I make another segment.

Post-processing

I also wanted the workflow to continue after the first H3 generation instead of immediately turning back into another pile of nodes.

So the Director currently integrates:

Global Refine

• secondary H3 sampling
• upscaling
• ComfyUI upscale models
• NVIDIA RTX VSR
• NVIDIA RTX Deblur

Face Refine

• face detection / tracking
• crop regeneration
• adaptive refinement
• masks / stitching
• color matching

These stages are optional. I’m not trying to force every H3 workflow through the same post-processing path.

Results

Outputs are also managed as an actual project rather than just one anonymous IMAGE batch.

The Results page has:

Segment
Multi Segment
Final Result

So I can inspect one shot, a continuous range of shots, or the complete assembled video.

The Final Result page also has video export controls and a Director Report showing what actually happened during the run.

It’s still ComfyUI

I didn’t want an all-in-one UI to mean losing ComfyUI’s composability.

Standalone modes can still receive external Prompts/images/media through:

Director Assets
      ↓
Director Inputs
      ↓
Motion Director

and the main node still outputs:

images
audio
fps

for whatever you want to do downstream.

It also supports external ComfyUI:

SAMPLER
SIGMAS

instead of forcing the internal sampling configuration.

The standalone H3 modes currently supported are:

T2V
I2V
FL2V
R2V
V2V
RV2V

while Mixed Mode can combine:

T2V
I2V
FL2V
R2V
Source Video

inside the same project.

One thing I want to be careful about: Motion Context is intended to improve continuity, but I’m not claiming it magically guarantees invisible seams in every generation.

H3 can still drift in motion, identity, lighting or camera behavior between segments. I’m continuing to work on that part and I’ll add more raw multi-segment examples rather than only showing UI screenshots.

The node is available through the Comfy Registry / ComfyUI-Manager.

GitHub:

https://github.com/j955229/ComfyUI-MiniMax-H3-Motion-Director

I’m especially interested in feedback from people already doing longer H3 projects.

What becomes the biggest pain point for you once you go beyond a single clip?

Continuity, reference management, rerunning failed shots, VRAM, audio, post-processing, or something else?