Closed freebag668 closed 1 year ago
Hello again. So you're saying that latent lora separation broke. What's the original file's created / modified date? Do you happen to know which version of webui and the extension you were using to generate it, before the windows format? I haven't gotten latent mode working properly yet, but if you could try to downgrade the regional extension to the version that worked (according to the file date), we may be able to pinpoint the faulty commit. It might also be caused by the webui version, but that's more difficult to test, so we'll start with the extension.
Edit: Is it from before or after we fixed #32?
Hello again. So you're saying that latent lora separation broke. What's the original file's created / modified date? Do you happen to know which version of webui and the extension you were using to generate it, before the windows format? I haven't gotten latent mode working properly yet, but if you could try to downgrade the regional extension to the version that worked (according to the file date), we may be able to pinpoint the faulty commit. It might also be caused by the webui version, but that's more difficult to test, so we'll start with the extension.
Edit: Is it from before or after we fixed #32?
https://github.com/hako-mikan/sd-webui-regional-prompter/issues/32 It's after fixing it It worked well when it was fixed
Alright. Can you try this version and see if it works correctly? Also, please run with debug toggled and copy the output. https://github.com/Symbiomatrix/sd-webui-regional-prompter/tree/Ddim1 Or this one: https://github.com/hako-mikan/sd-webui-regional-prompter/tree/b772bfec90670030e95df8ebdf509ade927f6ff5 Basically, just need to overwrite rp.py and reload.
https://github.com/Symbiomatrix/sd-webui-regional-prompter/tree/Ddim1 test https://postimg.cc/gallery/Y0mgTZ9 https://anonfiles.com/X934Pdj6z9/01_txt Image quality error
https://github.com/hako-mikan/sd-webui-regional-prompter/tree/b772bfec90670030e95df8ebdf509ade927f6ff5 test https://postimg.cc/gallery/B3m0TYs https://anonfiles.com/f461Pajez9/mikan_txt Image quality error
Image quality errors occur in both versions
Okay, so more likely caused by a webui version change. Let's try to compare a simpler prompt, standard dimensions and no hires. I ran this on the 14/3 version, it probably won't be exactly the same for you as there were some seed breaking changes. Is the quality of the image below similar to what you've had before? And does your current version show the same quality degradation you posted above for these settings?
https://postimg.cc/gallery/2DQGVkh I set it up and applied it similarly b32d8fe8 (Fri Apr 7 16:05:28 2023) Image quality error
So if even basic settings aren't doing well, I guess it's something to do with the new lora application method. I can't upgrade to that version for now, perhaps you could try downgrading to the previous version, https://github.com/AUTOMATIC1111/stable-diffusion-webui/tree/a0d07fb5807ad55c8ccfdfc9a6d9ae3c62b9d211 (Unless hako would like to take a shot at it.)
https://github.com/AUTOMATIC1111/stable-diffusion-webui/tree/a0d07fb5807ad55c8ccfdfc9a6d9ae3c62b9d211 test https://postimg.cc/gallery/jdkJdD2 b9b31c4d (Sun Apr 9 14:38:03 2023) Image quality error
Can you please add the debug printout for this as well?
https://github.com/AUTOMATIC1111/stable-diffusion-webui/tree/a0d07fb5807ad55c8ccfdfc9a6d9ae3c62b9d211 test https://postimg.cc/gallery/HY2DRdM https://anonfiles.com/r6N1j2kez1/9d211_txt b9b31c4d (Sun Apr 9 14:38:03 2023) Image quality error debug printout added it
I think I might finally have a breakthrough. I upgraded to the latest locon extension from my old one (I think it's the 04/03 version, 2e9a79533987e6b454c87705fc4e178febac4fe0), and I'm finally getting garbage, with the same settings. It's possible, seeing as some additional lora functions were overridden and that's pretty much the only difference between our debug printouts. Can you disable / downgrade your locon extension and see if it helps?
Edit: But it might just be from omitting easynegative. Ugh. You don't happen to be missing that embedding, right? Do you happen to have the list of extensions you had installed before the format?
@Symbiomatrix Thanks for the validation. In my environment, LoCon extension appeared to be unrelated. After all, what are the conditions under which this problem occurs?
@hako-mikan Checkpoint: meina pastel v4 Loras: roxyMigurdiaLora_offset , megumin_v10 (not sure which is that particular one, I used "Megumin (KonoSuba) - arch wizard outfit") We're attempting to replicate the results in https://postlmg.cc/rd26VT0z . So far, every attempt has fallen short of it - so you might say, any conditions. We know for sure regional's version was https://github.com/hako-mikan/sd-webui-regional-prompter/tree/99ea794c8512caf24f469527d97f06a17d74f6d8 . The webui version is unclear, but we tried either the latest one, or before the lora change, and on my end 14/3.
Since perfect replication might be impossible (due to various undocumented settings or extension overrides in play), I tried to test a less complex prompt:
2girls, bento BREAK[common] <lora1> BREAK <lora2>
I'm under the impression that the migurdia lora might be malfunctioning when used in regional, as without easynegative it's showing various forms of discolouration, even with a lower weight, compared to a non regional prompt. Megumin does not suffer the same level of degradation. Does it being "offset" have any relevance?
Observe: Regionless, crisp detail.
Migurdia one side (low weight), looks like a picasso whereas other side is unchanged.
Migurdia both sides, completely off.
Megumin on standard weight holding up quite well.
In fact, even when the region is 1,0 this degradation occurs, so that might be something that can actually be compared on the tensor level. I hadn't thought of that before.
EDIT: Correction, thanks to freebag having posted the full page, we do know his previous commit - it was indeed the the latest webui.
disable test https://postimg.cc/gallery/0byh3Qf https://anonfiles.com/2dB5w3k3zf/disable_txt Image quality error
https://github.com/KohakuBlueleaf/a1111-sd-webui-locon/tree/2e9a79533987e6b454c87705fc4e178febac4fe0 downgrade test https://postimg.cc/gallery/DXFLpcp https://anonfiles.com/C2D7w4k6z1/c4fe0_downgrade_txt Image quality error
@freebag668 Do you have any other loras beside migurdia? Do they show the same quality error in regional?
other lora test
2girls, bento BREAK
@freebag668 Okay, I think the results are at least somewhat similar. It's not as pronounced as migurdia, but definitely has a discernable effect. I wonder if xformers' nondeterminism might be causing slight variations; megumin looks significantly different (but then I'm probably not using the same lora as yours, so that might be the reason).
https://civitai.com/models/23000 https://civitai.com/models/10782 https://civitai.com/models/33990 https://civitai.com/models/11866/meinapastel This is the model and LORA that I used for the test
Is there anything else I can test?
There are certainly cases where the quality is lower, but this has been the case for some time. I was able to reproduce the example I am giving in the ReadMe, but at the same time, applying LoRAs such as megumin produced images with quality issues. In general, when multiple LoRAs are used, the quality tends to drop due to the interaction. This is avoided by reducing the strength of the LoRAs or by applying them in a Block weight. Therefore, I think that the quality degradation is normal.
Are the following issues related to this? https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/9118 https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/9207
On earlier versions of the WebUI, the results were also a bit worse.
What happens if you use the settings you're having trouble with and only decreasing strength of LoRA?
If you just turn off the extension, you can't get such a serious blurred result. If you reduce the weight of both to 0.5, the left side still has a similar bokeh but lighter.
I'm going to try an older version of the extension.
I reverted to the earliest extended version, no any improvement, you can test Latent Couple + Composable Lora.
Based on my own testing, I think the problem lies with the checkpoints and the Lora model itself, changing any of them can see a significant improvement.
https://postimg.cc/gallery/vs6yZq0 The pictures here are made using a Regional Prompter You can download the png file to view the information
After seeing these pictures, I am 90% sure that your results are obtained in Attention mode. I can get similar results.
https://drive.google.com/file/d/1KzkMXpxL_rsBOAuBHyzqd3B7tYpnm1U_/view?usp=share_link https://github.com/hako-mikan/sd-webui-regional-prompter/issues/32 This is a video that I filmed while doing a bug test on April 6 If you download the video and watch it closely, the date will be confirmed Only the first picture has a quality error It's normal from the second picture
https://postimg.cc/LhS1pmxj (2023-04-06) https://postimg.cc/WFpxYHcT (2023-04-04) This is a capture when I make a picture Only the first picture has a photo error The rest of the picture is normal
Latent mode is used
The latest version displays all photo errors
What extension is causing so much "up_model" output?
I rolled back the extended version many times, until the Latent just added, and none of the similar results can be reproduced. You can go back to the old version through the extended commit history, and then feedback which version can get the effect you expected, otherwise it is difficult to locate the problem.
What extension is causing so much "up_model" output?
That should be regional, on webui 25/3+ version. There's a ton of layers which loras affect. Not sure under which circumstances it's up_model or weight.
def changethedevice(module):
if type(module).__name__ == "LoraUpDownModule":
if hasattr(module,"up_model") :
print("up_model")
module.up_model.weight = torch.nn.Parameter(module.up_model.weight.to(devices.device, dtype = torch.float))
module.down_model.weight = torch.nn.Parameter(module.down_model.weight.to(devices.device, dtype=torch.float))
else:
print("weight")
module.up.weight = torch.nn.Parameter(module.up.weight.to(devices.device, dtype = torch.float))
if hasattr(module.down, "weight"):
module.down.weight = torch.nn.Parameter(module.down.weight.to(devices.device, dtype=torch.float))
You can go back to the old version through the extended commit history, and then feedback which version can get the effect you expected, otherwise it is difficult to locate the problem.
We know for certain which webui and regional version he had been using: webui was the latest, the commit is shown at the bottom of this image from the issue. And the extension version was right before and then after the lora fix PR. What is unknown, is whether there were other extensions in play, or specific webui settings. That regional might've somehow run on attention instead of latent seems plausible quality wise, but attention completely lacks lora separation; the results are very different in attention compared to latent with a low weight on migurdia. In any case, if there's some magical setting which can improve latent's lora stability, or an unknown bug in the implementation which was bypassed, the search might be worthwhile.
Attention, identical settings:
Latent, low weight on migurdia:
If I knew more about computers I could help, but I'm sorry I can't.
I switched to the latest WebUI, and then used the same extension version as his (525741c), and got terrible results, and in my case the output was "weight", I believe there are other factors causing the difference.
I forgotten deleting print("up_model")
.
It's for debugging.
@Sakura-Luna It's an interesting difference, but likely a red herring. I asked freebag to copy his debug printouts earlier in this issue, and he still receives the up_model message along with the degradation.
@hako-mikan Question: Would it make sense that running a single lora in base, with base ratio = 1, be different compared to regionless as well? Does the latent method alter the application that much?
@Symbiomatrix In that case, result will be same, but not same now. So something wrong.
@Symbiomatrix Not exactly. It is not exactly the same because I followed the Composable LoRA and erasing LoRA's impact on negative prompts. Maybe this is where it is affecting. I will test turning off that feature.
You mean, that in denoiser_callback only text_cond is flipped back via params.text_cond[b+a*self.batch_size] = ct[a + b * areas]
and not text_uncond?
No. When applying LoRA to Textencoder. Weight of loRA is set to 0. Also, Weight of LoRA is set to 0 when calculating in unet of uncond.
Ah, okay. I know that part - te_llist & u_llist's additional elements. So that's what it means.
We can disable this feature.
comment out line 1296
#regioner.ndeleter()
Surprisingly, my sample in README get terrible result. But result of megumin was improved.
Sorry I'm sleepy(2:00 AM now in japan)
My bad, I hadn't noticed the time. Much obliged. Good night.
Can confirm: Base lora becomes identical (both single and dual lora), but in region megumin alone at weights of >0.2 causes the other side to become noise very quickly. Migurdia less so, oddly. Unbalanced?
Edit: Te_llist weights seem to have little effect on the output. for these loras at least. Here, megumin's general u only is nullified. And here, megumin's te + u.
LoRA settings regarding negative prompts have been added as an option. The default is off; turning it off seems to give better results when using LoRA such as megumin.
https://postimg.cc/gallery/WjQNN9N https://postimg.cc/gallery/tXYcRv0/4f2b98c6
disable LoRA in negative textencoder disable LoRA in negative U-net
We tested the option with the option on and off In my situation, every picture has an error
https://civitai.com/models/33990 https://civitai.com/models/24679 https://civitai.com/models/23000 https://civitai.com/models/10782 test lora
https://civitai.com/models/11866 test model
That update was not released to fix your problem.
Here is the extension version you used before, you can change the name to sd-webui-regional-prompter
after decompression, and then copy it to the extensions
folder under the SD installation location.
That update was not released to fix your problem.
Here is the extension version you used before, you can change the name to
sd-webui-regional-prompter
after decompression, and then copy it to theextensions
folder under the SD installation location.
I got it Thank you always for your hard work
Hello freebag. Sorry I'm late, but #120 should expand sakura's negative parameters to control individual loras, so you can mess around with those once merged. Wrote an explanation about it in known issues.
https://postimg.cc/H8Wsc8RS Images you created previously (Latent mode using 2 Lora)
https://postimg.cc/rd26VT0z PNG INFO -> Send to txt2img
https://postimg.cc/FfzPXnG1 https://postimg.cc/jwrZndtn Images created with the same setting The color of the image is outputting strangely
https://postimg.cc/XZx3Lggn https://postimg.cc/bSymTQ3f The output of the image is weird even if you use a simple prompt
https://postimg.cc/m110vv0y Extension Version b32d8fe8 (Fri Apr 7 16:05:28 2023)
I format the windows and I installed a new webui, but it's the same symptom
Is there a solution?
Thank you always for your hard work