ComfyUI-MiniMax-H3-LongMedia README

The project's README from github.com/vizart-vj/ComfyUI-MiniMax-H3-LongMedia. As one markdown file: README.md.

ComfyUI-MiniMax-H3-LongMedia

Production-oriented ComfyUI nodes for MiniMax H3 long-form video/audio generation, native reference editing, MultiClip planning, camera direction, fixed segmentation, lip-sync/redubbing, latent hi-res refinement, and adaptive low-VRAM execution.

screenshot

Current release: 0.5.40

Main Nodes

Legacy internal MiniMaxH3LatentLab... class identifiers remain registered for workflow compatibility.

Installation

Install into:

ComfyUI/custom_nodes/ComfyUI-MiniMax-H3-LongMedia

or install the package from the Comfy Registry.

Package identity:

GitHub:             vizart-vj/ComfyUI-MiniMax-H3-LongMedia
Comfy PublisherId:  noise

Restart ComfyUI after installation/update.

Current Setup Model

New workflows use independent semantic controls:

control_mode
h3_mode
timeline_mode
duration_source
audio_mode

This is the main change in how the project should be understood compared with the public 0.4.40 documentation.

See Operating Modes.

H3 Conditioning

t2va
fl2va
ref2va
hybrid
video_ref_edit

Timeline

single
segmented
multiclip

Duration Ownership

auto
video
audio
manual
longest_input

duration_source controls timeline length only. It does not remove audio references or change final-audio policy.

video_ref_edit

Typical source-character replacement:

video_1 = source video frames
image_1 = replacement identity
audio_1 = source soundtrack or new dub

A Video input is an IMAGE batch and never contains soundtrack data.

For preserve-style modes, Video1+Audio1 can be presented as a native paired source-performance reference while Audio1 also owns the target timing/output waveform.

For audio_mode=lip_sync, Audio1 is intentionally independent from Video1's original facial performance so completely new dialogue or singing can drive the replacement character.

Audio2/Audio3 remain prompt-addressable references for music, percussion, bass, ambience, or other semantic timing. In video_ref_edit, they are conditioning references only; Audio1 remains the sole preserved/passthrough source soundtrack.

See Audio Modes and video_ref_edit.

MultiClip + Cameras

Recommended connection:

Long Media Planner
        ↓ clip_plan
Long Media Cameras
        ↓ clip_plan
Long Media Setup

Use:

timeline_mode = multiclip

Planner owns diegetic scene/action prompts, durations, names, and optional seeds. Cameras owns framing, rig/lens, movement, speed, spatial relation, entity continuity, and transitions.

See:

Segmented Long Form

Use:

timeline_mode = segmented

for one continuous semantic movie split into fixed-duration internal units for VRAM/stability. It is not a storyboard scheduler.

See Fixed Segmentation Prompting.

Two-Stage H3 / Latent Hi-Res

The Long Media Sampler can:

  1. generate a low-resolution Stage-1 denoised x0;
  2. learned-upscale the video latent only;
  3. preserve the audio latent;
  4. rebuild target-grid conditioning;
  5. optionally run an independent same-seed fresh-noise high-resolution H3 pass.

Without Latent Hi-Res, the Refiner remains a continuous zero-noise low-sigma tail.

See Two-Stage Sampling, Latent Hi-Res and Refiner.

Sampler / Memory

Production starting point:

sampler_mode   = auto
memory_mode    = auto
attention_mode = auto

Keep ComfyUI Dynamic VRAM enabled.

Current memory-safety work includes exact Comfy Kitchen query streaming for structurally impossible fused-QKV workloads, repeat-run memory isolation, guarded native INT8 VBAR prefetch on constrained GPUs, and RAM-pressure-aware pinned host memory.

See Sampler, VRAM and Performance Guide.

FastH3 / FastVideo VSA

LongMedia includes isolated compatibility paths for supported H3ddle/PulpCut FastH3 VSA and Kijai FastVideo VSA packages.

These paths use strict structural detection and reset their runtime state when switching back to ordinary H3 checkpoints.

Loop Closure

Loop Closure returns the generated tail toward the opening macro-state in latent/H3 space. It is independent from conditioning/timeline mode and does not use an RGB crossfade as its primary mechanism.

Documentation

Start at docs/README.md.

Important guides:

Example Workflows

Release workflows contain neutral media placeholders rather than user media or local preview paths.

See workflows/README.md.

Third-Party Code

This repository contains adapted third-party components under their respective licenses, including:

See THIRD_PARTY_NOTICE.md and THIRD_PARTY_APACHE_2_0.txt.

Release History

0.5.40 is the release consolidation after public v0.4.40.

Historical release notes remain in docs/ for compatibility/reference. They may use the old workflow_mode terminology.

License

See LICENSE.

ComfyUI-MiniMax-H3-LongMedia (vizart-vj/ComfyUI-MiniMax-H3-LongMedia)

memory-management
Searching Database…

What is this?A set of production-oriented custom nodes for ComfyUI that run MiniMax H3 for long-form video and audio generation: reference editing, MultiClip planning, camera direction, fixed segmentation, lip-sync and redubbing, latent hi-res refinement, and low-VRAM-safe execution.
Is this a standalone app or something I add to ComfyUI?It is a plugin, not an app: the nodes are installed into an existing ComfyUI setup (custom_nodes folder or as a package from the Comfy Registry) and then appear as nodes in your workflows.
How do I get it into ComfyUI?Install it into ComfyUI's custom_nodes directory or grab the package from the Comfy Registry, then restart ComfyUI after installing or updating.
What do I need besides the plugin itself?A working ComfyUI installation with an H3 checkpoint to sample from; the README treats ComfyUI's Dynamic VRAM option staying enabled as the production starting point.
Will older 0.4.40 tutorials still apply?Partly: 0.5.x is a consolidation after public 0.4.40, and new workflows use independent semantic controls (Setup, Planner, Cameras, Sampler, Decode nodes), while historical notes may use the old workflowmode terminology.
Do I need a high-end GPU with lots of VRAM?No — constrained GPUs are an explicit target: query streaming for fused-QKV workloads that cannot fit, repeat-run memory isolation, guarded INT8 VBAR prefetch, and RAM-pressure-aware pinned host memory.
What can I actually generate with these nodes?Long-form video with its soundtrack: one continuous movie split into fixed-duration internal units for VRAM and stability, or MultiClip sequences where a Planner owns scene prompts, durations, names and seeds while a Cameras node handles framing, lens, movement and transitions. Loop Closure pulls the generated tail back toward the opening macro-state.
How does the character-replacement lip-sync mode work?In videorefedit modes Video1 and Audio1 can act as a paired source-performance reference while Audio1 still owns the target timing and output waveform. In lipsync mode Audio1 is deliberately independent of the original facial performance, so completely new dialogue or singing can drive the replacement character.
What does the Latent Hi-Res two-stage sampling do?The Long Media Sampler first denoises a low-resolution Stage-1 x0, learned-upsamples the video latent while preserving the audio latent, rebuilds target-grid conditioning, and can optionally run an independent same-seed fresh-noise high-resolution pass; without it the Refiner stays a zero-noise low-sigma tail.
Is there a ready-made workflow to start from?Yes — releases ship example JSON workflows like 'MiniMax-H3-LongMedia-SAFE-1080p-15s.json' (the production starting point) and 'MiniMax-H3-LongMedia-LatentUpscale-Detailer.json', containing neutral media placeholders rather than user media or local preview paths.
Creator
vizart-vj
Size
6.9 MB
Stars
294
Age
2mo
Commits · 90 Days