mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
026d095afe
`LatentsField` objects have an optional `seed` field. This should only be populated when the latents are noise, generated from a seed. `DenoiseLatentsInvocation` needs a seed value for scheduler initialization. It's used in a few places, and there is some logic for determining the seed to use with a series of fallbacks: - Use the seed from the noise (a `LatentsField` object) - Use the seed from the latents (a `LatentsField` object - normally it won't have a seed) - Use `0` as a final fallback In `DenoisLatentsInvocation`, we set the seed in the `LatentsOutput`, even though the output latents are not noise. This is normally fine, but when we use refiner, we re-use the those same latents for the refiner denoise. This causes that characteristic same-seed-fried look on the refiner pass. Simple fix - do not set the field in the output latents.