<h2 id="support">Support</h2>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><li>⚡ Or right here: the Civitai tip button on this page sends Buzz directly.</li></ul>Three ways to drive MiniMax-H3, and a VRAM fix that makes it usable on a 32 GB card. Chain shots from a script into one long piece; pin keyframes anywhere in a clip; or drive identity from reference images, video and voice. All in one node pack, all producing video and audio.<h2 id="keyframes-at-any-position">Keyframes at any position</h2>Stock ComfyUI pins H3 keyframes to the first and last frame only and raises <code>only first/last keyframe anchors are supported</code> for anything else.That is a positional-maths limit, not a model limit. Both stock cases are the same expression, because <code>sum(_video_t_spans(latent_t)) == FRAME_RESCALE * frame_count</code>:<pre><code>cond_t = text_len + FRAME_RESCALE * pixel_index</code></pre>— which is defined for every frame, not just the two endpoints. So you can hand H3 up to six anchor images and say when each one should happen, as fractions (<code>0, 0.5, 1</code>) or absolute frame indices.Measured on an RTX 5090, 243 frames, one anchor at pixel frame 121: the rendered frame most resembling the anchor image was frame 122 — the requested position, off by one — arrived at by continuous motion with no cut (peak frame-to-frame change 2.3× the median), and the audio ran unbroken straight through it. A three-anchor run at 0 / 0.5 / 1 landed the second and third on frames 121 and 242 exactly.The patch is applied in memory — it does not edit any ComfyUI file. It self-tests against the stock formula before committing and rolls itself back if first/last positions do not reproduce exactly, so a future ComfyUI change degrades to “interior anchors unavailable” rather than to broken renders.<h3 id="it-moves-or-it-cuts-and-your-images-decide-which">It moves, or it cuts — and your images decide which</h3>Anchor images with a plausible camera path between them (same place, different angle or framing) make H3 interpolate: a real move that arrives on time. Images with no possible path — a kitchen and a diner — make it cut, then hold.That is the model being sensible, not a limitation of the node: stock first/last does exactly the same thing when given such a pair. And the cut case earns its keep, because it is a timed shot change inside a single generation — one generation means one continuous audio stream, so the voice does not get re-derived and there is no seam to hide.<h3 id="saying-when:-percentages-indices-and-ranges">Saying when: percentages, indices and ranges</h3>Anchor positions take whichever form suits the shot:<pre><code>0%, 50%, 100% percentages
0, 121, 242 absolute frame indices
0-9, 352-361 inclusive ranges
30%-20% descending: reverses that section of the batch</code></pre>Ranges matter when you have a burst of frames rather than a single anchor — several frames clustered at each end to pin a complex move, or a run kept from a source video. For that there is an <code>images_batch</code> input that takes any number of anchors, and it adds to the six individual slots rather than replacing them.Both of those came from @poltergeisha360, who asked for the batch input here on Civitai and then wrote both features and sent pull requests. The percentage syntax also fixes a genuine trap of mine: a bare <code>1</code> used to mean the last frame, not frame 1, so addressing an early frame absolutely meant writing <code>1.0001</code>. Saved workflows keep working — a bare non-integer at or below 1.0 is unambiguous and still reads the old way, while an all-integer <code>0, 1</code> takes the new absolute meaning and logs a warning rather than silently anchoring a different frame.<h3 id="models-in-subfolders-show-up">Models in subfolders show up</h3>Both loaders scan <code>diffusion_models</code> and <code>text_encoders</code> recursively, so a GGUF filed under <code>gguf/</code> appears in the dropdown. It did not before, while ComfyUI-GGUF's own loader listed the same file fine — the scan exists because <code>.gguf</code> is not in ComfyUI's <code>supported_pt_extensions</code>, so the normal file list never returns it.<h2 id="which-workflow">Which workflow</h2><ul><li>A script of several shots, chained into one piece — <code>H3_Multishot_AIO.json</code></li><li>Specific frames at specific times, one continuous take — <code>H3_Keyframes.json</code></li><li>2–5 minutes without identity drifting — <code>H3_Multishot_MEMORY.json</code></li><li>Identity from reference images, video or voice — <a target="_blank" rel="ugc" href="https://civarchive.com/models/2836967">Hard Mode</a>, a separate download</li></ul>Reference-to-video has landed, as its own release: MiniMax-H3 Hard Mode — identity from reference images, video and audio instead of a start frame, up to 9 images, 3 videos, 3 soundtracks and 3 standalone audio clips. It uses this pack's nodes, so install this first. On <a target="_blank" rel="ugc" href="https://huggingface.co/joeygambino/MiniMax-H3-HardMode-Workflow">Hugging Face</a> and <a target="_blank" rel="ugc" href="https://github.com/jlucasmcrell/MiniMax-H3-HardMode-Workflow">GitHub</a>. Also on <a target="_blank" rel="ugc" href="https://civarchive.com/models/2836967">Civitai</a>.References and keyframes are mutually exclusive — worth knowing before you wire the two together. This is ComfyUI core behaviour, not a choice made here: <code>model_base.py</code> assigns <code>cond_video_latents</code> for references, discarding keyframe latents while the keyframe layout rows survive — the packed sequence then desyncs into a shape-mismatch crash. There is no “reference images plus start frame” mode. Pick one per shot.<h2 id="~4-faster-on-32-gb-cards">~4× faster on 32 GB cards</h2>The text encoder is evicted before sampling. The Qwen3-VL encoder (~16.5 GB even at Q4) and the H3 DiT (~25 GB) do not co-fit on a 32 GB card, so the DiT was loading partially and streaming ~19 GB from system RAM on every sampling step. If you have ever seen this in your log:<pre><code>loaded partially; 6423 MB usable, 5847 MB loaded, 19363 MB offloaded</code></pre>that was it. Measured on an RTX 5090 — 960×544, 124 frames, 20 steps, <code>ref2va-Q5_1</code>, one reference image: 12.3 min with the encoder evicted. The un-evicted run of that same render was killed past 90 min without finishing, so there is no honest completion time to quote against it. Every sampler in this pack evicts, including the keyframes node, and prints <code>TE evicted; NN.N GB free for the DiT</code>.Treat this as a cliff, not a curve. The encoder (~16.5 GB at Q4) and the DiT (~25 GB) do not co-fit in 32 GB, so either the DiT is resident and you get normal speed, or it streams ~19 GB every sampling step. The size of the slowdown depends on how far over your card you are, not on resolution or frame count directly — one speed-up ratio would not generalise, so there is not one here.<h2 id="quick-fixes-read-this-first">Quick fixes — read this first</h2><ul><li>Red / missing nodes when a workflow loads Why: pack not installed, or ComfyUI not restarted. Fix: install <a target="_blank" rel="ugc" href="https://github.com/jlucasmcrell/ComfyUI-H3-Multishot">ComfyUI-H3-Multishot</a> (Manager &gt; Install via Git URL), restart, then hard-refresh the browser tab — the frontend caches node definitions.</li><li>GGUF errors with “unknown model architecture” Why: ComfyUI-GGUF does not know MiniMax-H3 out of the box. Fix: run <code>python apply_gguf_arch_patch.py</code> from the pack folder (one line, idempotent), restart. This is for the DiT only — the text encoder is Qwen3-VL and needs no patch. Only want the DiT working? The patch is also downloadable on its own (2 KB) if you are running ComfyUI's built-in MiniMax-H3 nodes with the safetensors encoder and do not need this pack at all. It is included here, so installing this pack is enough.</li><li>Reference audio crashes the sampler with a shape mismatch Why: your clip is mono. The audio VAE encodes <code>[B, 2, L]</code> and the layout reserves exactly two channels, so a mono reference produces half the rows it reserved and dies deep inside the model with no useful message. Nothing in stock converts it. Fix: the H3 Reference Audio node — forces stereo 32 kHz and trims length. It is already wired in the hard-mode workflow.</li><li>The model ignores my reference image Why: reference blocks are labelled in the prompt and the numbering is 1-based while the input slots are 0-based — <code>ref_image_0</code> is <code>&lt;Picture 1&gt;</code>. If you never name it in the text, the model has no reason to bind it. Fix: write <code>&lt;Picture 1&gt; is the woman. &lt;Picture 2&gt; is the room.</code> Note a reference video with a soundtrack consumes an <code>&lt;Audio j&gt;</code> ordinal before your standalone clips.</li><li>Multi-shot ignores my reference image entirely Why: missing <code>mmproj</code>. It is required for chaining, not just for reference images — chaining feeds the previous shot's last frame through the encoder's vision path. Fix: download the <code>-mmproj</code> file alongside the encoder and keep both filenames exactly as downloaded, in the same folder. The loader pairs them by name.</li><li>Length change errors out Why: H3 hard constraint — frame counts live on a 17k+5 grid. Fix: 226, 243, 260… the widget steps by 17 so it keeps you legal. 243 ≈ 10s; 362 ≈ 15s is the trained ceiling.</li><li>Speech turns to gibberish Why: usually an under-filled shot, not an over-long one. Speech runs about 2.5 words/second, so a 243-frame shot wants roughly 22–25 spoken words; give it eight and the model invents sound to fill the dead air. Fix: match dialogue length to shot length, and if you want silence, script it (“she listens, saying nothing”).</li><li>An object morphs into something else at a seam Why: chaining hands each shot the previous final frame. If shot 1 ends on the cameraman holding his camcorder and shot 2 is filmed FROM that camcorder, the model must explain a device in a hand that should not be in frame — so it invents one. Fix: end every shot on what the NEXT shot expects to see.</li><li>Out of VRAM, or renders crawl Why: 33B of weights — and see the eviction section above. Fix: use the GGUFs, Q5_1 for 24–32 GB, Q4_0 for 16 GB. The file does not need to fit in VRAM; ComfyUI streams the overflow. Expect ~10 min per 10s shot on a 5090-class card.</li></ul><h2 id="writing-a-script-this-is-most-of-the-quality">Writing a script — this is most of the quality</h2>The identity lock is description density, not assertion. Every shot is an independent conditioning pass: the model rebuilds the person from your text each time. Writing “the same woman, same face, same wardrobe” asserts continuity without supplying what is needed to rebuild it, and the face drifts. Re-describing 6–8 concrete attributes verbatim in every shot is what actually holds it:<pre><code>She is an attractive American woman in her mid twenties with warm hazel
eyes, a friendly confident smile, light freckles, shoulder-length auburn
hair tucked behind one ear, small gold stud earrings, and a relaxed
sage-green blouse. Her voice is a clear warm young woman's voice in a
casual American accent.</code></pre>Do the same for the voice: one short concrete line, repeated verbatim. Flowing prose beats <code>SHOT:</code> / <code>Audio:</code> labels.<h2 id="what-you-need">What you need</h2><ul><li>ComfyUI v0.30.0+ (native MiniMax H3 support)</li><li>The node pack: <a target="_blank" rel="ugc" href="https://github.com/jlucasmcrell/ComfyUI-H3-Multishot">ComfyUI-H3-Multishot</a></li><li>DiT weights: <a target="_blank" rel="ugc" href="https://civarchive.com/models/2833352">MiniMax-H3 GGUF</a> (or on <a target="_blank" rel="ugc" href="https://huggingface.co/joeygambino/MiniMax-H3-GGUF">Hugging Face</a>) (Q5_1 / Q4_0, both flavours) — or the originals</li><li>Text encoder: <a target="_blank" rel="ugc" href="https://civarchive.com/models/2834385">MiniMax-H3 Text Encoder GGUF</a> (or on <a target="_blank" rel="ugc" href="https://huggingface.co/joeygambino/MiniMax-H3-encoder-GGUF">Hugging Face</a>) — take the mmproj file too</li><li>VAEs: <a target="_blank" rel="ugc" href="https://huggingface.co/Comfy-Org/MiniMax-H3">Comfy-Org/MiniMax-H3</a></li><li>For GGUF: <a target="_blank" rel="ugc" href="https://github.com/city96/ComfyUI-GGUF">ComfyUI-GGUF</a> + the included one-line patch</li></ul><h2 id="a-word-on-expectations">A word on expectations</h2>MiniMax-H3 is a 33B joint audio+video model and this pack started days after the weights landed. It works, and the measurements on this page are from real renders on one consumer GPU — but you may still need to tune to YOUR machine. If you get stuck, comment here or open a GitHub issue. I answer.<h2 id="everything-else-i've-published">Everything else I've published</h2><ul><li><a target="_blank" rel="ugc" href="https://huggingface.co/joeygambino/MiniMax-H3-Multishot-Workflow">This workflow on Hugging Face</a></li><li><a target="_blank" rel="ugc" href="https://github.com/jlucasmcrell/ComfyUI-H3-Multishot">Node pack source on GitHub</a></li><li><a target="_blank" rel="ugc" href="https://huggingface.co/joeygambino">All models on Hugging Face</a></li></ul><h2 id="support">Support</h2>Everything I publish is free and stays free. If it saved you a night of debugging, tips keep the 5090 warm: <a target="_blank" rel="ugc" href="https://ko-fi.com/joeygambino">Ko-fi</a> · <a target="_blank" rel="ugc" href="https://github.com/sponsors/jlucasmcrell">GitHub Sponsors</a> · <a target="_blank" rel="ugc" href="https://liberapay.com/joeygambino">Liberapay</a>.

