stable-diffusion VS diffusers

I am using this repo: https://github.com/basujindal/stable-diffusion and it works fine with e.g. this model: https://huggingface.co/CompVis/stable-diffusion-v-1-4-original

That includes this optimized version : https://github.com/basujindal/stable-diffusion

Ah, I wasn't aware of that. I use this version, which was very easy to set up and use by CLI.

Used repo recommended in https://github.com/CompVis/stable-diffusion/issues/39 to use https://github.com/basujindal/stable-diffusion - same result.

As per the best solution I found, I have download this (https://github.com/basujindal/stable-diffusion) version and pasted the optimizedSD folder in the main (user>stable-diffusion-webui) folder as per site instruction.

The git says you can simply grab the OptimizedSD folder and paste it into the installation path, which I did. However, I'm not sure how to call upon its functionality. Again, the reddit post says >Remember to call the optimized python script python optimizedSD/optimized_txt2img.py instead of standard scripts/txt2img. Though I'm not even sure where that script call is performed. Any ideas? Thanks in advance!

I'm missing something about the random factor, from the sample code from https://github.com/huggingface/diffusers/blob/main/README.md

Hey people, I noticed that combining these two methods in a single forward pass increases the controllability of the generation quite a bit. I was kind of puzzled that sometimes ControlNet yielded better results than T2IAdapter for some cases, and sometimes it was the other way around, so I decided to test both at the same time, and results were quite nice. Some visuals and more motivation here: https://github.com/huggingface/diffusers/issues/5847 And it was already merged here: https://github.com/huggingface/diffusers/pull/5869

Open Parti Prompts: The better way to evaluate diffusion models (repo)

You have disabled the safety checker for by passing `safety_checker=None`. Ensure that you abide to the conditions of the Stable Diffusion license and do not expose unfiltered results in services or applications open to the public. Both the diffusers team and Hugging Face strongly recommend to keep the safety filter enabled in all public facing circumstances, disabling it only for use-cases that involve analyzing network behavior or auditing its results. For more information, please have a look at https://github.com/huggingface/diffusers/pull/254 .

For developers, TensorRT support also exists for the diffusers library via community pipelines. [1] It's limited, but if you're only supporting a subset of features, it can help.

In general, these insane speed boosts comes at the cost of bleeding edge features.

[1] https://github.com/huggingface/diffusers/blob/28e8d1f6ec82a6...

I was training sdxl UNET base model, with the diffusers library, which was going great until around step 210k when the weights suddenly turned back to their original values and stayed that way. I also tried with the ema version, which didn't change at all. I also looked at the tensor's weight values directly which confirmed my suspicions.

Merging LoRAs is essentially taking a weighted average of the LoRA adapter weights. It's more common in other UIs.

diffusers is working on a PR for it: https://github.com/huggingface/diffusers/pull/4473