ComfyUI_MiniMax_H3_Extender README

The project's README from github.com/tritant/ComfyUI_MiniMax_H3_Extender. As one markdown file: README.md.

ComfyUI MiniMax H3 Extender

A ComfyUI custom node for MiniMax H3 designed to generate long, continuous video sequences from multiple clips while preserving motion, visual continuity, and audio continuity between generations.

The node combines Ref2VA conditioning, Motion Context, disk caching, multi-clip generation, image references, audio references, and final video/audio decoding into a much simpler workflow.


🆕 Per-Clip Local References

Ref2VA clips can now use their own local Picture, Video and Audio references in addition to the existing global references.

Each clip gets a compact Refs panel where local references can be added, removed and previewed without cluttering the main card UI.

Local references use the normal H3 slot numbering and share the same limits as global references:

Global references remain global exactly as before. Local references simply use the next available slots for that clip.

If a slot is already used locally, the matching global slot is automatically reserved to avoid conflicts. References coming from a Ref Pack are also handled safely without remapping or blocking generation.

Local Pictures can be edited with the same image editor as global references, and local Video/Audio references include compact preview players directly inside the Refs panel.

All local references are fully included in Project Save/Load, so they are restored automatically with the project.


🆕 Full Batch: Interrupt, Save & Resume

Full Batch workflows are now much safer and easier to manage.

You can interrupt a long Full Batch, keep the clips that are already computed, save the project, close ComfyUI, reload it later, and resume from where you stopped without losing completed work.

This also works with project Save/Load, so long generations can now be split across multiple sessions instead of needing to finish in one run.

Available for both Ref2VA and FL2VA.


🆕 News — Dynamic FL2VA Guides & Native VIDEO Output

🎯 Dynamic Image Guides for FL2VA

FL2VA clips can now use up to 3 independent image guides, each placed at an exact frame_idx.

This is based on ComfyUI's native MiniMaxH3AddGuide support introduced in PR #15439.

You can now build a real visual timeline inside a single generation:

First → Guide 1 → Guide 2 → Guide 3 → Last

MiniMax H3 automatically generates the transitions between these visual anchors, opening the door to controlled transformations, pose changes, camera evolution, action staging and much more.

🎬 Native VIDEO Output

The Final Decode / Preview node now exposes a native ComfyUI VIDEO output.

This makes it possible to connect the final result directly to compatible video nodes such as upscalers, post-processing pipelines and video encoders, without having to reload the generated MP4 manually.


🚀 MiniMax H3 Extender 2.0.0

Version 2.0.0 is now available!

This release introduces FL2VA support

It also includes major speed and memory optimizations, with reduced RAM/VRAM usage, faster continuity handling, smoother preview behavior, and improved performance on longer projects.

Project save/load, preview restoration, clip continuity, and overall stability have also been improved.

MiniMax H3 Extender 2.0.0 is now the new base for the project.

Thanks to everyone testing, reporting issues, and helping improve the extension ❤️


🎛️ New — Per-Clip LoRAs

Each clip card can now use its own LoRA.

This makes it possible to change style, motion or behavior from one clip to another while keeping the Extender’s normal continuity workflow.


🎬 New — Video & Audio References for MiniMax H3

The Extender now supports MiniMax H3 video references directly inside the workflow.

You can now use external video frames as <Video N> references, combine them with image references, and optionally attach the matching video audio for motion, timing, camera behavior and lip-sync guidance.

What’s new

Automatic FPS correction

MiniMax H3 expects reference-video frames at 24 fps, but real source videos can be 23.976, 25, 30, 45, 50, 60 fps, etc.

The Extender now accepts the original source FPS through:

The reference-video frame batch is then automatically resampled to 24 fps while preserving the original duration before it is sent to H3.

This fixes cases where the end of a reference video appeared to be missing because a non-24-fps image batch was previously interpreted as if it were already 24 fps.

Typical workflow:

