ComfyUI-Hand-Tie-Clips

Hand Tie Clips

Multi-hop MiniMax H3 video from one node. Write a shot plan, drop in your reference stills, queue. The pack's whole job is the join — the place where one generation ends and the next begins.

Six consecutive frames spanning the join between hop 1 and hop 2. One of these is the last frame the first generation produced and the next is the first frame of a second, separate generation. The pack exists so that you cannot tell which.

Each hop is native MiniMax H3 Reference-to-Video. Hops after the first are guided by the previous hop's sampler AV latent through ComfyUI-H3-Motion-Context when it is installed; stock MiniMaxH3AddGuide is the fallback, and the console says which one each hop took.

---

What it gives you

---

Tested in public

Before 2.0 shipped, a tester ran ten controlled nine-hop chains — 65 s each, one variable per run, same model, LoRA, references, locked audio and seed — and measured them end to end with her own instruments rather than by eye. The results below are hers, used with permission.

Her headline: anchor: "restart" won. It is the only run type whose last ten seconds is still on the reference still's side of its own hop 1 — colour, texture, background and framing all hold. The cost is that a restart is a hard cut. Second best was a small pin_noise, one run each way. Nothing else moved the needle — not pin_renorm=band, not reference protection, not a different DiT, not ref_image_size=match, not a fresh seed — and the plain control was the worst of the ten.

Her diagnosis is sharper than ours was: relay convergence with no content anchor. Each hop inherits its predecessor's end state and nothing pulls it back toward the reference. It also explains why the scale knobs did nothing — the pin's statistics never drifted (sigma stayed within ±6% across nine hops) while the picture lost a fifth of its chroma and doubled its background edges. The drift is in the latent's content, not its scale, and pin_renorm and pin_noise only rescale.

Three things in 2.0 come straight from that study:

• Restart hops write their full length. They used to drop 0.9 s of new content as though they were continuations.
• last_frame_guide=before_restart, so both sides of a restart cut meet on the same photograph and it reads as a match cut rather than a jump.
• tone_anchor_ref=still. The anchor used to hold hop 1, on the reasoning that hop 1 is the one tone in the chain nothing has drifted into yet. Her measurements say that is false — hop 1 is the first casualty, already short of the still before any relay has happened:

A chain anchored on hop 1 converges on a target that already fell short.

What her study could not fix, this release does not claim to fix. Texture still ratchets on long chains, and 3–5 hops is still the honest limit.

---

Install

From your ComfyUI/custom_nodes/ folder:

git clone https://github.com/dntpi/ComfyUI-Hand-Tie-Clips.git

Or from the HuggingFace mirror, which is the same repository:

git clone https://huggingface.co/sandpies/ComfyUI-Hand-Tie-Clips

Cloning puts the folder at the right depth, which is the mistake the zip route invites — one level too deep (custom_nodes/ComfyUI-Hand-Tie-Clips/ComfyUI-Hand-Tie-Clips/) and the pack simply will not appear. Updating later is git pull and a restart.

No dependencies to install. Everything it imports — torch, numpy, PIL, av, aiohttp — already ships with ComfyUI, which is why dependencies in pyproject.toml is empty.

Then restart ComfyUI (Python changed) and hard-refresh the browser (Ctrl+Shift+R). The editor is served from /extensions/ComfyUI-Hand-Tie-Clips/, and a stale cache is the single most common reason the node mounts with no UI on a fresh install.

It is installed correctly when all three are true:

• the startup log carries a line beginning [HandTieClips]
• the browser console says [HandTieClips] editor ui v2.2.0 loaded
• node search shows a Hand Tie Clips category with six nodes, each once

Workflows saved before the 2026-08-29 rename keep loading — the old ids are registered as deprecated aliases. Nothing needs migrating.

Needs