MiniMax-H3 Multishot — chained shots, one master, with audio

Keyframe positions get percentages and ranges, keyframes take an image batch, and the model loaders stop hiding your GGUFs.Keyframes: image batches, percentages and rangesTwo contributions from <a target="_blank" rel="ugc" href="https://civitai.com/user/poltergeisha360">@poltergeisha360</a>, who asked for the first one here on Civitai and then wrote both himself and sent pull requests (as @viralesveras on GitHub).An <code>images_batch</code> input. Six individual slots runs out quickly if you want several frames clustered at each end to pin complex motion, or a set of frames kept from a source video. The batch takes any number of anchors. Merged with one change: it adds to the six individual slots rather than replacing them — as originally written, wiring <code>image_1</code> and then adding a batch dropped <code>image_1</code> silently.Percentages and inclusive ranges in <code>positions</code>. This fixes a genuine trap of mine: a bare <code>1</code> meant the last frame, not frame 1, so addressing an early frame absolutely meant writing <code>1.0001</code>. That is how the ambiguity got found — in real use.<pre><code>0%, 50%, 100% percentages
0, 121, 242 absolute frame indices
0-9, 352-361 inclusive ranges
30%-20% descending: reverses that section of the batch</code></pre>Your existing workflows keep working. A bare non-integer at or below 1.0 is unambiguous — nobody means "frame index 0.5" — so a saved <code>0, 0.5, 1</code> is still read the old way, and logs the percentage spelling to switch to. An all-integer <code>0, 1</code> is genuinely ambiguous, so it takes the new absolute meaning and warns, rather than silently anchoring a different frame than it used to.Loaders find GGUFs in subfoldersBoth model loaders scanned only the top level of <code>diffusion_models</code> and <code>text_encoders</code>, so anything kept in a <code>gguf/</code> subfolder was invisible in the dropdown — while ComfyUI-GGUF's own loader listed the same files fine. They walk the tree now.If your models showed up on one machine and "disappeared" on another, this was why: the scan exists because <code>.gguf</code> is not in ComfyUI's <code>supported_pt_extensions</code>, so the normal file list never returns it. It just was not recursive.New models: curve-form GGUFs, ~40% smallerNot part of this zip, but worth knowing about — there is now a second DiT repo carrying <code>-curve-</code> files built from MiniMax's pruned checkpoints. About 40% of this model was never unique data: each block carried a 96768×2688 modulation matrix, and those turn out to be a smooth function of the timestep rather than 51 independent tensors.TierCurve formOriginalQ8_021.5 GBnever built — too large to be worth itQ5_115.2 GB25.9 GBQ4_011.5 GB19.9 GBThat Q8_0 is smaller than the Q5_1 that has been shipping since day one, and it fits a 24 GB card. Verified by rendering, same graph and same seed, changing only the model file: swapping to curve form moved the output about a third as far as dropping one quant tier does, with per-frame motion in family. <a target="_blank" rel="ugc" href="https://huggingface.co/joeygambino/MiniMax-H3-curve-GGUF">Files and the full comparison table are on Hugging Face</a> — a separate repo, so the original-form quants stay where they are for anyone on an older ComfyUI or who prefers the larger files.Curve files need ComfyUI 0.30.0+. On older builds they will not load at all, because the shape of the modulation weights changed. The original-form files remain up for anyone pinned to an older version.Full contents<ul><li><code>H3_Multishot_AIO.json</code> — easy mode: one script to many chained shots</li><li><code>H3_Multishot_MEMORY.json</code> — 2–5 minute pieces with an identity anchor</li><li><code>H3_Keyframes.json</code> — anchors at any position, single pass, unbroken audio</li></ul>Every one of those three has a render on disk that its own node produced, verified from the render's embedded graph rather than from the file existing.

Files with SHA256: d840e3c4e4d19e237885a0fb30729bf64b31abfe274329d1acc462a0b6b91340