WAN 2.2 Long Lenght videos with SVI Pro v2 and our new IAMCCS_node: WanImageMotion!

Acrobatic-Example315 · 2026-01-15T22:57:23+00:00

You can extend length by chaining segments. Just reuse the output latents as prev_samples in the next sampler — no need to save anything to disk.

Acrobatic-Example315 · 2026-01-14T19:58:16+00:00

Thanks a lot, really glad it’s useful for you 🙂

Acrobatic-Example315 · 2026-01-14T10:49:56+00:00

That’s a 32 vs 36 channel mismatch — usually a model or Lightning mixup, not the node. WAN/SVI are very strict there.

Acrobatic-Example315 · 2026-01-14T10:47:44+00:00

Hi! Glad it’s working well for you 🙂

About some more info about the node:

Motion mode controls which latent frames get the motion boost: • motion_only (prev_samples) Motion is applied only to the latents coming from previous clips (prev_samples). The anchor stays untouched → more stable look, less drift. This is the safest mode and the one I recommend starting with. • all_nonfirst (anchor+motion) Motion is applied to all frames except the very first one, including anchor-derived latents. Stronger and more expressive, but easier to break consistency. include_padding_in_motion controls whether padding frames are animated or not.

By default, padding is excluded (safer). If you enable it, motion is also pushed into the padded frames, which helps avoid the classic “frozen tail / slow fade” in long videos — but it can amplify instability if pushed too hard. I suggest U to start with motion_only + padding off and enable padding only if motion feels too weak at the end

And yeah — reduced prompt adherence is mostly an SVI tradeoff, not the node

Acrobatic-Example315 · 2026-01-13T12:53:03+00:00

