automatic VS sd-webui-lobe-theme

> it won't ever be a viable option

For production workloads, I generally agree. It's an unsupported hack with a questionable future, I wouldn't do anything money-making with it.

However, for tinkering and consumer workloads, it already works pretty well. Enough of cuDNN and cuBLAS work to run PyTorch and in turn, Stable Diffusion with https://github.com/lshqqytiger/ZLUDA - there's even a fairly user-friendly setup process already in https://github.com/vladmandic/automatic .

I was able to get a personal non-ML related project working on my AMD card in just a few minutes, which saved me a lot of development time before I then deployed the production workload on NV hardware (this is probably why AMD pulled the plug on the project - it's almost more of a boost to NV than anything else, AMD really need people to be writing code on ROCm to deploy on AMD datacenter hardware).

While I currently use SD.Next[1], I have tested ComfyUI locally with my AMD card. The UI can be daunting, but you learn quite a great deal about how a Stable Diffusion pipeline works. In addition some innovations and advances find their way into ComfyUI first.

[1] https://github.com/vladmandic/automatic

I used SD.NEXT ( https://github.com/vladmandic/automatic ) and https://civitai.com/models/82098/add-more-details-detail-enhancer-tweaker-lora and epicphotogasm_lastUnicorn

I found this thread on GitHub talking about how this was fixed in the latest version with an optional setting. I tried enabling it, as they mentioned, but it just resulted in an immediate CUDA out of memory error when starting generation. So it seems I'm actually needing the shared memory, which I assume is my issue.

As always, do check out our more detailed changelog, give us a quick install from our Repo, and stop by our Discord Server for any questions or help you may need.

SD.Next

Today I finally wanted to give SDXL a chance, so I set everythin up according to Vladmandic's Wiki https://github.com/vladmandic/automatic/wiki/SD-XL

I'm trying to get SDXL working on Vlad's SDNext, but I keep getting the error in the title when trying to run basic operations. I'm not sure what's going on, I followed his guide for it to a T.

We used an inference container based on SDNext, along with a custom worker written in Typescript that implemented the job processing pipeline. The worker used HTTP to communicate with both the SDNext container and with our batch framework.

upscayl is very approachable, but lacked many features i needed. i ended up using https://github.com/AUTOMATIC1111/stable-diffusion-webui after upscaling became part of my regular workflow, but for someone who just needs a few images enhanced, it's an ideal tool.

For the Git alternative, simply right-click on the location you want to put the Stable Diffusion and select “Git Bash Here”, then paste this on the CLI: git clone https://github.com/AUTOMATIC1111/stable-diffusion-webui

ComfyUI is similar to Houdini in complexity, but immensely powerful. It's a joy to use.

There are also a large amount of resources available for it on YouTube, GitHub (https://github.com/comfyanonymous/ComfyUI_examples), reddit (https://old.reddit.com/r/comfyui), CivitAI, Comfy Workflows (https://comfyworkflows.com/), and OpenArt Flow (https://openart.ai/workflows/).

I still use AUTO1111 (https://github.com/AUTOMATIC1111/stable-diffusion-webui) and the recently released and heavily modified fork of AUTO1111 called Forge (https://github.com/lllyasviel/stable-diffusion-webui-forge).

Seems like an interesting project. Regarding the name, is there permission to use something so similar to AUTOMATIC1111 [1]?

> Diffusers will Cuda out of memory/perform very slowly for huge generations, like 2048x2048 images, while Auto 1111 SDK won't.

Do we have some numbers on this? I have seen AUTOMATIC1111 fall-over whilst using only half the available of GPU VRAM - there seems to be some weirdness where it tries to allocate before de-allocating the last batch or something.

> You can use any of the 6 compatible RealEsrgran models/weights with our RealEsrgran pipeline for upscaling images. Here are the model ids:

I've previously had trouble trying to use AUTOMATIC1111 upscalers, it seems like it needs more GPU VRAM than just generating the image already upscaled.

[1] https://github.com/AUTOMATIC1111/stable-diffusion-webui

You might be thinking of Fooocus: https://github.com/lllyasviel/Fooocus

The Stable Diffusion web interface that got a lot of people's attention originally was Automatic1111: https://github.com/AUTOMATIC1111/stable-diffusion-webui

Fooocus is definitely more beginner friendly. It does a lot of the prompt engineering for you. Automatic1111 has a ton of plugins, most notably ControlNet which gives you fine grained control over the images, but there is a learning curve.

Stable Diffusion https://github.com/AUTOMATIC1111/stable-diffusion-webui

Make it into a stable diffusion server!

There's no link version, you have to run it locally. You install it from here

Repository: AUTOMATIC1111/stable-diffusion-webui · Tag: v1.7.0-RC · Commit: 48fae7c · Released by: AUTOMATIC1111