Load Video
   ↓
Get Video Components
   ├── images → ref_video_1
   ├── fps    → ref_video_fps_1
   └── audio  → ref_video_audio_1

Character replacement

Video references can be combined with image references for workflows such as:

For example:

This keeps the Extender’s existing internal image-reference system fully intact while adding proper H3 Ref2VA video/audio support.

Added support for an external prompt pack through the new MiniMax H3 Prompt Pack Bridge node.

Reference Pack Bridge

A new node MiniMax H3 Reference Pack Bridge has been added.

This allows external ComfyUI IMAGE outputs to be injected directly into the Extender’s existing internal reference slots, while keeping the current internal reference system fully intact.

You can now mix both approaches in the same workflow:

The Bridge is optional and does not replace the current reference workflow. It simply adds a flexible external entry point for advanced ComfyUI pipelines.

🎬 Save Preview

The Final Decode / Preview node now includes a dedicated Save Preview button.

It saves the currently assembled Extender preview exactly as shown, including:

The saved MP4 can be dragged back into ComfyUI to restore the workflow.

🎨 Real-Time Per-Clip Color Editor

Each generated clip now has its own color editor, accessible directly from the clip card with the 🎨 button.

You can adjust:

The editor provides a live looping preview around the selected clip, including a short part of the previous and next clips, making it much easier to visually match colors between continuations.

Corrections are:

Color correction is applied only to the decoded video and does not modify Motion Context, latent data or clip validation.

A small ✓ next to the palette indicates that a clip has an active color correction.

⚡ Full Batch Integration

Full Batch correctly preserves and applies all previously configured clip corrections during final assembly.

You can therefore:

  1. Generate several clips
  2. Color-correct individual clips
  3. Continue generating additional clips
  4. Run Full Batch
  5. Obtain the complete sequence with all previous adjustments preserved

💾 Save / Load Project

Per-clip color adjustments are stored inside .ext projects.

Loading a project restores the clip settings and color correction state, allowing you to continue exactly where you stopped.


https://github.com/user-attachments/assets/a18cc6a5-2340-474e-9d3b-b784cd41584a

Capture d'écran 2026-08-31 010245 Capture d'écran 2026-08-29 141350 image Capture d'écran 2026-08-20 062155 image image image Capture d'écran 2026-08-15 083401

Keeping References Consistent Across Clips

When using image references, it is strongly recommended to place a subject_definitions block at the beginning of every clip prompt.

This helps MiniMax H3 keep the same subjects, identities, clothing, visual roles and even the environment associated with a reference image from one clip to the next.

Example

subject_definitions:
<Picture 1> is the reference image defining the exact visual appearance, identity, face, hairstyle, body proportions, clothing, accessories, and overall look of <Subject 1>, as well as the established environment and visual context of the scene.
<Picture 2> is the reference image defining the exact visual appearance, identity, face, hairstyle, body proportions, clothing, accessories, and overall look of <Subject 2>.
<Subject 1> is the exact same woman shown in <Picture 1>.
<Subject 2> is her friend, the exact same woman shown in <Picture 2>.
<Subject 3> is the same street environment and scene context established in <Picture 1>.

Place this subject_definitions block at the very beginning of every clip prompt.

The important point is that a reference image does not have to represent only a character.

A reference can also define the environment, location or visual context of the sequence.

In the example above:

So the same reference image can be used both to preserve a character and to preserve the environment established by that image.

Repeating these definitions at the beginning of each clip prompt helps MiniMax H3 maintain the intended reference roles throughout the entire sequence.


Features


Clip Validation

Each clip has a Validated checkbox.

The validation system allows you to progressively build a long sequence without regenerating clips that have already been accepted.

When a clip is validated:

A typical workflow is:

Clip 1 → Generate
Clip 1 → Validate

Clip 2 → Generate
Clip 2 → Retry if needed
Clip 2 → Validate