• ComfyUI new enough to include Add Guide for MiniMax H3 (MiniMaxH3AddGuide)
• A ref2va (or hybrid ref2va) checkpoint — fl2va has no reference rows
• Video VAE + audio VAE + MiniMax text encoder
• Recommended: ComfyUI-H3-Motion-Context for the latent join. Without it the node falls back to MiniMaxH3AddGuide, which still works and still chains — it is a different join, so a seam you are comparing against someone else's render may not be the same code path.

The two shipped workflows wire the turbo stack this node is actually run with, because an example without it is not the graph anyone uses:

UNETLoader -> LoRA Loader Stack -> H3 AdaLN LoRA Fix -> MiniMax H3 Low VRAM
           -> H3 SLA Attention -> Model Preview Override -> H3 Cache
           -> Hand Tie Clips

H3 Cache is this pack's own and needs no install; it is last on the wire so the clone the sampler sees is the one every other patch has been applied to.

CLIP reaches the node from the LoRA loader, not from the encoder — that is what makes the text half of every LoRA land. Do not rewire it back.

None of it is required by the node itself. Missing a pack, its nodes load as red boxes: delete them, wire the loader straight into model and the encoder into clip, and raise steps from 10 to around 20.

Both shipped workflows are saved pointing at the exact quantised files they were rendered with. These are not the only builds that work — any ref2va or hybrid ref2va set will do. Repoint the loaders at what you have; a loader showing an empty or red filename is naming a file you do not have, not a broken workflow.

<details> <summary>The exact files the examples name</summary> </details>

---

Start here

1. Load workflows/HandTieClips_Starter.json — two hops, no references, runs as soon as the loaders point at your files. It carries a READ ME board on its own canvas, to the left of the loaders: the laws, the directive table, the reference rules and the failure table, where you need them rather than in another file.
2. Point the loaders at your ref2va DiT, encoder, and both VAEs.
3. In REFS, add a row per identity still and drop a picture onto its thumbnail. Give it a @tag; group photos of the same person under one subject number. Files land in ComfyUI/input/h3_refs — there is nothing to wire.
4. In SCRIPT, write one card per hop. Shot 1 is the whole opening; every later card is only the new beat.
5. Optional: a first frame, up to three reference clips, up to three voices, a music bed, a master audio take — all in MEDIA.
6. Queue. Wire info to a Preview Text node to read the fully assembled prompt for every hop.

workflows/HandTieClips_Showcase.json is the six-hop version and needs three pictures of your own. Both carry the turbo stack above.

Each tab carries its count, and RUN stays pinned below them. SCRIPT is one card per hop: the beat, its duration, and its own join, camera, framing, pace and tail, with lock and the range button on the card header.

Under the script sits RUN, collapsed, holding everything that is not per-shot: output size and length, sampling, the join and pin controls (pin_mech, last_frame_guide, tone), and the hop cache. Its title line summarises the run — 1344x768 · 10s ×3 · 14 steps res_multistep · cache off — so you can read the setup without opening it.

Two script modes: Simple (one prompt box and a hop count, the way it always worked) and Shots (one card per hop with directives; switching from Simple carries your prompt over and splits it on ---). Only one is on screen at a time, so no text box is ever quietly doing nothing.

Keep later-hop beats on what happens next. Do not re-describe the face; the photos, the register and the pin already carry it.

---

What's new in 2.2.0 — 2026-09-21

Three corrections to the refine pass shipped in 2.1.0, plus the MEDIA audio window.

refine_align picks the sigmas the refine pass re-runs. The default stays denoise — a 2.1 graph reloads on the schedule it rendered under — and speed_mode=turbo now sets hop_tail, which re-runs the hop's own last steps instead of inventing a schedule tuned for a 4-step base.

refine_blend=auto derives the blend ramp from this run's overlap. The old literal 0:0, 22:0, 44:1 had the overlap width baked into it, so at a 1.6 s overlap it refined frames inside the pin — exactly the seam cost the ramp exists to remove — and at 0.2 s it threw away refined frames you had paid for. auto at the shipped 0.9 s overlap resolves to the old string byte-for-byte, so cached hops still hit.

