LTX-2 Blend Latent Bridge ???

The core problem in extending any video model past one segment is the seam. Generate segment 1, generate segment 2 independently, and there's a hard cut where the first one ends - different motion, different lighting, a visible jump. IAMCCS LTX-2 Blend LatentBridge is the node that welds the two segments together by blending the previous segment's tail into the current latent's head, so the new segment starts inside the old one instead of after it.

The name is doing real work: this is a "bridge" between segment renders, not a full continuation sampler. It belongs to the pack's LTX-2 extension module, the family of helpers that let you build iterative long-video extension workflows in native ComfyUI.

How it works

The inputs tell the story:

• latents - the current segment's LATENT.
• segment_index - which segment this is (0 for the first). The bridge only activates on segment > 0.
• render_id - the identifier of the current render, used to locate the previous segment's saved bridge payload on disk.
• temporal_overlap - how many pixel frames of the previous segment to fold into this one. The node converts that to latent frames using the VAE's time scale (from the optional vae input, defaulting to 8).
• vae (optional) - used for the pixel→latent time conversion.

If segment_index is 0, or there's no render_id, or no bridge payload exists yet, it returns the latents untouched with a report saying so - an "initial or disabled" state that's safe to leave in place. And if an upstream extend sampler has already applied the bridge, the node detects the flag and hands the latents straight through.

Outputs: latents (bridged) and report - a text summary that tells you which state you landed in, which is genuinely useful when you're debugging whether the weld actually ran.

Where it fits

This isn't a drop-in for anything in stock ComfyUI; it's purpose-built for the IAMCCS extension workflow where segments are rendered with a shared render_id and the tail of each one is persisted for the next. If you're hand-rolling long-video extension without the pack's segment queue machinery, you can still use it as long as a previous render's bridge payload exists under the expected path - that's what render_id is for.

Install

Standard IAMCCS-nodes install:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

or ComfyUI Manager → search IAMCCS, then restart. The node itself needs no extra deps; it does assume you have LTX-2 loaded in ComfyUI (a real checkpoint + VAE) and, ideally, the pack's segment-queue machinery feeding it.

The honest caveat

If the report says missing:<filename> the bridge payload wasn't found - the previous segment didn't run, or its render_id doesn't match. That's the number one reason this node silently does nothing. Check the render_id is identical across segments and that the earlier segment actually completed.