Sign In

MiniMax-H3 Sections — Unlimited Length, Re-Roll Any Shot

Download

1 variant available

Archive Other

H3_SECTIONS_v1.0.zip

15.7 KB

Verified:

Type
ComfyUI Workflows
Stats

109

Reviews
Published

Aug 21, 2026

Base Model

MiniMax H3

Hash
AutoV2
E2F1E17626
default creator card background decoration
Followers - 2

2

Likes - 7

7

MiniMax H3 is licensed by MiniMax under the MiniMax H3 Community License Agreement. That agreement’s Applicable Territory excludes the European Union, the United Kingdom, the Republic of Korea and the United States of America. Your use of H3 and of any H3 derivative is subject to that agreement and its Acceptable Use Policy.

MiniMax H3

A sectioned film workflow for MiniMax-H3. The film is built as a chain of sections, each one continuing the previous section's motion AND sound, so a character keeps moving and keeps talking across a cut instead of restarting. Add as many sections as your story needs, and re-render any single one without touching the others.

How it works

Each section is a complete render of its own: prompt, seed, steps, length, LoRAs. What connects them is the latent handoff — a section receives the previous section's raw output latents and locks its opening onto them, picture and audio together, then trims the overlap it regenerated. Nothing is decoded and re-encoded between sections, so quality does not degrade along the chain and the sound crosses the join as continuously as the picture.

Because each section is a separate set of nodes rather than one big render, they are cached independently. Change section 4's prompt and queue again: sections 1-3 are already computed and cost nothing, so only 4 onward re-renders. That is the whole reason the workflow is shaped this way. Tuning a long film normally means paying for the entire thing every time you fix one shot; here you pay for the shot you changed and the ones after it.

Six sections ship set up. They are a starting point, not a limit — sections are copies of each other, so you extend the film by copying the last one, retitling it, and redrawing three links. The on/off panel picks up the new section by itself. That is also how the workflow steps past H3's single-pass ceiling of 362 frames: no individual render is longer than the model was trained for, but the film can be as long as you like.

What it is good at

  • Long films with dialogue. Continuous speech across cuts is what this chain does best, and it is what a single long render cannot give you.

  • Iterating cheaply. Re-roll one beat and the rest come back from cache. An assembled film can also be rebuilt in seconds at any point, since assembly does no sampling — useful for watching the story so far while you write.

  • Uneven films. Length, steps, seed and LoRAs are all per-section, so a hero shot can afford 20 steps and a style LoRA while a filler gets 10 and none.

  • Writing rather than wiring. All the prompts sit in one column on the left, one box per beat. You write the film top to bottom and never touch the graph.

  • A light install. No custom nodes ship with this — only the H3 pack you already have and rgthree.

What it does not do yet

Stated plainly, because these are the things you will notice.

  • No audio spine. H3 generates the sound and it carries across joins, but you cannot yet supply your own soundtrack or a voice reference for the chain to lock onto. This is the next thing planned, and it is the biggest gap.

  • Voice drift is unmeasured. The voice is anchored only by your prompt and reference picture, so across many sections it may wander. If it does, the audio spine above is what will fix it.

  • One character. Multiple reference pictures are read as the same person on this path, so two-character scenes are out of reach for now.

  • No global colour matching. Every section renders on the same checkpoint and the joins are latent-continuous, so drift is mild — but there is no pass that levels the whole film's tone at the end.

  • Forward-only. Changing a section makes the sections after it stale, because they were built on its latents. Fix a beat, then re-roll the ones that follow. Never regenerate backwards.

Requirements

  • ComfyUI

  • ComfyUI-H3-Multishot — provides Motion Context and the H3 loaders this workflow is built on

  • rgthree-comfy — the sections on/off panel

  • Models: an H3 ref2va checkpoint (fl2va has no reference rows and will not work here), the H3 text encoder, and both the video and audio VAEs

Quick start

  1. In the GLOBAL group, pick your character picture in CHARACTER REF 1 and unmute that node (Ctrl+M) — a muted node passes nothing, so choosing a file is not enough.

  2. Check WIDTH and HEIGHT. 736x1280 ships; both must be multiples of 32.

  3. Replace the example beats in the PROMPTS column with your own.

  4. Queue. Each section writes its own clip; the FILM group writes the assembled film.

Two rules the on-canvas notes repeat, because both are easy to break by accident: keep every seed's control on 'fixed' — one seed set to 'randomize' re-renders its section and everything after it on every queue — and always regenerate forward, never backward.

Three notes on the canvas cover the rest: first-run steps, what every section holds, and how to add another section. Frame counts follow H3's grid of 17k+5 (90, 107, 124, 141 ... 362) at 24 fps, and sections after the first deliver 22 frames fewer than their length, because the regenerated join is trimmed.