Clip 3 → Generate
Clip 3 → Retry if needed
Clip 3 → Validate

This makes it possible to build a sequence one clip at a time while preserving all previously accepted generations.

Validation always forms a continuous chain from the beginning of the sequence.

For example:

Clip 1 ✅
Clip 2 ✅
Clip 3 ⬜
Clip 4 ⬜

If an earlier clip is unvalidated, every clip after it is automatically unvalidated as well, because each continuation depends on the previous generated clip.

Changing a generation parameter also invalidates the sequence when necessary. This includes changes to:

The affected clip and all dependent clips after it must then be regenerated.

In clip_by_clip mode, the Extender works on the first unvalidated clip in the sequence.

The intended workflow is therefore:

Generate → Preview → Retry if needed → Validate → Continue

This allows long MiniMax H3 sequences to be created progressively without repeatedly regenerating clips that are already approved.


Installation

ComfyUI Manager

Search for:

MiniMax H3 Extender

and install it directly from ComfyUI Manager.

Manual Installation

Open a terminal in:

ComfyUI/custom_nodes/

Then run:

git clone https://github.com/tritant/ComfyUI_MiniMax_H3_Extender.git

Restart ComfyUI after installation.

ℹ️ About the old Disk Join nodes

The old low-level Motion Context Disk Join workflow is now considered deprecated and is no longer actively maintained.

New workflows should use the main MiniMax H3 Extender node, which now handles cache management, references, trimming, validation, preview, seam correction, project Save/Load, color correction and final assembly internally.


Thanks again to everyone testing the node and reporting edge cases.

The Extender is becoming much more comfortable to use for long H3 sequences.

ComfyUI_MiniMax_H3_Extender (tritant/ComfyUI_MiniMax_H3_Extender)

Searching Database…

What is this?It's a ComfyUI custom node for the MiniMax H3 video model: it chains multiple generated clips into one long sequence while preserving motion, visual and audio continuity across clip boundaries.
So this isn't a standalone video app — where does it live?It's a plugin inside ComfyUI, not a standalone app. You build a workflow from its clip cards, reference panels and a Final Decode/Preview node, all wired together in the normal ComfyUI node graph.
How do I get it into ComfyUI?Install it like any ComfyUI custom node: clone this repository into ComfyUI's custom_nodes folder, restart ComfyUI, and add the Extender node to your workflow.
Does it work on its own, or do I need MiniMax H3 set up first?You need ComfyUI with MiniMax H3 available — the node orchestrates H3 generation rather than being a model itself. Reference images, videos, audio and LoRAs are optional inputs you attach in the workflow.
If I generate clips one after another, will they actually blend together?Yes — Motion Context and video/audio latent continuity carry over between clips, and the final soundtrack is rebuilt from PCM once at the end, with gain matching and declicking to hide the joins. For visual consistency, README advises starting every clip prompt with a subjectdefinitions block describing your references.
How heavy is this on RAM and VRAM?No hardware requirements are listed, but version 2.0.0 brought major speed and memory optimizations with reduced RAM/VRAM usage, smoother previews and better performance on longer projects.
Can it drop a new character into an existing performance?Yes — pair an image reference defining the new character with a video reference carrying the original motion, timing and camera behavior, plus the matching video audio for lip-sync. README names character replacement, motion transfer, pose transfer and camera-motion transfer as intended uses.
My reference videos aren't 24 fps — do I need to convert them first?No. Pass the source FPS through the refvideofps inputs (23.976 to 60 fps work) and the node resamples the frames to the 24 fps H3 expects while preserving the original duration.
Clips come out slightly different in color — can I fix that in the node?Each clip card has a color editor for saturation, contrast and brightness, with a live looping preview that includes part of the neighboring clips. Corrections are non-destructive, stored per clip in the project, and applied in Preview, Full Batch and Save Preview.
Creator
tritant
Size
0.7 MB
Stars
338
Age
2mo
Commits · 90 Days