automatic VS stable-diffusion-webui-ux

> 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.

If you're open to trying a fork of auto1111, I'd recommend using the Ui-UX fork of auto1111 by anapnoe. It has a big ui overhaul, one item of which is improved inpainting. Has move, zoom, and full a screen mode. Take a look at the screenshots and see if that seems to fit your need.

I'd highly recommend using the Ui-UX fork of auto1111 by anapnoe. It is designed with mobile in mind, and has a custom interface for img2img and inpainting.

If you want more than that, the only thing I know of is a fork that needs a fresh install: https://github.com/anapnoe/stable-diffusion-webui-ux

https://github.com/vladmandic/automatic or https://github.com/anapnoe/stable-diffusion-webui-ux

Yes that's the fork I'm using, it's got a great UX, and I much preferred it when it was working!

Seriously, if anyone wants to use Auto1111 (which supports all the important SD "extras") but are turned off by the clunky interface, try this fork: https://github.com/anapnoe/stable-diffusion-webui-ux. It has a much better UI, runs nearly every Auto1111 extension without issues AND only merges stable commits. If you were already considering InvokeAI (which is in itself a great downscaled SD environment) then try Anapnoe's webui. It's closer to bleeding edge, but without the actual bleeding.