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

2.6.0 — the extend take: one prompt, one continuous speech, as long as you wantType a length. Get a take. Set <code>take_seconds</code> on MASTER CONTROLS (or open H3_Extend_Take, now the main workflow, shipped at 1280x736 with a 30-second take), give the writer one premise, queue. Guides: <a target="_blank" rel="ugc" href="https://civitai.com/articles/34047/make-talking-videos-with-minimax-h3-the-5-minute-guide-26">the 5-minute guide</a> and <a target="_blank" rel="ugc" href="https://civitai.com/articles/34046/every-setting-explained-the-seamless-chain-deep-manual">every setting explained</a>. The panel sizes a window for your card (<code>window = auto</code> - wire the loader's MODEL into the panel for a real weight size) and the number of windows that fills the time. The writer's new extend take join style writes ONE continuous speech and cuts it across the windows at sentence boundaries - no airlock, no settle, no per-shot dialogue budget. The chain continues it under <code>context_pin</code> in H3's own voice. No TTS.Verified before shipping: seven writer-driven renders on a 32 GB card at 141/192/243-frame windows plus a 65-second, seven-window take - every join continued the speech, zero repeats, zero clipped words, reviewed blind as one uninterrupted take. Dead air at a join turned out to be a word-fill problem, not a join problem: the writer now aims for the upper half of each window's word budget (measured: 11 words in a 10-second window left a 5-second hole; the same config after the steer, 1.8 seconds).Known limit in 2.6.0: the chain's texture ratchet is not fully solved for long takes - we measure about +13% fine texture per join at 736x1280 with every anti-drift setting on. Under about 4 windows (30-40 seconds) it is slight; at 7 windows it is visible sharpening. Keep extend takes to about 4 windows for now; a fix is in progress.<ul><li>Auto refs now reach the sampler on their own. The REFERENCE IMAGES lane had two switches in series - USE AUTO REFS, and a REFERENCE gate downstream that silently threw the auto refs away unless you also flipped it (the log said "3 ref(s)" and the character rendered from prose alone). USE AUTO REFS alone is enough now; the gate is the MANUAL REFS gate and only guards the two LoadImage slots. Proof line in the log: "N reference image(s) ride in every shot".</li><li>The writer no longer overrides your reference photographs. Same seed, photographs attached: the writer's identity sentence ("a woman in her thirties with dark hair tied back") rendered that person; the same prompt with the sentence replaced by "looks exactly as in the reference photographs" rendered the person in the photographs. The writer has a refs_attached input, wired from USE AUTO REFS in the shipped canvases; when on it points at the photos and describes nothing about face, hair, age or build.</li><li>Saved 2.5.x canvases keep working: the VRAM / SPEED panel dropped its five dead toggles but keeps all eight output slots in the original order (saved graphs link by slot number); the removed slots always emit false.</li><li><code>take_seconds = 0</code> (the default) is exactly the old behaviour; saved workflows are unaffected.</li><li><code>audio_pin_frames</code> on the memory sampler: the audio reference window independent of the picture pin (96 = a 4-second audio memory; measured neutral so far, ships 0).</li><li>Reserve-planning fixes from the 24 GB test lab: no more phantom x1.6 on CORE-workflow reserves; first runs borrow measurements only from the same quant family (GGUF figures do not transfer to w4a8/int8); streamed masters embed the real graph again.</li><li>Writer fix: a silent shot whose boilerplate mentioned lip movement, with a voice anchor in the chain, could re-speak an earlier line. Fixed at the source, and the writer now warns by shot number.</li></ul>2.5 — the memory releaseFour new memory systems, all measured, two of them fully automatic. If renders have ever randomly crawled, if a long chain has ever killed your machine at the final join, or if the text encoder's 15 GB has ever been the difference between fitting and not — this release is about you.New: the random-slowdown fix (automatic)The single biggest fix this pack has shipped. High-resolution renders would randomly take anywhere from 27 minutes to 3 hours for identical work — same seed, same settings, a lottery. The cause: when the model weights plus working memory fill the card past roughly 95%, the Windows driver starts quietly demoting GPU memory, and whether your render crawled was luck.The pack now detects that zone before sampling and deliberately streams a few GB of weights instead of riding the ceiling — streamed weights are nearly free on modern ComfyUI, the last few percent of VRAM are not. The lottery render became 15 minutes, every time. Nothing to configure; the console prints a "driver headroom" line whenever it saves you.New: <code>low_ram_master</code> — long chains without the system-RAM cliffOff (the default), every finished shot is held in system RAM until the final join — historically the point where long renders killed whole machines, after all the sampling was already paid for. Switch it ON and each shot streams to lossless disk staging as it finishes; the master is assembled from disk through the exact same levelling math. Verified at 42.8 dB against the in-RAM path, which is codec noise. Peak RAM stays near two shots no matter how long the chain is. Turn it on if you chain long or run under 32 GB of system RAM. The finished file's path comes out of the new <code>master_path</code> output either way.New: remote text encoder — the 15 GB your render card never neededThe text encoder works for a few seconds per shot and occupies 15+ GB the rest of the time. If you have any second PC with ComfyUI: install this pack on it, point the new H3 Remote Text Encoder node at it, turn <code>remote_encoder</code> ON in the VRAM / SPEED SWITCHES panel, and prompts are encoded over there while your render card keeps the memory. Results are identical — verified across two different machines to float precision — and repeated scene text is answered from a local cache with no network call at all. It ships wired into the full workflow; the panel flag defaults OFF, so single-PC setups see zero change. A how-to note sits right next to the node.New: <code>H3 TAE Decode</code> — 2-second draft previewsA 9 MB tiny decoder (Kijai's <code>taeh3</code>, one small download into <code>models/vae_approx/</code>) turns latents into full-resolution draft frames in about 2 seconds, versus roughly a minute per shot through the real VAE. Drafts smear fine texture, but composition, framing and motion read clearly. Use it to audition seeds or triage a batch, then decode the keepers through the real VAE. Never for finals.New: the Speed Boosters panel — every option, measured, with the honest verdictsSpectrum, TeaCache, block cache and ComfyUI's own EasyCache, each behind a switch on one node. All measured on the same seed, and all eye-tested on the same finished videos:<ul><li>block cache: no effect at 14 steps — 0 cache hits on every run on two cards (the earlier -11% did not reproduce). Ships OFF; only worth it at 30+ steps.</li><li>Spectrum: -29%, but visible distortion on people. Rooms and environments were fine.</li><li>TeaCache: -14% to -21% depending on strength, same story — people distort, environments hold.</li><li>EasyCache (built into ComfyUI, nothing to install): -21%, same family of people distortion.</li><li>Stacking Spectrum + TeaCache: no faster than Spectrum alone and severely damaged output. Never stack them.</li></ul>If your scene has no people in it, the aggressive boosters are real money. If it has people, leave them all off. A booster whose pack is not installed prints an install link and passes the model through unchanged — it no longer breaks the graph.Changed: defaults tuned for 16-24 GB cards736x1280 at 192 frames and 14 steps, <code>euler</code>/<code>beta57</code>, the <code>curve-Q5_1</code> checkpoint (~14 GB), and the full anti-drift set on: <code>context_pin</code>, <code>chain_gain_control=flatten</code>, <code>master_normalize=luma+contrast</code>, <code>pin_renorm</code>, <code>memory_frames=0</code>. The resolution floor is deliberate — the base model distorts faces below roughly 1 megapixel, so shrinking the canvas to save VRAM costs you faces first.Changed: the writer now knows how long a shot really isChained shots spend about five seconds of every block on the replay, airlock and settle, so the speakable span is shorter than the clip. The prompt writer now receives that real span and sizes every line against it, and overruns or fully-silent scripts are flagged at generation time with the numbers. Measured on renders: lines over budget garble, lines under budget drag, matched budgets came back natural and fully intelligible.Changed: writer craft rules learned from failed renders<ul><li>Silent shots with visible people now state what mouths are doing — stops the model inventing mumbling.</li><li>Things revealed mid-shot are written as already present — stops pop-ins.</li><li>A shot that opens a mouth without dialogue must name the sound it makes.</li></ul>New: clickable title blocksEvery workflow now carries its version number and live links to the GitHub repo, the HuggingFace page and this page, plus a plain-language pass over every on-canvas note. If you have ever wondered which version of a workflow you had open — that is over.Every new control in this release is appended at the end of its node's input list, so workflows you saved against 2.2.x load unchanged.

minimaxH3MultishotSeamlessChain_v26ExtendTake.zip

v2.6 Extend Take

v2.6.3

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

v2.0 - Seamless Chain

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: fc18f08a7d26d0bcfc56741c37f865de3fb2732294aabe900b905651b478cb33