Support
Everything here is free and stays free — the format spec, the nodes, the workflows, the cartridges, the LoRAs. If it saved you a night of debugging (it contains several hundred of mine), tips keep the 5090 warm:
🔁 Liberapay (recurring)
⚡ Or right here: the Civitai tip button on this page sends Buzz directly.
Type a story. Get one continuous video, with sound. Multi-shot scenes render as a single take - no last-frame chaining, no quality loss from shot to shot. That's the whole pitch.
Both workflows now read left to right: numbered lanes, and you only ever touch lanes 2-4. Everything below the main row is optional.
What you need
ComfyUI + this node pack (Manager: MiniMax-H3 Multishot, or the zip on this version).
A MiniMax-H3 checkpoint (links on this page). 24 GB card? Take a GGUF.
SEAMLESS CHAIN - multi-shot scenes as one take
Lane by lane:
README - the quick start lives on the canvas itself.
1 - MODELS - pick your H3 checkpoint and text encoder. VAEs are preset; LoRA slots are empty until you fill one.
2 - ANCHORS (optional) - a photo to open shot 1 on (enable its gate), and a short voice clip to lock the speaker's voice.
3 - YOUR PROMPTS - type your idea in the box, or point the switch at a prompt file. The writer expands it into shot prompts. Writing your own? Set the writer to
passthrough (raw JSON, skip LLM)and paste shots separated by---lines.4 - CONTROLS - size, frames per shot, steps, and
take_seconds(total length; 30 is a good first run). The switches stay off unless you installed the pack a switch names.5 - ENGINE - nothing to change. The remote encoder lives here if you want the text encoder on a second PC: enter its address, flip the encoder switch, free ~15 GB.
6 - OUTPUT - your video and its audio save here.
Optional panels below the main row: reference images (your character, ref2va checkpoints - folder per character + AUTO REFS on), V2V reference (a clip whose look guides the render), FFLF plates (flf_chain mode only), audio spine (a soundtrack the take follows).
EXTEND TAKE - one person talking, as long as you want
Same lanes, different job: one premise becomes ONE continuous speech cut across windows.
1 - MODELS - same as above.
2 - ANCHORS - a photo of your speaker (shot 1 opens on them) and a voice clip. More useful here than anywhere: one person carries the whole take.
3 - YOUR PROMPT - ONE premise, one speaker. The writer writes the whole speech. num_shots 0 = it decides. Passthrough works here too.
4 - CONTROLS -
take_secondsis the star: 30 ships, 60 clears TikTok's minute.windowstays on auto - it sizes itself to your card.5 - ENGINE / 6 - OUTPUT - same as above.
Keep takes to about 4 windows for now - very long takes slowly sharpen.
Rules of thumb (both workflows)
Spoken lines: 8-12 words per shot. Short lines sync; long lines garble.
Say the sounds you want ("rain on the roof, a fridge hum") or it invents its own.
Keep your character's face in frame - faces carry identity between shots.
If something breaks
Red node? Update the pack in Manager, restart, reload the workflow from disk.
Render crawls at low wattage? Lower resolution or frames per shot, or use the remote encoder.
Only one of the two workflows shows in your sidebar? Fixed in 2.6.5 - re-download both.
Still stuck: comment with your console log. I answer.
Deep dives: the two articles linked on this page. Every lane also has a short note on the canvas.
Detailed guide for people that can read good:
Every setting explained: the Seamless Chain deep manual | Civitai
Description
Sampler and scheduler exposed
Both multishot samplers (H3MultishotSampler and H3MultishotMemorySampler) hardcoded their sampling internally — res_multistep on a simple schedule. Those are now widgets, with exactly those values as the defaults:
Existing workflows render identically. The defaults are the values that were hardcoded, and the new widgets sit at the end of the input list on purpose — ComfyUI stores widget values by position, so putting them anywhere else would silently re-map the saved settings of every workflow you already have.
The option lists come from ComfyUI itself at load time (44 samplers and 9 schedulers on a current build), not from a copied list that goes stale when core adds one.
Bundled workflows relabelled
Every node in the three graphs now carries a descriptive title. The two bare VAELoaders are Video VAE and Audio VAE, reference slots state their <Picture n> binding, the sampler chain is named step by step, and the long-form graph's read-me note no longer sits on top of the model loaders.
No graph wiring, defaults or behaviour changed in this release — v1.4 is control exposure and labelling. If you are exploring samplers: res_multistep is what every measurement on this page was taken with; treat other choices as experiments.
Full contents
H3_Multishot_AIO.json— easy mode: one script to many chained shotsH3_Multishot_MEMORY.json— 2–5 minute pieces with an identity anchorH3_Keyframes.json— anchors at any position, single pass, unbroken audio
FAQ
Comments (12)
hello and thanks for your work. You wrote " RTX 5090: ~60 min → ~15 min ". For wich width/ height and laps of time/frames ?
Good catch - that line's missing its conditions, and now that I've gone back to the logs it's also just not a good pair of numbers.
The real run, pulled from the render's own embedded workflow:
960 x 544, 124 frames (5.2 s at 24 fps), 20 steps
ref2va-Q5_1, one reference image, RTX 5090, --reserve-vram 7
-> 12.3 minutes with the encoder evicted
The un-evicted version I killed somewhere past 90 minutes, so it never finished. That means "~60 min" is a number I don't actually have, and "~15 min" was 12.3 rounded up. I'll fix the model page - thanks for asking instead of trusting it. A properly controlled pair, where both sides ran to completion or a deliberate cut-off (480x864, 124 frames, one reference VIDEO):
no eviction: killed at 46 min, 98% "utilization" at ~172 W
eviction on: 6.5 and 7.7 min on two clean runs, 355-390 W
The thing that matters more than any ratio: this is a cliff, not a curve. The Qwen3-VL encoder is ~16.5 GB even at Q4 and the DiT is ~25 GB, so on a 32 GB card they just don't co-fit. Either the DiT is resident and you get normal speed, or it streams ~19 GB from system RAM every sampling step. How bad it gets depends on how far over your card you are - which is why quoting one speed-up ratio was misleading of me regardless of the numbers.
Two tells. In your log:
loaded partially; 6423 MB usable, 5847 MB loaded, 19363 MB offloaded
and on the card, watch POWER DRAW, not utilization. A GPU thrashing weights between RAM and VRAM still reports ~98% while pulling a fraction of its rated watts. 146-172 W on a 5090 is thrashing; 400 W+ is real work. I chased the utilization number for hours before the wattage told me what was going on. If you're on 24 GB, the curve-form Q8_0 is worth a look - 20 GiB resident on a 3090 with room to spare, 6.8 min for 123 frames, and it's smaller and faster than the original-form Q4_0.
Is it just me that face, eye and lip artifacts have decreased with 1.3? Anyway, great update.
Thank you!
Seen someone mention in discord that heunpp works really well for better audio. But I don't see a way to change it in this node. Have you tried this heunpp?
I will work on exposing the sampler and scheduler in the AIO node for the next version, likely have it up tomorrow.
My experience with heunpp2 has been very positive for audio but it is slow. Very slow. Maybe twice as slow as res_multistep.
@JustTrying2026 v1.4 uploaded with sampler and scheduler exposed
@aikoyama heunpp2 is indeed a bit more than twice as slow as res_multistep, but it definitely results in higher quality generations, at least when it comes to motion artifacts.
@Undecked I am about to tell this myself, along with res_2s. beta57 and/or bong_tangent.
Have you done any testing for taking an existing video and extending it? MiniMax H3 has the capabilities to do so but from my own testing is oftne has issues with audio or color grading. I was wondering if a similar method coould be applied there as well (as in, take an existing video + prompt as as the first 'shot' instead of just an image + prompt)
I have not yet, but I will put it on the list for next workflows!