SLA moved to the front of the MODEL wire in both shipped workflows, on PlagueKind's recommendation. That reorder changes _model_fingerprint, so every hop re-renders once on first run even with cache_hops=on.

Also: master_audio_start_s, so the chain's audio window can start somewhere other than zero.

Full notes stay at the bottom under Changelog. Detail lives in CHANGELOG.md.

---

The one law

Sampling runs at cfg 1.0 with no negative branch, so the prompt is purely additive: anything you name is added, and nothing can be removed by mentioning it. Almost every rule in this pack is a consequence, and each of the rules below was confirmed against renders rather than reasoned from code.

Never name the thing you want to end. The cook stops talking keeps her talking. Write the state you want as a pose plus a sound:

The cook leans back against the counter with her lips closed, and lets her eyes move slowly across the room. The kitchen is quiet apart from the hum of the refrigerator.

H3 generates audio for the whole hop no matter what, so silence has to be written as a sound. Written as an absence, you get speech. The ban is on the idea, not on a word list: fades, subsides, dies down all name an ending as surely as stops does.

Point the action line at the reference you want used. Describing a reference in the register is not enough — the beat is what drives the frame. Write the tag into the action: The cook stands at the counter in @kitchen, looks up…. Phrase a place as depicted, not as a container to be placed inside, or you can get a literal composite of the photograph.

Put a state change at the end of the previous shot. Every hop after the first opens by holding the frames it was handed, and the audio pin carries the previous hop's tail across the join. If shot 2 ends mid-sentence, no wording in shot 3 will make it start quiet — arrive there before the previous shot ends.

Pick ambience that is narrowband and specific. "faint street noise through the window" is broadband and renders as a five-second hiss; "the low hum of the refrigerator" does not.

Set tail on your last shot. Left on ongoing, the model is told action is still underway at the final frame and will invent something to satisfy it — a stray gesture, or a stray line of dialogue in the closing second.

The full authoring guide is PROMPTING.md. Its rules come from what this model actually does, not from taste. prompt_pack/ is the same writer as a copy-paste prompt, for when you would rather work in a chat window.

---

Let a model write the plan

Open WRITE, point it at any OpenAI-compatible server, say what you want in one sentence, and press Write plan. It fills the SCRIPT cards and the REFERENCES rows together — and the pictures already on those rows go with the request, so the model describes what it is actually looking at rather than guessing from a filename.

• Context 32768. The system prompt alone is ~6,000 tokens, the reply another 1,000–2,000, and every reference picture costs ~260 on top.
• Reasoning off. Thinking tokens come out of the same budget; a reply that stops before the JSON closes is the tell.
• Temperature 0.3. Higher and the JSON grows trailing commas and smart quotes.

Server settings are saved on this machine only — a shared .json never points at your server.

Treat what comes back as a strong draft, not a finished plan. It gets the structure right — hop count, join types, which reference rides which hop, a sound bed on every quiet hop — which is the part that is tedious by hand. Read two things every time: each reference's desc, which can be confidently wrong about its own photograph, and the spoken words in every beat. The node lints both and prints what it finds before you render.

---

SWAP

A one-hop identity swap from a reference clip: the clip supplies the motion and the scene, a still from your rail supplies the person. Trim the clip in MEDIA, pick an identity, press Write, then Accept — which writes exactly one shot and the clip's description, and never touches ref_plan. Your register is not rewritten.

Four modes, because at cfg 1.0 a mode that merely omits the swap line does not keep the clip's person — the identity still is in front of the encoder either way and governs the subject anyway. Each mode states positively what stays:

Alongside them: background (from the clip / from a picture @tag / free) and an optional wardrobe plate — a @tag whose garment is worn, draping on the body in frame and creasing where it bends, not pasted.

Two things to get right, both of which cost renders to find out:

