This repo sucks big time

[chopthesalami]

Yes, I am sorry for this. I feel guilty because as a developer, I KNOW how much free time and enthusiasm went into creating this.

But... do we really need to have hundreds of users every month who know nothing about the completely breaking changes? Do we need updates that f*k up everything every 2 weeks? Like, totally, so that users flood the forums and complain and cry about not being able to use it?

I understand. Gradio is a problem.

But how about testing changes BEFORE updating the main branch? Outlandish idea? How about putting some capable people in charge of this awesome repo? No? Okay. Lets have monthly update cycles of break and repair, because apparently this is normal behaviour, right?

Maybe in understaffed dev compartments. No communication. 2 weeks absent. Ok. Everyone has a busy life. 3 weeks absent, totally sh*tty updates. Everything breaks, no tests, everything sucks.

A1111 if you started to hate your project just give it to someone who wants to do it

[Kilvoctu]

Works on my machine.

[iparanoid]

Works on my machine.

[JemiloII]

This post is not about it working or not. The repo is just a hot mess where if you want to update to get new features. The entire application can just break. It's too inconsistent. Shotty code, poor UI, and the list can go on. Remember, the poster, isn't hating, he is just passionate and like to see the repo improve its releases.

[DuckersMcQuack]

Can attest to that. After updating mine to dev branch to test the new tensorRT thing (yes, that one is broken as well, gets as far as making all the small files that makes up the different parts of the model, then caves in when it's gonna assemble the final onnx), or updating in general, my img2img is now just broken because now seemingly "scripts.py", line 456, in run
processed = script.run(p, *script_args)" is now missing 27 arguements, so i can't upscale nor img2img at all anymore. Have to downgrade/fresh install to get stuff working again. Hell, even regular img2img is broken. tonnes missing in scripts.py.

[FurkanGozukara]

This is a tremendous software for free. I don't think you can expect better

[Dormouse123]

I agree. As a non-developer and relatively beginner level user, I often get frustrated at things not working, but as you say, this free software -that we could never have dreamed of having just couple of years back- so a little respect and understanding for those bright sparks who keep at it with little thanks wouldn't go amiss.

[BetaDoggo]

The biggest issue in my opinion is the massive number of extensions that add a ton of complexity to every install and make debugging issues much harder. I love how easily the ui can be modified but it definitely hurts its stability. There's no way to test everything on every hardware config with every extension for every commit so I think we're stuck for now. A stable and dev branch might help but that would make the extension issue even worse.

[quasiblob]

How would it make extension issue worse? I mean, most of the extensions are created by third party. If one develops an extension for a specific version it should work just fine. Then when a new stable comes out they can update their extension to work with it, if there are some breaking changes or new bugs appearing because of web ui code updates. And testing extensions is responsibility of extension authors and users can help them too. Those who want stable environment probably won't care if they don't have the newest things ASAP those come out.

[BetaDoggo]

I guess that would work, though I'm sure many users would likely update their stable versions as soon as a new one became available without checking for compatibility. Maybe some kind of freeze period where the next stable version is finalized for a week or so to give devs time to validate their extensions before packaging it as a release would work.

All of that would require extra time and cooperation so I don't think it's possible unless another person or group was given permission to create and manage these releases.

[quasiblob]

I don't get it. New version of web ui gets released. Extension makers notice this. Then they can see if their extension works or doesn't with the new updated version of web ui. If there needs to be changes to their extension, then they can implement the code changes. Haven't checked what is the case with web ui, but most 3D software add-ons / extensions have version numbering and some even had different versions for specific software version. Check Blender add-on, those have block of data which defines the version of add-on, and the version of Blender this specific add-on supports (2.7x, 3.x). So here too, extensions should have information about which version of A1111 web ui it supports. Then it becomes only an issue of is a specific extension supporting the latest version of web ui. At least with 3D software, it has been so that popular extensions get updated by their authors quickly, and less popular ones will not get updates immediately and some less popular will wither away and die. It requires no co-operation, unless those extension makers feel like there is something missing in the software API, which prevent creating properly working extension or something, but that is another thing, more like a feature request, not related to updating an extension. This way user can update the software, and see which extensions are supported. If not everything he/she needs is updated to support the latest version, then roll back to older version.

[eadnams22]

I think part of the challenge is that the extension authors don’t want to fix bugs(or can’t) that are rooted in WebUI, and would rather WebUI fix those bugs.

I know of a few authors who have pulls waiting to be merged here that fix WebUI, because the issue isn’t with their extension.

Which wouldn’t be an issue if this wasn’t managed by only one person, who can’t be on this 24/7.

I think it needs a trusted team of contributors.

[elchupacabrinski]

Why is the infinitely loading Checkpoint dropdown not solved yet? That seems like such an easy fix

[Alchete]

We're re-living the VHS / Betamax wars, where the winner supports one feature (plugins) while the loser with superior-tech and UX, doesn't.

This is becoming an increasingly sad situation.

• Single person running the entire repo which is now the de-facto interface for SD
• No development branch, so everything breaks on almost every merge
• Growing disinterest from owner, so merges and updates only happen every 2-3 weeks without any public communication
• The UI toolkit, Gradio, is WOEFULLY overmatched in an increasingly complex UI

And, also, as a fellow developer, it brings me no pleasure to point these things out, as I know how thankless and time-consuming the job is.

[quasiblob]

"Growing disinterest from owner" - has he mention somewhere that he is no longer interested? Edit - meaning that maybe he is simply busy with other stuff.

[davehornik]

No development branch

Could you please use your f eyes?
There's a dev branch since August 2022, and also "release-candidate".
3324f31

But for yall its better to complain and cry rather than doing a bit of research.

[catboxanon]

For posterity, that is incorrect. Dev branch was only made two weeks ago, so one month after this discussion was opened (not that I agree with this discussion topic of course). #9311 (comment)

[econundrum]

I sort of agree but in view of the fact they are doing all the work for free in their own time, I'm willing to tolerate the fact it's not being done in a very professional way. though improvements would indeed be welcome.

[eadnams22]

Nothing have some trusted contributors who can merge wouldn’t fix, really.

[sarpsomer]

You joined GitHub
[on March 29, 2023]
Zero contribution
Zero support (payment, coding, wiki contribution,....)
You don't have a right to say "This repo s*** big time"

Others who have spend a lot of time to answer a user who has below average IQ; please consider the fact that
Gradio updated to 3.21 version on 14th March
Pytorch updated to 2.0 version on 15th March

I can only say some people really hate the owner of this repo for previous or personal issues.

[playlogitech]

You joined GitHub [on March 29, 2023] Zero contribution Zero support (payment, coding, wiki contribution,....) You don't have a right to say "This repo s*** big time"

Others who have spend a lot of time to answer a user who has below average IQ; please consider the fact that Gradio updated to 3.21 version on 14th March Pytorch updated to 2.0 version on 15th March

I can only say some people really hate the owner of this repo for previous or personal issues.

i guess the main take was about "why push all breaking things into the main repo and then leave this pile of garbage untouched for days or even weeks?"
there is normal scenario when all such things in other projects happens only in NIGHTLY builds or external dev repo.
majority of sdwebui users using google colabs and other free stuff where the script just downloading latest version of sdwebui

[JemiloII]

I hope you all know, this is github. You can always fork the repo and branch off. Put stable in the name and advertise developers to make changes to your repo.

A1111 sucks, but it has bleeding-edge features compared to the other libraries. A1111 also has too many duplicate extensions.

Personally, I never was a fan of Python, too easy to make chicken scratch code.

[alphaomegarandomname]

i still hate the new high res fix to no end. even in cope mode aka trying to make it work like the old mode, you have to use .60 noise or higher or nothing comes out right. i mean default value went from 60 to 75.. that should tell you something.

old high res was great at .40.. i guess its all semantics since .60 new is .40 old from what i can tell but still, why did it need messing with?

[playlogitech]

old high res was great at .40.. i guess its all semantics since .60 n

you can try comfy ui btw, they have simple workaround where you can control everything, including highres, even use different sampler for it if you like
and then use this picture in webui again

[Dddokter]

i still hate the new high res fix to no end. even in cope mode aka trying to make it work like the old mode, you have to use .60 noise or higher or nothing comes out right. i mean default value went from 60 to 75.. that should tell you something.

old high res was great at .40.. i guess its all semantics since .60 new is .40 old from what i can tell but still, why did it need messing with?

It seems that you have not had a closer look at what the new highres fix offers as you state that it cannot go below 0.6 denoise.
This is only the case if you stick with the default Latent upscaler as it requires at least 0.5-0.55 denoise to work properly or it will look like a pixelated mess.

There are multiple different esrgan type upscalers ready to be selected that can go all the way from 0 to 1, even though I would recommend going for a 0.2-0.3 for little changes while keeping the image similar while increasing the details.

edit: Not only esrgan also re-esrgan

[Sakura-Luna]

I think maybe Auto can create a new project like SD-nightly, and then give permissions to several people, so that users who like to update can switch to this project, and Auto can also choose which pr to accept to the current stable version at leisure .

[econundrum]

I've moved over to using this fork today.

https://github.com/vladmandic/automatic

More actively maintained and runs better as well, do read the readme though it does something differently and may not be for everyonem

[davehornik]

I've moved over to using this fork today.

https://github.com/vladmandic/automatic

More actively maintained and runs better as well, do read the readme though it does something differently and may not be for everyonem

I don't want to ruin your dreams, but the way he's doing that is so bad from dev and "aesthetically intelligent" perspective;
I could quote: ,,Not everything shiny is diamond."

And making a list of things what is bad and why so many guys are deleting that repo after few moments, but it's not worth my time.

[some9000]

Well, another possibility is that he's somewhere where the war in Ukraine may have an effect in some way. Either way, on this end everything works great.

It certainly would be better if there was a team of knowledgeable people that could bring different skills to the table. But at the same time what's currently there is great as is.

Also, the ability to add extensions is amazing and any version without that would be missing a lot.

[noisefloordev]

Grow up.

[Deckard9999]

Maybe a beta version could be a good idea. Heros download it, test it and then we have a stable version after 10(?) days, without break half of the (functioning) system. Dunno if can be a solution.
Btw I had no problem with update but the annoying check on ckpt that I disable immediatly, resolving the issue.

[Soulreaver90]

He's been doing a DEV branch for awhile now actually, I think he heard the complaints of bugs and took the suggestions to heart. He's been updating the DEV branch consistantly too.

[davehornik]

Yes, I am sorry for this. I feel guilty because as a developer, I KNOW how much free time and enthusiasm went into creating this.

But... do we really need to have hundreds of users every month who know nothing about the completely breaking changes? Do we need updates that f*k up everything every 2 weeks? Like, totally, so that users flood the forums and complain and cry about not being able to use it?

I understand. Gradio is a problem.

But how about testing changes BEFORE updating the main branch? Outlandish idea? How about putting some capable people in charge of this awesome repo? No? Okay. Lets have monthly update cycles of break and repair, because apparently this is normal behaviour, right?

Maybe in understaffed dev compartments. No communication. 2 weeks absent. Ok. Everyone has a busy life. 3 weeks absent, totally sh*tty updates. Everything breaks, no tests, everything sucks.

A1111 if you started to hate your project just give it to someone who wants to do it

I don't see a problem, I am watching the DEV branch and there are updates regularly. Maybe use your fu**ing eyes before un-reasonably criticizing work so harsh, that someone is doing for free.
But go for it, do it better urself then for free from your GH profile I can see you are VERY active, VERY experienced developer. wink wink. I BELIEVE YOU!
There are some guys trying, but they're putting so much trash "heavy opinions" in their version that it is literally unusable.

[Ainaemaet]

This is probably the silliest take I've ever heard about a software like this before.
I've been using Auto1111 since it first became available, keeping up to date and I've only had it break twice out of dozens of new pulls, and even at that it was always quickly fixed.

[f-rank]

Same here. Had to hold to some releases for a couple of times while things were getting sorted and that's it.
I don't know how these randos even wind up in here to be honest. It's like an eternal September moment of clueless chumps getting pissed at something they don't understand at all. Probably cheaper than therapy or just introspecting why they get to that poor state of mind about something free on the web that allows them to access something they actually like using.

[leizim182]

How sad to see this type of comment and charges. A project that works, for free, and that if there is any breakage, simply use a previous commit. "But no... I want everything my way, in my time, and even if I'm managing to do the renderings, I want an update to come out every week, without errors." Imagine who knows if there because the dev was missing, and when he comes back, trying to solve things little by little, he is faced with this... sad... (sorry for the poor english...it's not my default language)

[JasonKillsUs]

still there are thousends who preciate what the dev of automatic1111 is doing, and i´m one of them

[Ainaemaet]

Over the years (and from monitoring my own distortions) I found that when people begin a software critique with "As a developer, I....", they are most likely not really a developer, and are at best someone who's dabbled a bit but never actually put anything out of real value.

If they had and they knew what went into it and the process as well as they make it seem, I don't think they would be complaining so much (and would likely be offering to help instead).

@chopthesalami I think you're probably full of salami - if you can do better why not fork the repo and have a go yourself?

I update sdwebui almost daily and the only issue I've had in months was due to an extension that hadn't been updated properly.

Make sure you have your environment set up exactly as it needs to be, that can take a bit of tweaking if you're doing anything other than the automatic installs - I'm running in WSL2 and getting it to work properly took a bit, but it's been fairly smooth sailing ever since (aside from aforementioned extension issues).

[Magratheuis]

Harmless Comment I respect the work that goes into Auto 1111 but the new contrast thing is putting me off it. this however is my only issue.
I use realistic vision to do image to image pictures. need to blend in with real stock photos for my game project. in the past Auto 1111 brought stunning pictures. now it looks too dark. please tell me how to disable this or suggest to Auto to have a way to turn this off.
please look at this 2 pictures of a simeler room

grant you theirs not a huge difference. but I don't think the light is as realistic on the 2nd one. same modal and version on both but older and newer Auto 1111 versions. it's a shame. I like the rest of it.

some pictures are too sharp now. like this third one. i've turned off VAE and even try ed down scaling the alphas
this 2 show the same pic from both versions top old 2nd new


the light bounces better on the older. the newer looks more sharp and cartoon. I hope Auto might fix this. (PS Old version won't install)
I have autism and can't write sorry for spellings.

[espritdautomne]

A real serious developer would know that Gradio is NOT the problems in the first place; i use it myself for other applications than stable diffusion. A real developer would understand how things works together in the first place within the python environment overall. Python is not a plug and play environment but has the advantage to be open and debug-able by the users.

The problems with that type of application is there are plugins, scripts made by third party who could break you stable diffusion so it is advisable to make a backup of a working one ( i use 7z to backup my webui folder) before installing a new one. But here, i will share some tips, works from comfyui to automatic1111.

No need to do it all in this order, there are tips for specific problems and worth trying.

• Backup when it's working

• make sure to set these environment
  PY_LIBS = (portable webui folder)\python\Scripts\Lib; (portable webui folder)\python\Scripts\Lib\site-packages;
  PY_PIP = (portable webui folder)\python\Scripts
  IP_INSTALLER_LOCATION=(portable webui folder)\python\get-pip.py
  SKIP_VENV=1 (i dont use venv when it is possible)
  these can be a bit different on you side so try to locate these folder to make sure.

• pip can be often broken in many portable version of stable diffusion. Make sure those environment variables are correctly set then do this:
  python -m pip install --force-reinstall --upgrade pip

• download and decompress a portable version of git and set it to you path or many plugins will not work or update. This also prevent install manager to work properly in comfyui if git does not exist in path

• If a plugins or module broke you stable diffusion and you didn't make any backup, you can just delete it's folder from the folder webui\extensions or from nodes extensions in comfyui, restart and it should work.

• in webui-user.bat , add --skip-instal (yes, with one l only) to COMMANDLINE_ARGS. this will prevent errors while working completely offline or having later update that might broke something that work.

• if you use reactor, download GFPGANv1.4.pth ( https://huggingface.co/gmk123/GFPGAN/blob/main/GFPGANv1.4.pth ) , move it to \webui\models\GFPGAN folder then use GFPGAN instead of codeformer for better result.

• open cmd with admin right then do this:
  takeown /F "my drive:\my webui folder" /A /R /D Y

• On my side, running run.bat from clicking on it wont work properly so i need to open a cmd with admin right and run it with run.bat from webui folder instead and it work.