automatic VS stable-diffusion-webui

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

* LLaVA model: I'll add more documentation. You are right Llava could not generate images. For image generation I don't have immediate plans, but checkout these projects for local image generation.

- https://diffusionbee.com/

- https://github.com/comfyanonymous/ComfyUI

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

I would love to be able to have a native stable diffusion experience, my rx 580 takes 30s to generate a single image. But it does work after following https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki...

I got this up and running on my windows machine in short order and I don't even know what stable diffusion is.

But again, it would be nice to have first class support to locally participate in the fun.

In Auto1111, that just uses Image.blend. :)

https://github.com/AUTOMATIC1111/stable-diffusion-webui/blob...

I used SDXL in automatic1111 webui for both images. Now that I think about it, the procedure I described was how I made this one, but the one that looks like an illustration was done in two steps. I used the canny ControlNet as I said for the outer part of the logo to preserve the shape of the fonts, but I had to turn it off for the boot to give SDXL leeway to add detail and make it look more like a boot.

That said, please do learn coding and don't get discouraged when somebody says to learn PyTorch or recommends using a Jupiter notebook with no further information on how to translate the skill into images. I would highly recommend some short term goals. Get your feet wet by taking apart the UIs. The comfy API documentation is here and the A1111 API documentation is here. There is a difference in completeness, welcome to programming. Writing nodes or plugins is also a good way to jump into this world. Custom wildcard logic might be very attractive to you if you aren't the type that want to deal with a nested file structure to simulate logic.

Possibly Unprompted? https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/8094

version: v1.6.1  •  python: 3.10.13  •  torch: 2.0.1+cu118  •  xformers: 0.0.20  •  gradio: 3.41.2  •  checkpoint: 6e8d4871f8