Wan2.2 i2v (clarifications needed regarding settings on low vram system)
John6666:
WanMoeKSampler: boundary: 0.900 add_noise: enable steps: 12 cfg_high_noise: 3.0 cfg_low_noise: 3.0 sampler_name: euler scheduler: simple sigma_shift: 5.0 start_at_step: 0 end_at_step: 10000 return_with_leftover_noise: disable VAE: wan_2.1_vae.safetensors Video: 33 frames 512-640px long side fixed seed Disable: LoRAs upscaler interpolation face restore postprocessing
yup this did it. the two sd3’s were the culprits. you nailed it! its working now, no distortions, no artifacts, has better obedience and face permanence. now if i could only fix the quality part. everything has some kind of low def bloom, airbrushed, blended quality to it. this isnt just this specific setups issue. i noticed when i switched from [rapidWAN22I2VGGUF_q4KMRapidBase.gguf] to [wan2.2-i2v-rapid-aio-v10-nsfw-Q4_K.gguf] a week ago. [rapidWAN22I2VGGUF_q4KMRapidBase.gguf] basically kept true to the source image no matter what it was. even low res screengrabs. it just made whatever i fed it move. [wan2.2-i2v-rapid-aio-v10-nsfw-Q4_K.gguf] and the two low/high unets always gave me this weird dream sequence kind of bloom.
i tried the
| A | Q3_K_M | Q3_K_M | safest low-VRAM baseline |
|---|
its stable , no oom, no hick ups. im gonna move forward and test the B option. any setting changes for options A to tweak in order to squeeze more juice out of it before i move to the next step?
Discussion in the ATmosphere