LTX-2 Last Frame Bridge Save ?????

The last frame of your just-finished segment is the most valuable frame in the whole pipeline - it's what the next segment has to continue from. This node makes sure that frame actually survives the handoff: it takes an IMAGE batch, grabs the final frame, and writes it as a PNG to the bridge directory where IAMCCS_LTX2_LastFrameBridgeLoad can pick it up.

That's the whole job, and it's intentionally dumb in a good way. No analysis, no upscaling, no decisions - save the last frame, report where it went. The decisions live in the bridge naming, which is where the real logic of a segmented pipeline hides.

How it works

last_frame = images[-1]
bridge_path = <output>/iamccs_ltx2_bridges/<bridge_name>_<render_id>.png

The file lands in ComfyUI/output/iamccs_ltx2_bridges/, named as the concatenation of bridge_name (default ltx2_detailer_bridge) and render_id. Two guards worth knowing:

• If render_id is empty, the save is disabled - it passes the images through and reports save disabled. This is deliberate: without a render identifier there's no way to key the bridge, so the author chose to do nothing rather than write garbage.
• It validates the input is a real [N,H,W,C] batch with at least one frame; anything else raises instead of silently saving a broken PNG.

Inputs and outputs

• images - the IMAGE batch; its last frame is what gets saved.
• bridge_name - must match the corresponding Load node.
• render_id - the render chain key; empty disables the save.

Outputs: images (passed through untouched) and report naming the saved file.

Install

ComfyUI Manager → "IAMCCS", or:

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

Restart. No extra dependencies.

Gotchas

Symmetry is everything with bridges. The bridge_name and render_id here must exactly match the Load node, because the path is the concatenation of both - a mismatch and your next segment quietly falls back to its own anchor with no error. Also note the save is skipped entirely when render_id is empty, which surprises people who wire it up without a render key and wonder why the bridge directory stays empty. If you're debugging a chain that keeps losing continuity, check the bridge folder after a run: a missing PNG there means the Save side never fired, and no amount of tuning on the Load side will fix that.