I've done my best to place most nodes that you'd want to configure at the lower portion of the flow (roughly) sequentially, while most of the operational / backend stuff sits at the top. Nodes have been labeled according to their function as clearly as possible.
Beyond that;
NAG Attention is in use, so it is recommended to leave the CFG set to 1.
The sampler and scheduler are set to uni_pc // simple by default as I find this is the best balance of speed and quality. If you don't mind waiting (a lot, in my experience) longer for some slightly better results, then I'd recommend res_3s // bong_tangent from the RES4LYF custom node.
I have set the default number of steps to 8 (4 steps per sampler) as opposed to 4, as here is where I see the most significant quality / time tradeoff - but this is really up to your preference.
This flow will save finished videos to ComfyUI/output/WAN/<T2V|T2I|I2V>/ by default.
For I2V, I find that generally Wan 2.2 does better if the input image's resolution is above the resolution you are sampling at (as opposed to resizing to fit the sampling resolution prior to executing) - but I haven't tested this super extensively.
The custom node flow2-wan-video will cause a conflict with the Wan image to video node and must be removed to work. I have found that this node does not get completely removed from the custom_nodes folder when removing via the ComfyUI manager, so this must be deleted manually.
lightx2v_T2V_14B_cfg_step_distill_v2_lora_rank64_bf16.safetensors
model.safetensors (renamed to clip-vit-large-patch14.safetensors)
T2V: UP
T2V Low Memory:
I2V: UP
I2V Low Memory:
If you want to support my work, Buy me a Coffee!
Major Update - Infinite Generation, Smart Best Frame Detection, etc...
Fixed metadata saving
Fixed duplicate segment saving
Go ahead and upload yours!
Your query returned no results β please try removing some filters or trying a different term.