To be fair- Auto has been acquiring features at an insane clip (recently getting banned from the SD discord for accusations of code theft lol)
I think Invoke is competitive for now, but biggest advantage is an improved UX, and a large community with an ambitious roadmap focused more on enthusiasts/pros.
I’d give it a whirl and see where you end up preferring to do your SD projects :)
Oh I see that my comment might be interpreted as snarky, I was literally just asking to please list the stuff that are new or different cause that would be very helpful for everyone.
I legitimately think the answer is -
- Experimental/novel SD features, Automatic typically has them first
- Better UI/UX and exploration/gallery workflows, Invoke.
From a feature perspective, both have their own flavor of certain features.
Goal of Invoke is to eventually have prompt/concept library, a node-based workflow UI (with the ability to share techniques), etc.
It’s kind of a - switch if you want a better UX now; keep an eye on it if you want new workflow solutions long term.
- a gallery to easily compare generations and easily regenerate images with small modifications
- responsive design --> works great on mobile, swipe left/right to switch between pictures in same generation and up/down to switch to another generation to compare
Also if you don't have the hardware, you can also get images for free using the Stable Horde (https://stablehorde.net), a cluster of backends provided for free by volunteers.
Automatic1111's webui is what 90% of the StableDiffusion community uses but he recently made the decision to use a company's proprietary code after it was leaked by a hacker and when confronted about it, instead of removing it as requested he chose to lie about it despite the git history evidence and the fact that the paper he claimed to have used as reference wasn't related at all to the techniques used by the stolen code.
The company whose code was stolen works closely with the man behind SD and the decision was made to merely ban him from the community instead of torpedo-ing the repo via DMCA.
This seems to have been proven to not be the case, and the code in-fact originates from a pre-stable-diffusion MIT licensed repo.
It's not even a particularly large or interesting piece of code, the only reason why it's controvertial is because of the code is only necessary to use the NovelAI leaked models.
I'd be interested to see that repo since one of the commits to Automatic's github is Anlatan's code while a second commit changes function names and tweaks the code slightly in an apparent effort to disguise it's origin. Most of the discussion about this has been on 4chan where the amounts of misinformation has been staggering before it pretty much devolved into "it doesn't matter if their code was taken, it should have been open source anyway".
As you can see, that repo from 2 years ago even originates the "# attention, what we cannot get enough of" comment and is an exact 1:1 match to Automatics commit, while the one from NovelAI even has a small change in the if clause that Automatic doesn't have.
The code that was taken from Anlatan is actually this:
https://user-images.githubusercontent.com/23345188/194727441...
But that same GitHub issue also shows code from the lucidrains repo (the picture you've linked there) and people have latched onto it saying nothing was taken when the picture I linked is right above it containing code that doesn't exist outside the leaked code and Automatic's fork.
One thing is that invoke-ai can be run via CLI or possibly programatically. I haven't found a good way to do that with the automatic GUI. Personally, I've also found features in automatic to be buggy. For example, batching seems to always break the UI for me personally. With the invoke-ai fork, I can run the CLI and produce images all night if I want to.
The bees knees would be being able to use automatic as a CLI or with some programmatic interface, because it is more feature rich. But I haven't seen anything that allows me to do that yet, so I'm stuck to its clunky UI or to use invoke-ai.
Like I mentioned elsewhere, https://github.com/cmdr2/stable-diffusion-ui is pretty popular, and is a 1-click installer for Win and Linux (Mac coming soon). Quite a lot of features, and well-liked by users for its easy-to-install and user-friendly GUI.
Comments
Is there anything new here that might interest an existing user of auti's gui to switch?
To be fair- Auto has been acquiring features at an insane clip (recently getting banned from the SD discord for accusations of code theft lol)
I think Invoke is competitive for now, but biggest advantage is an improved UX, and a large community with an ambitious roadmap focused more on enthusiasts/pros.
I’d give it a whirl and see where you end up preferring to do your SD projects :)
Oh I see that my comment might be interpreted as snarky, I was literally just asking to please list the stuff that are new or different cause that would be very helpful for everyone.
Oh, no snark interpreted! Very valid question.
I legitimately think the answer is - - Experimental/novel SD features, Automatic typically has them first - Better UI/UX and exploration/gallery workflows, Invoke.
From a feature perspective, both have their own flavor of certain features.
Goal of Invoke is to eventually have prompt/concept library, a node-based workflow UI (with the ability to share techniques), etc.
It’s kind of a - switch if you want a better UX now; keep an eye on it if you want new workflow solutions long term.
Or you can stay on automatic1111 and use https://diffusionui.com/b/automatic1111 for better UX.
You can use https://diffusionui.com/b/automatic1111 once the automatic1111 webui is running:
- better inpainting
- a gallery to easily compare generations and easily regenerate images with small modifications
- responsive design --> works great on mobile, swipe left/right to switch between pictures in same generation and up/down to switch to another generation to compare
Here is the repo: https://github.com/leszekhanusz/diffusion-ui
Also if you don't have the hardware, you can also get images for free using the Stable Horde (https://stablehorde.net), a cluster of backends provided for free by volunteers.
You can test it here: https://diffusionui.com/b/stable_horde
Automatic1111's webui is what 90% of the StableDiffusion community uses but he recently made the decision to use a company's proprietary code after it was leaked by a hacker and when confronted about it, instead of removing it as requested he chose to lie about it despite the git history evidence and the fact that the paper he claimed to have used as reference wasn't related at all to the techniques used by the stolen code.
The company whose code was stolen works closely with the man behind SD and the decision was made to merely ban him from the community instead of torpedo-ing the repo via DMCA.
This seems to have been proven to not be the case, and the code in-fact originates from a pre-stable-diffusion MIT licensed repo.
It's not even a particularly large or interesting piece of code, the only reason why it's controvertial is because of the code is only necessary to use the NovelAI leaked models.
I'd be interested to see that repo since one of the commits to Automatic's github is Anlatan's code while a second commit changes function names and tweaks the code slightly in an apparent effort to disguise it's origin. Most of the discussion about this has been on 4chan where the amounts of misinformation has been staggering before it pretty much devolved into "it doesn't matter if their code was taken, it should have been open source anyway".
This is what other people have found over on reddit: https://reddit.com/r/StableDiffusion/comments/xzipjx/automat... According to that comment, this (https://user-images.githubusercontent.com/23345188/194727572...) is allegedly the only reasonable match with the leaked code from NovelAI, but note that I have not verified that myself, and since NovelAI/Stability never said which part they take issue with it is hard to tell. This is the file in that other repo that the code actually seems to originate from https://github.com/lucidrains/perceiver-pytorch/blame/main/p...
As you can see, that repo from 2 years ago even originates the "# attention, what we cannot get enough of" comment and is an exact 1:1 match to Automatics commit, while the one from NovelAI even has a small change in the if clause that Automatic doesn't have.
The code that was taken from Anlatan is actually this: https://user-images.githubusercontent.com/23345188/194727441... But that same GitHub issue also shows code from the lucidrains repo (the picture you've linked there) and people have latched onto it saying nothing was taken when the picture I linked is right above it containing code that doesn't exist outside the leaked code and Automatic's fork.
One thing is that invoke-ai can be run via CLI or possibly programatically. I haven't found a good way to do that with the automatic GUI. Personally, I've also found features in automatic to be buggy. For example, batching seems to always break the UI for me personally. With the invoke-ai fork, I can run the CLI and produce images all night if I want to.
The bees knees would be being able to use automatic as a CLI or with some programmatic interface, because it is more feature rich. But I haven't seen anything that allows me to do that yet, so I'm stuck to its clunky UI or to use invoke-ai.
Like I mentioned elsewhere, https://github.com/cmdr2/stable-diffusion-ui is pretty popular, and is a 1-click installer for Win and Linux (Mac coming soon). Quite a lot of features, and well-liked by users for its easy-to-install and user-friendly GUI.