• Do not run MEDIA's describe on the clip before a swap. That caption reaches the encoder as what <Video 1> is, and — being additive — a caption naming a person asks for the person you are about to replace. Four consecutive "head swap doesn't work" reports came down to that, a missing frame sequence and a weak citation; none of them was broken code. SWAP now warns when a caption names somebody.
• Drop the clip to ~0.3 MP. A reference clip's decode area is its token count, and its token count is its influence. A full-size plate out-argues a single photograph.

---

Holding a chain together

The join

pin_mech chooses it. auto (default) is Motion-Context when the pack is installed, the overlap has a matching context_length, and the previous hop left a sampler latent; AddGuide pixels otherwise. Forcing motion_context or addguide does not fall back — it fails with the reason, because a lever that silently becomes the other setting cannot be compared against it. motion_context is a latent join with no decode/re-encode; addguide re-encodes decoded pixels, which is itself a VAE round trip. Switching re-renders hops 2+ and leaves hop 1 on disk. A restart hop pins nothing.

<details> <summary>Three more pin dials, all defaulting to their pre-existing behaviour</summary>

pin_to_qwen separately shows the incoming state to the text encoder: off, last frame (default — the previous hop's last frame becomes <Picture 1>, and identity stills shift to Picture 2+), pin clip (overlap frames as an extra <Video> at ~2 fps, no soundtrack), or both. @tags in beats resolve per hop, so stills shifting never breaks prose; a literal <Picture N> in a hop 2+ beat would.

</details>

Brightness drift — two different problems

The step at a join is the denoiser's tone bias on a fresh generation. tone_compensate=frame_shift measures it on the overlap the hop regenerated and cancels it, which is why the seams in a corrected chain read as invisible. Measured on a 3-hop render: chain drift 5.6/255 without it, 0.3/255 with it. All three modes remove the drift equally well, but gain_bias and lut pair pixels between a frame and its regeneration, fitting a slope that is not really there; frame_shift uses frame averages only, so it can shift but never distort.

The slide across a whole chain is different. Each hop also darkens across its own frames, hands that darker tail to the next hop, and the next hop starts from there. Seam correction cannot see this — every individual join is exact while the film gets steadily dimmer. An 8×15 s chain slid from luma 46 to 11 across hops 2–6 with every seam already corrected.

tone_compensate=anchor is frame_shift plus a pull back toward a target, matched in Lab — L*, a*, b* and L* spread — because chroma loss is the largest measured drift and a per-channel RGB mean cannot restore it. tone_anchor_ref picks the target: hop1 (default) or still, which holds the photograph and is the only setting that ever closes the 33.6-against-30 gap above. still needs start_image_file, and under the Motion-Context join the correction still only reaches the delivered frames, not the next hop's pin — pin_mech=addguide is what closes that loop.

Two things keep the pull from causing the problem it is fixing: it ramps in across the first two seconds of each hop, so frame 0 still matches the previous hop's last frame exactly and the seam stays as clean as frame_shift left it; and it is capped per hop (tone_anchor, default 0.35 ≈ a third of the gap), so a long slide is corrected over several hops instead of one hop snapping back and pumping.

Both columns are H3 Seam Report's own numbers, so what you measure matches what this table says. Drift falls evenly — 45%, 62%, 78% of the uncorrected slide. The seam does not: 0.15 pulls it tighter than the uncorrected chain and it grows from there. Hop 1 is byte-identical in all four. 0.35 is the default and stays — it halves the drift while every seam still reads as marginal or better. Set tone_anchor to 0 for plain frame_shift.

A scene that is meant to get darker looks exactly like drift from the inside, so a shot can opt out: "tone": "free" skips the pull for that hop, "tone": "rebase" also moves the anchor onto it — which is how a scene that is genuinely darker from here on stops being fought for the rest of the film.

Restarts, and the last-frame guide

anchor: "restart" on a shot makes that hop a chain start — the start image is frame 0 and nothing is relayed. It is a cut, so it belongs where a cut is motivated: a pause, a change of thought, a new beat, not on a hop interval. Pair it with join: hard_cut or match_cut; continuous is refused. Name the room in the beat, because a pin-less hop has nothing else telling it where it is. Never on shot 1, and it needs a start image.

last_frame_guide plants start_image at a hop's last pixel frame (AddGuide frame_idx=-1, not latent T-1). It does not become the next hop's frame 0. Needs a start image. Ships off.

Reach for before_restart. It guides only a hop whose next shot is a restart, so both sides of the cut meet on one image — hop 3 used to end tight and smiling, hop 4 open wide and neutral; with the guide, hop 3 arrives at the still's framing. Measured: the four hop endings of a 4-hop chain converge to 3.8/255 of each other against 39.1/255 unguided, while mid-hop frames stay as varied as ever (65.8 against 61.1). Two people watched it in motion and could not see the convergence.

still is the "I know what I am doing" setting. It plants the photograph on every hop, unconditionally, which overrides an authored framing at every hop ending — a shot set framing: close plays close for six seconds and then snaps to the still's wider framing in about 0.6 s, and the next hop pushes back in. A user watching this described it, unprompted, as "the camera kept cutting in and out." Frame-by-frame from that run, hop 3, framing: close:

1.58s close   3.67s close   4.92s close   5.96s close-ish   6.58s WIDE   7.04s WIDE

Safe when no shot authors a framing; visibly wrong when they do.

---

Reference

The shot fields, the directive vocabulary, the reference register and the dry-run flags are in PROMPTING.md, which ships with the pack. That file is how to write a plan; what follows is what the knobs do.

Reference media: three clips, three voices

H3 takes 9 reference pictures, 3 reference videos and 3 standalone reference audios. Pictures go through REFS; the clips and voices are in MEDIA.

Numbering is dense. Fill slots 1 and 3 and you get <Video 1> and <Video 2> — there is no gap, so clearing a slot renumbers the ones after it. Refer to media by what it is, not by its number.

Reference clips carry their own sound: each clip's audio track is decoded and handed to the model alongside its picture. A clip with no usable audio track passes silent and says so in the log.

Trim them. Every reference audio is attended on every step of every hop, and H3 encodes the whole file, so a three-minute take is a large invisible tax on a clip that only needed four seconds. Slots 2 and 3 share slot 1's reference video size, which is a decode budget rather than a creative setting — and, as SWAP found the hard way, an influence dial.

A reference clip with its in/out scrubber, the description that tells the encoder what the clip is for, and video input size.

master_audio_file is the odd one out: one continuous take every hop lip-syncs to, delivered as a passthrough with no VAE round trip. Empty is off and leaves generated voice as before. The beat still needs the words in <d>[English] …</d> — the lock supplies the timing, not the script — and a take shorter than the chain is refused on the queue rather than discovered as a mute final hop.

An end of 0 on any scrubber means to the end of the file, so a longer replacement still plays out rather than being cropped to the old one.

Hop cache

cache_hops=on writes every rendered hop to ComfyUI's temp dir as lossless FFV1 video plus a float32 .npy waveform, evicting least-recently-used above cache_budget_gb. The key chains — each hop's key includes the previous hop's — because hops are causally dependent. So:

• edit shot 3 and re-queue → shots 1 and 2 load from cache, only 3 renders;
• edit shot 1 → all three re-render, which is correct, not a bug;
• change resolution, sampler, the checkpoint, a LoRA, or an attention setting → the whole chain re-renders;
• change pin_to_qwen or overlap → only hops 2+ re-render, because neither can reach hop 1. A restart hop is a start, so overlap does not reach it either;
• set last_frame_guide=still or master_audio_file → every hop re-renders (both reach hop 1). before_restart only moves the hop that gets the guide;
• change a reference picture → only the hops that picture rides re-render.

That last one is worth knowing about. The node cannot read the settings on your LoRA and attention nodes, so it fingerprints what they did to the model — which weight keys were patched, at what strengths, and the attention overrides — plus the base model's class, dtype and parameter count. Two remaining gaps: two different LoRAs touching exactly the same keys at exactly the same strengths, and two different builds of the same architecture at the same dtype and parameter count.

Set locked: true on a shot to pin it to its last render regardless.

Defaults

Three shots at 10 s with a 0.9 s overlap is about 28 s of master.

Nodes

H3 Ref2VA Chain — images, audio, info, contact_sheet out. Wire CreateVideo + SaveVideo as in the example workflow, info to a Preview Text node, and contact_sheet to a Save Image.

H3 Chain Preview — a passthrough panel for the IMAGE (and optionally AUDIO) wire, placed between the chain and CreateVideo. Images and audio come out unchanged, so adding or removing it changes no pixels. It shows the live sample, the seam, a chain-wide progress bar, cache hit / seed / steps per hop, which pin mechanism each hop actually used, and end-of-run A/V drift.

H3 Tone Compensate — images out. For hand-built chains only. It cannot fix H3 Ref2VA Chain's output: that node joins its hops internally and drops each hop's first overlap frames at the seam, so the regenerated copies this needs are already gone. Use the chain node's tone_compensate widget instead.

H3 Seam Report — report (STRING) + chart (IMAGE). Ships wired on the Starter canvas. Wire the chain's info into it as well as images: with a restart in the chain the hop lengths are no longer uniform, and the hops / overlap widgets cannot describe that. It measures the brightness step at every join, says whether each is invisible / marginal / visible, and totals the chain's cumulative drift. A single reading includes whatever the scene did across the cut, so treat one number as an upper bound.

H3 Cache — MODEL in, MODEL out. Drop it on the model wire before the chain node. It reuses MiniMax-H3's whole-block-stack residual on steps whose features have barely moved, which is what makes the non-turbo base fast enough to be the recommended setting rather than a purist's option. Patches a clone, so it composes with SLA attention and the LoRA stack in any order. The defaults are deliberately conservative — cache error here feeds the next hop's guide and compounds, so it is not a per-hop cost. Implementation by silveroxides, redistributed with permission; see THIRD_PARTY_NOTICES.md. If you already run PlagueKind's cache node, use one or the other: two on one wire corrupt each other, and this one refuses rather than let that happen silently.

H3 Continuity State — continuity_state (STRING) out. Setting only: setting_locked / setting_context / setting_mutable. Characters belong in ref_plan.

Limits

• Texture still ratchets on long chains. Stay around 3–5 hops until that is handled. Nine-hop chains have been measured; they converge.
• A workflow saved before 2026-08-28 loses its reference pictures. The old ref_image_N sockets carried tensors, so there is no filename to recover. The rail names each affected ref and asks you to pick its picture.
• The reference desc and subject locked text go to the encoder verbatim, every hop. A detail that is not in the photograph is asked for, not ignored. Describe what you actually wired.
• HTCContinuityState is setting only; the characters_* fields were removed because filling in both injected identity text twice.
• Each join hard-cuts video but crossfades audio ~40 ms, so A/V drifts ~40 ms per hop.
• A 22-frame pin clip is ~2 Qwen frames at 2 fps. It is a live-state hint, not a full previous-clip watch.
• A longer overlap does not fix continuity — it can pin whatever content happens to be in that longer tail.
• A 5 s hop drops the airlock on a continuous join; validate seams at 8 s or 15 s.

---

Credits

From the Sulphur Discord:

• @urlilgoddess — the ten-run degradation study this release is built on, run and measured with her own instruments, and the sample frames in Tested in public. Three of 2.0's behaviours exist because she measured that the reasoning behind the old ones was wrong.
• @frankyi — contributed the SWAP tab, which ships in 2.0 rebuilt from its own design rather than merged as-is.
• @Sean3884 — author of PromptMasterLD, which this pack has borrowed from twice: its song_lock shaped audio_lock.py, and its edit laws shaped SWAP's four modes. Technique, not code — the distinctions and the discipline of stating an exclusion affirmatively, with the prose written fresh here.

Also: the H3 Cache node is silveroxides' MiniMax-H3 block cache from ComfyUI-UtilsCollection (AGPL-3.0), improved and ported by PlagueKind (ComfyUI-H3-MiniMax-Cache — his v1.5.1 reference protection and the production defaults this pack ships), then redistributed here with silveroxides' permission — the full chain, including the part of it that descends from GPL-3.0 ComfyUI Core and that nobody was in a position to relicense, is written out in THIRD_PARTY_NOTICES.md. The tone estimator is ported from rkfg/ComfyUI-MiniMaxH3-ToneCompensate (MIT, as is this pack), and the latent join comes from ComfyUI-H3-Motion-Context. The turbo stack in the shipped workflows is PlagueKind and KJNodes.

Docs

CHANGELOG.md is what 2.2.0 contains, written for users. PROMPTING.md is the authoring guide. docs/ARCHITECTURE.md is the internals, for anyone changing the node. All three ship with the pack.

The rest are in the repository only — the published package excludes them, so they are not in your custom_nodes folder and these links leave for GitHub. docs/DEVLOG.md is the engineering log and docs/LEVER_AUDIT.md the lever sweeps behind it. docs/GROK_V2_HANDBACK.md, docs/GROK_V2_GPU_TESTS.md, docs/POST_V2.md and BETA_NOTES.md are historical session notes — do not take them as the state of this release.

---

Changelog

Full notes in CHANGELOG.md.

2.2.0 — 2026-09-21. Three corrections to 2.1.0's refine pass, plus the MEDIA audio window. refine_align (denoise default, hop_tail under speed_mode=turbo) chooses whether the refine pass builds its own schedule or re-runs the hop's own last sigmas — the published refine_denoise=0.50 + refine_steps=2 pair was a schedule hard-coded to a 4-step base, whatever the hop actually sampled. refine_blend=auto derives the blend ramp from this run's overlap instead of hard-coding 22 frames; at 1.6 s the old literal refined frames inside the pin, and at 0.2 s it discarded refined frames. auto resolves to the old string exactly at the shipped 0.9 s overlap, so the hop cache still hits. speed_mode=turbo no longer moves refine_head, which is a measured drift lever and not a property of the checkpoint. SLA moved to the front of the MODEL wire in both shipped workflows on PlagueKind's recommendation, which changes _model_fingerprint and therefore re-renders every hop once. New: master_audio_start_s, where the chain's window opens inside master_audio_file; there is deliberately no matching end, because the width is the chain itself.

2.1.0 — 2026-09-16. A refine pass. hop_refine runs a second, short, deliberately under-converged sampler pass over each hop and blends it back into the raw latent on a per-frame ramp, so the pin the next hop inherits is the blended one. It ships off, along with refine_denoise, refine_steps, refine_sampler, refine_scheduler, refine_cond, refine_model, refine_audio, refine_blend, refine_blend_interp, refine_head and speed_mode. refine_audio=freeze is the default and it means audio leaves a refined chain bit-identical to an unrefined one. A new H3 Cache node makes the non-turbo base fast enough to recommend; it is silveroxides' implementation, improved and ported by PlagueKind, redistributed with permission, and THIRD_PARTY_NOTICES.md records the whole chain of provenance. The prompt pack gained a trust boundary: scene material now arrives in labelled blocks that cannot change the hop count or any rule. Every widget was appended, so a 2.0 graph loads and renders identically. Three 9-hop chains held identity flat at this refine block, each with a second DiT on refine_model, which is why these values are frozen; the controlled off-vs-full pair has not been run, so attribution stays open and the CHANGELOG says so.

Earlier releases — 2.0.0 back to 0.4.x — are in CHANGELOG.md.