WAN 2.2 I2V 14B + Lightning 2.2 I2V, Pusa, FusionX
screenshot of workflow being review by moderators currently...
Workflow that uses a bunch of helpers and doesn't crush the LoRa action / motion. Just threw it together and configured with various tips and bits of info from comments on the site. It works well. Can gen 480p or 720p.
8/7
Uses the new Lightning 2.2 I2V, I was using a Char Lora, so the faces weren't an issue. If you are noticing issues with face variety, disable the high noise lightning lora. It gave me a tiny performance boost when enabled, but not really anything special. Might as well disable it.
but only on low noise.High noise Lightning is disabledre-enabled but see note aboveAfter some more testing it looks like having them both enabled is the slightly better optionsee note above
We also set the action LoRas to 2 on high noise and 1 on low noise. (sometimes, see Additional Info below)
Additional Info
With a powerful and strong LoRa like WAN Cumshot setting the high noise to 2.0 can affect prompt adherence negatively. If you set both high and low noise to 1.0 it will better adhere to prompt, but remember the trick if you need the boost on other LoRas.
Workflow set to 16fps but 24fps possible. With something like WAN cumshot LoRa enabled it needs to be set to 16 fps or it produces fast motion, my guess is it depends on what fps the lora was trained on. When using other LoRas (only tested a few) or just base model 24 fps works well. For example pov-tongue-job-wan-21-i2v works well at 24 fps and with this workflow
I'll continue to update this post with more information as I test and figure stuff out.
Contains
Fusion x phantom wan:
Pusa:
Lightning 2.2 I2V:
Example LoRa used in this workflow:
Description
minor tweaks
FAQ
Comments (3)
I'm having trouble making sense of what the approach is here.
In the workflow, both Lightning High and Low LoRAs are enabled at 1.0-1.1 strength. Meanwhile, the action LoRA (Cumshot High and Low in this case) has its High disabled at 2.0 strength, and its Low enabled at 1.0 strength.
Yet there is also a note in the workflow:
"HIGH NOISE set to 2
LOW NOISE set to 1. Have seen 1.1 suggested but haven't tried yet.
Lightning set on LOW only. HIGH NOISE lightning disabled. Helps not to kill cum/motion"
I infer from the note that it's the Lightning High LoRA that should be disabled, yet it's actually the action High LoRA that is disabled. What am I missing?
+5 sec. videos have the same start and end. I don't want this. How can I avoid this behavior?
Works well, just need to make sure all the resources are available but that is given in the notes. Thanks !
Request : If you can use PowerLoraLoader or similar to add more loras that would be great !