Wan Continuation Conditioning

Wan 2.2 gives you about five seconds. That's it - 81 frames at 16fps is the model's native window, and asking for more in a single generation is exactly where the motion reversal and subject drift start. So the way real long videos actually get made is chunking: generate 81 frames, grab the last frame, and feed it into the next 81-frame pass as the new starting image. WanContinuationConditioning is the little connector node that makes that handoff painless. It's part of shootthesound's comfyUI-LongLook pack, the FreeLong project that landed with a genuinely warm reception on r/StableDiffusion in late 2025 - this node is the chunking half of that story.

Under the hood it does exactly what ComfyUI's WanImageToVideo does, but purpose-built for chaining. You feed it the decoded last frame of your previous chunk through anchor_images, and it builds a full video-length tensor: your anchor frame at position 0, neutral gray (0.5) everywhere else. That whole thing gets VAE-encoded into latent space and attached to your positive and negative conditioning as a concat_latent_image plus a concat_mask. The mask tells the sampler "preserve frame 0, denoise the rest" - that's the i2v conditioning signal Wan needs. The latent it also returns is the noise tensor you start sampling from, pre-shaped for exactly the width, height, and frame count you asked for. Chain it, and each chunk sees a clean starting point instead of a mushy ambiguous one.

The inputs that matter are few. positive and negative are your text conditioning straight from a CLIP encode. anchor_images is the last frame of the previous chunk (wire up the last VAE decode's image output, or just grab the final frame of your video). vae is your Wan VAE, and width/height should match what you generated in chunk 1. Then video_length - default 81, and here's where people get burned: it must match your sampler's frame count. Set 81 in both. Wan's VAE time-compresses roughly 4x, which is why frame counts practically land on the 4n+1 pattern; 81 is the native sweet spot and the safest number.

One genuinely nice addition came in v3.0.7 (credit to @onerok): the optional end_images input. Feed it a target last frame and the node preserves both anchors - start and end - which can steer a chunk toward a specific ending pose instead of letting it wander. That's end-frame guidance, and it's great for scene transitions that need to land somewhere particular.

Installing is the same story for every node in this pack, since they all ship together. Easiest is ComfyUI Manager - search for "comfyUI-LongLook" and click install, then restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/shootthesound/comfyUI-LongLook.git

then restart ComfyUI. There's no requirements.txt and nothing extra to download from this pack - it doesn't ship models. You need a Wan 2.2 checkpoint (i2v recommended) and VideoHelperSuite for actually saving video.

Troubleshooting is mostly about expectations. Character likeness still degrades across many chunks - that's a universal chunking tax, not this node's fault. Users in the release thread kept it to 2-3 chunks before it got noticeable, and the pack's updated Car-Racing workflow supports per-chunk LoRAs if you need identity to survive longer. GGUF-quantized checkpoints work fine, and if your chunk's output comes back a frame or two short, check that video_length matches your sampler rather than blaming the node.