Closed Edgar-Nino closed 1 year ago
The burning is likely to be an upstream bug with img2img color correction. I'll look into it and submit a bug report if so.
Under the config tab, I set it to do color correction for img2img by default, so you can disable it there. The behaviour where it starts burning after using the Krita plugin is because the webUI & the plugin store their settings separately (i.e. color correction for img2img is off in the webUI).
I think I might decide to make color correction individually toggleable for img2img vs inpainting (where its more useful).
Oh I was thinking that was the case with upstream, but it seemed strange to me that only the first image was modified Thanks!!!
btw, I also don't know why its occuring for specifically the first image. Internally, its a turn on/off sorta thing, so it might mean the upstream bug causes color correction to be applied only to the first image.
Describe the bug
Hi, as the title says, img2img in krita always burns the first image, it seems as if it is trying to match the colors of the source image
after you use img2img in krita, all the first images start to burn in Stable Diffusion UI and Krita
if you don't use img2img in krita, the images don't burn
To Reproduce
Steps to reproduce the behavior:
Screenshots
EDIT: I attached a better example
ORIGINAL SOURCE
GRID BEFORE IMG2IMG IN KRITA SAME SEED
GRID AFTER IMG2IMG IN KRITA SAME SEED
Desktop:
Additional context
I was using two embeddings and a merge of SD 1.4 and WD 1.3