stable-diffusion-webui-ux VS InvokeAI

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.

Probably not, since I have no idea what you're talking about. I've just been using the models that InvokeAI (2.3, I only just now saw there's a 3.0) downloads for me [0]. The SD1.5 one is as good as ever, but the SD2 model introduces artifacts on (many, but not all) faces and copyrighted characters.

[0] https://github.com/invoke-ai/InvokeAI

I actually used the rocm/pytorch image you also linked.

I'm not sure what you're pointing to with your reference to the Fedora-based images. I'm quite happy with my NixOS install and really don't want to switch to anything else. And as long as I have the correct kernel module, my host OS really shouldn't matter to run any of the images.

And I'm sure it can be made to work with many base images, my point was just that the dependency management around pytorch was in a bad state, where it is extremely easy to break.

> Anyways, hopefully this PR fixes the immediate issue: https://github.com/invoke-ai/InvokeAI/pull/5714/files

It does! At least for me. It is my PR after all ;)

The data being flagged is not in that github repo, it's fetched from elsewhere and I don't fancy spending time looking for it. The alert is for 'Sirefef!cfg' which has been reported as a false positive with a bunch of other stable diffusion projects (https://www.reddit.com/r/StableDiffusion/comments/101zjec/trojanwin32sirefefcfg_an_apparently_common_false/, https://www.reddit.com/r/StableDiffusion/comments/xmhukb/trojan_in_waifudiffusion_model_file/, https://github.com/invoke-ai/InvokeAI/issues/2773 )

I haven’t tried it recently, but InvokeAI runs on Mac. Invoke. I used to run on my MacBook, but have since gotten a Win laptop.

There are already a number of local, inference options that are (crucially) open-source, with more robust feature sets.

And if the defense here is "but Auto1111 and Comfy don't have as user-friendly a UI", that's also already covered. https://github.com/invoke-ai/InvokeAI

https://github.com/invoke-ai/InvokeAI should work on your machine. For LLM models, the smaller ones should run using llama.cpp, but I don't think you'll be happy comparing them to ChatGPT.

Stable Diffusion. /r/stablediffusion There are many tutorials on how to set it up locally and use it. InvokeAI is the easiest way to set it up. https://github.com/invoke-ai/InvokeAI

InvokeAI