MiniMax-H3 Multishot — Seamless Chain: multi-shot scenes that render as one continuous take (picture + audio)

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:<ul><li>☕ <a target="_blank" rel="ugc" href="https://ko-fi.com/joeygambino">Buy me a coffee on Ko-fi</a></li><li>💛 <a target="_blank" rel="ugc" href="https://github.com/sponsors/jlucasmcrell">Sponsor on GitHub</a></li><li>🔁 <a target="_blank" rel="ugc" href="https://liberapay.com/joeygambino">Liberapay</a> (recurring)</li></ul>⚡ Or right here: the Civitai tip button on this page sends Buzz directly The joins are gone. Two independent video-understanding models were shown a four-shot chain from this version, blind and with no context. Both described it as one continuous unedited take - no cuts, colour consistent, audio unbroken.That is the whole point of 2.0. Everything below is either what made it possible or what got cleaned up on the way.A second way to join shotsChaining used to mean handing the next shot the previous shot's last frame. That still works, is still shipped, and is still what the CORE workflow uses. 2.0 adds <code>continuity = context_pin</code>, which is a different mechanism entirely.The previous shot's last 22 frames ride into the next shot as raw latents - bit-identical, never decoded to pixels and re-encoded - placed at interior keyframe coordinates, with a timeline-placed audio reference alongside them. The regenerated head is trimmed on decode. Colour, motion and voice cross the boundary as data instead of as a description, which is why the join stops being a place where things can drift.This mode needs the ComfyUI-H3-Motion-Context pack. Without it, set <code>continuity</code> to <code>first_frame</code> - the model's own trained hand-off, no extra install, and what the CORE workflow ships with.Seam audio that stops eating wordsThe boundary audio cut used to land blindly at the start of the incoming shot, which shaved the attack off any word the model happened to place there - audible as a tiny blip at a join. It now lands in the quietest gap within the shot's first 0.75 seconds, then welds with the same 40 ms equal-power crossfade. A line that begins early survives intact.Voice and identity anchors, on the chaining samplerThe memory-bank sampler now takes the same anchor inputs the single-shot sampler always had: <code>reference_images</code>, <code>voice_ref</code>, <code>self_anchor_voice</code>, <code>reference_image_size</code>, <code>preview_first_shot</code>, <code>two_pass_upscale</code> and its three dials, plus <code>sampler_override</code> / <code>scheduler_override</code> so one master panel can drive the sampler and scheduler by name.The bank already carried voice - each slot is a video reference with the audio under it - but only from shot 2 onward, because shot 1 renders against an empty bank. <code>self_anchor_voice</code> closes that gap: shot 1's own rendered voice becomes <code>&lt;Audio 1&gt;</code> for every later shot. Operator-supplied references are placed ahead of the bank slots, so <code>&lt;Picture n&gt;</code> and <code>&lt;Audio n&gt;</code> numbering stays fixed as the bank fills and a prompt's bindings cannot drift mid-chain.Two-pass upscale cannot be combined with <code>continuity = context_pin</code> or <code>latent_handoff</code>, or with an audio spine. Those carry the previous shot's raw latents - or one locked denoise trajectory - across the join, and a two-pass render preserves neither. The node stops with an error naming the conflict rather than quietly producing a weaker join. Two-pass is available on <code>cut</code>, <code>seamless</code>, <code>seamless_tail</code>, <code>first_frame</code> and <code>flf_chain</code>.A VRAM and speed panelOne panel, three lazily gated model patches - memory-efficient attention, chunked feed-forward, and a block cache - plus an activation-reserve control. Every switch off reproduces the shipped recipe exactly, and a gate that is off means the patch node never executes at all, so there is no cost to leaving them alone.And a reserve that understands payloadMemory measurements are now keyed by shape and conditioning payload, so a bare first shot and a reference-laden later shot no longer share one estimate. Measured pools are no longer overridden by a fixed floor, an unseen payload variant estimates from a measured sibling, and a spill into system RAM is now detected and named in the console rather than presenting as an unexplained five-times slowdown with nothing in the log.The writer knows the join rules nowThe LLM prompt writer gained a <code>join_style</code> control. Set it to a chained style and the render-verified boundary rules are appended to its system prompt automatically - open each shot holding the previous shot's closing arrangement, land settled, never straddle a line across a boundary, repeat every description verbatim. Generated scripts obey them without you memorising anything. Hand-written scripts still need to follow them; they are documented in <code>PROMPTING.md</code> with a worked four-shot example.Three workflows instead of five<ul><li>H3_Seamless_Chain_v2 - everything, with the optional lanes gated off by default: master controls, LLM writer, VRAM panel, identity and voice anchors, an episode/batch prompt source, FFLF boundary plates, and an audio spine.</li><li>H3_Seamless_Chain_CORE - the same job with zero third-party packs. Type shots into the script box and queue. Start here.</li><li>H3_Keyframes - unchanged, and still its own thing: single clip, anchors at chosen frame positions, per-anchor condition strength.</li></ul><code>H3_Multishot_AIO</code> and <code>H3_Multishot_MEMORY</code> retire. Every lane they had is in v2 - the AIO's episode source, plate chain and audio spine were folded in, and MEMORY had nothing v2 lacks. Your existing copies keep working; there is just no longer a reason to open them.Smaller things that were worth fixing<ul><li><code>flf_chain</code> selected with no boundary plates wired now stops with a clear error instead of quietly rendering an unanchored chain.</li><li>Interior keyframe anchoring and the Motion Context pack no longer fight over the same patch site. If that pack is installed it owns the site and this one stands down with a line in the log; if it is not, this one fills the gap. First and last anchors work either way.</li><li>GGUF vision sidecars can be named explicitly. ComfyUI-GGUF pairs the <code>-mmproj</code> file to a GGUF text encoder by filename, in the encoder's own folder only - rename either, or split them up, and it loads the encoder without its vision tower, which presents as the model ignoring your reference image. This pack's CLIP loader now raises instead of continuing blind, uses the only mmproj beside the encoder when there is exactly one, and takes an <code>mmproj_name</code> widget so you can point at the file directly - so the filename rule documented on the encoder listing stops being something you have to obey.</li><li>The pack now imports defensively - one module failing no longer takes every node in the pack down with it.</li></ul>Shipped defaults<code>ref2va</code> checkpoint, <code>continuity = context_pin</code>, voice self-anchor and the identity bank on, <code>euler</code> + <code>beta57</code>, 14 steps, 362 frames per shot (~15.1s), 24 fps, every VRAM switch off.Blind review ran on the lighter configuration - <code>fl2va</code>, no voice anchor - which is the same chaining mechanism with fewer reference rows. <code>ref2va</code> ships as the default because it makes voice and character identity explicit rather than emergent; switching to the reviewed path is two changes, documented in <code>SETTINGS.md</code>.Honest limits<ul><li>Audio dulls slightly per hop on very long chains - restart the chain on a scene cut, where a fresh start costs nothing.</li><li>Resolution cannot change mid-chain.</li><li><code>flf_chain</code> has not been rendered against a fully colour-matched plate set.</li><li>Two-pass upscale is off by default and excluded from the raw-latent continuity modes (above), so the seamless chain has no built-in upscale path yet. Upscale after the fact, outside the graph.</li><li>Keep the mux at 24 fps. Other rates audibly shift voice accents; that is the model's audio lane, not the muxing.</li></ul>

minimaxH3MultishotSeamlessChain_v20SeamlessChain.zip

v2.0 - Seamless Chain

v.2.2.5

v2.2.4 Multi-Ref+Vid-Ref

v2.2.3 More Mem Fix

v2.2.2 - Glasses?

v2.2.1 - Bugfix

v2.2 - Big Update

v2.1.2

v2.1.1

v2.1 Bugs in my bugfixes

v1.5 Auto-Voice Ref+LoRAs

v1.4.1 - Bugfix release

v1.4

v1.3

v1.2.1

v1.2

v1.1

v1.0

Files with SHA256: 74bab24923629ac66d21a8431422918ca0f2c7fe146e0079bf6b46e26605add4