huggingface_hub VS diffusers

Something to think about:

https://github.com/huggingface/huggingface_hub

Yes! We have a well documented Python library (https://github.com/huggingface/huggingface_hub) and public endpoints (https://huggingface.co/docs/hub/api#endpoints-table) you can use to retrieve information about the models and potentially build UIs with specific use cases in mind

i think if you search for pixel art here there are some models worth checking out: https://huggingface.co/

I received another error saying OSError: We couldn't connect to 'https://huggingface.co' to load this model, couldn't find it in the cached files and it looks like ./vae is not the path to a directory containing a file named diffusion_pytorch_model.bin

I plan to release it on https://huggingface.co/, where all this cool AI stuff is available for free for everyone that wishes to try it.

For this I used mainly the chainner application with models from here but I also used the google colab automatic1111 stable diffusion webui (for example for Lanczos) and also spaces fromhuggingface like this one or then from the replicate.com website super resolution collection.

you will now need to create a huggingface account ( https://huggingface.co/) if you haven't already. When you have, go here and accept the terms, https://huggingface.co/runwayml/stable-diffusion-v1-5. When you have done both, click on your profile icon and go to settings. Click access tokens and then create token, name it whatever you want, select "write". When you are finished with all this, then you can run the next cell which is the hugging face cell. It will ask for a token, you copy and paste what you just created.

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