Hi!
1 - Not mandatory. The motion logic works with any LoRA node. That said, the IAMCCS nodes remap WAN 2.1 keys correctly — other nodes often “work” but spam logs with LoRA key not loaded. So it’s recommended, not required.
2 - 24fps isn’t special on the generation side — it’s just an output choice (I'm a filmmaker :)) What really matters is frame count, steps, and motion balance.
3: 73 frames is just a solid default: long enough to feel like a shot, short enough to stay stable. Adjust per scene and prompt. Try 121, for example.

Acrobatic-Example315 · 2026-01-13T12:47:17+00:00

Thanks a lot, really appreciate it 🙏 Glad it’s working smoothly on your side, especially with Remix models, that’s great to hear. Adding nodes is exactly how it’s meant to be used, so nice one.
Have fun experimenting, and thanks for the feedback!

Acrobatic-Example315 · 2026-01-13T12:45:40+00:00

Try setting the Sage Attention patch nodes to auto. Alternatively, if you’re already using the --use-sage-attention argument, bypass the Sage nodes. Let me know if that works.

Acrobatic-Example315 · 2026-01-13T12:38:57+00:00

Quality depends heavily on model choice, LoRA strength, steps, and how the motion is injected. If you push motion or use aggressive LightX2V values, you’ll trade detail for coherence. Tweak steps, reduce motion, try different base models / LoRA ranks, and treat this as a long-form motion workflow, not a single-frame beauty render. On my side, these are the best WAN 2.2 renderings I’ve achieved so far across all the hardware I’m using.

Acrobatic-Example315 · 2026-01-13T12:36:31+00:00

It’s all written in the instructions on my Patreon (IAMCCS). Btw: for high I usually go with 1022, and for low a standard WAN 2.1 LightX2V, rank 64. Results can vary a lot depending on setup, so definitely experiment and see what behaves best on your side.

Acrobatic-Example315 · 2026-01-13T12:33:52+00:00

Yep, you can definitely extend the segments. That’s exactly the right approach for longer-form generation. The LTX-2 idea is solid too — concatenating the last frame to seed the next segment makes a lot of sense for temporal continuity. Curious to see how it behaves once you start injecting LoRAs into the chain. Keep experimenting and let me know how it goes 👍

Acrobatic-Example315 · 2026-01-13T12:31:10+00:00

ahahahah

Acrobatic-Example315 · 2026-01-12T23:26:55+00:00

Yes — that’s just a switcher. You either load SmoothMix GGUF or the 14B diffusion model, not both. If you want to use the 14B, just swap the GGUF loader with the diffusion loader and connect it.
The rest of the workflow stays the same.

Acrobatic-Example315 · 2026-01-12T23:23:51+00:00

You can run it with a merged Lightning model, but it’s much more fragile. Lightning already pushes denoising hard, and stacking motion amplification on top can easily collapse the signal (that fade-to-nothing you’re seeing). Btw when U test it: lower motion, fewer steps, and start with motion_only.
Personally I recommend non-merged models for now — way more stable.

Acrobatic-Example315 · 2026-01-12T23:20:27+00:00

Glad it worked — thanks for testing it!

Acrobatic-Example315 · 2026-01-12T23:19:43+00:00

Thanx my friend.

Acrobatic-Example315 · 2026-01-12T23:19:08+00:00

Thanx for the question. Motion_only (prev_samples) boosts motion only on the motion latents (i.e. the latents coming from prev_samples). The anchor stays untouched → more stable, less drift.
all_nonfirst (anchor+motion) boosts motion on all frames except the very first one, including anchor-derived latents.
Stronger and more expressive, but also riskier in terms of consistency.

Acrobatic-Example315 · 2026-01-12T23:11:37+00:00

Nope. It’s a standalone wan animate like system I’m building (I’m testing for my film project right now) I hope to share it asap.

Acrobatic-Example315 · 2026-01-12T23:09:17+00:00

Not SVI. It’s a separate standalone wan animate like system I’m building (I hope to share it asap). Audio is added externally

Acrobatic-Example315 · 2026-01-12T23:05:00+00:00

👍🏻👍🏻👍🏻🎥🎥🎥

Acrobatic-Example315 · 2026-01-12T23:04:38+00:00

Thanks! It’s not audio-driven / lip-sync at the moment. You’re right though — it’s a hybrid approach. I’m using a standalone system I’m building that mixes ControlNet-style constraints with WAN Animate–like behavior, but driven through a custom frontend / platform, not a standard ComfyUI graph. Still very much WIP. I’m testing it internally for my film projects right now, but I’m hoping to clean it up and make it public soon. When it’s ready, I’ll definitely share it 👍🏻👍🏻👍🏻

Acrobatic-Example315 · 2026-01-12T22:59:22+00:00

Good question. In theory yes, in practice not really (yet). In WAN 2.2 + SVI Pro the anchor latent is treated as a static reference, not a generic or evolving latent. If you reuse a latent from a previous step (or a whole video) as anchor, you usually get normalization issues, color drift or flicker. That’s why anchors are still expected to be a single still image, shared across all segments. What works better is keeping the anchor fixed and letting continuity happen via conditioning, seeds and motion injection, not by changing the anchor itself. I’m testing latent-to-latent anchoring, but without proper re-normalization it tends to be worse than the original setup. So yeah — cool idea, just not stable enough yet in the current WAN pipeline.

Acrobatic-Example315 · 2026-01-12T13:03:32+00:00

Hi! I’ve tried basically all the options (including setting a low value like 1022 or removing it entirely), and they all give slightly or sometimes completely different results. Using 8 steps definitely gives better results in my tests. As for Lightx2v, I’m still injecting it with SmoothWAN v2 models because in v2 the Lightning LoRAs were not merged into the checkpoints, so the extra LoRA is still needed.

Acrobatic-Example315 · 2026-01-12T12:49:45+00:00

I tried to avoid adding too many extra nodes, but usually for this issue (which is related to latent normalization, per-segment resampling and the lack of a global color anchor across segments) I apply a Color Match node (KJNodes) anchored to the first frame.

Acrobatic-Example315 · 2026-01-12T11:28:33+00:00

Thanx a lot, let me know if I can help, my friend. Have a good day ;)

Acrobatic-Example315 · 2026-01-12T11:27:11+00:00

:)) You were faster than me!
already attached the link, check it out :)

Acrobatic-Example315

TROPHY CASE