Can our entire field please realize that running this surveillance is a bad move, and just stop doing it.
If it isn’t explicitly surveillance, it could effectively be.
SDXL in particular isn't one of those "compute light, bandwidth bound" models like llama (or Fooocus's own mini prompt expansion llm that in fact runs on the CPU).
There is a repo focused on CPU-only SD 1.5.
The hundreds of python scripts and having the user to touch the terminal shows why something like Noiselith should exist for normal users rather than developers or programmers.
I would rather take a packaged solution that just works over a bunch of scripts requiring a terminal.
git clone https://github.com/lllyasviel/Fooocus.git
cd Fooocus
pip3 install -r requirements_versions.txt
python3 entry_with_update.py
> pip3: command not found
Okay. I'll need to install it? What package might that be in, hmm. Moving on, I already know it's python.
> /usr not writeable
Guess I'll use sudo...
= = =
Obviously I know better than to do this, but very few people would. This is not 'dead simple'! It's only simple for Python programmers who are already familiar with the ecosystem.
Now, fortunately the actual documentation does say to use venv. That's still not 'dead simple'; you still need to understand the commands involved. There's definitely space for a prepackaged binary.
This said, it's nice when developers attempt to detect the executable they need and warn what package is missing.
Additionally, some package choices depend on hardware.
In the end, a lot of the more popular projects have "one click" scripts for auto installs, and there are some for Fooocus specifically, but the issue there is its not as visible as the main repo, and not necessarily something the dev wants to endorse.
Look, DiffusionBee is still maintained but still no SDXL support.
Anyone who bet that the technology is done and it is time to focus on the UI is making the wrong bet.
It does look bad that it bundles GTM, though, as a sibling commenter says.
Samples:
No, its not.
There are two text encoders, but they aren't really “prompt” and “style” inputs.
> and most other UIs dont implement the style prompting.
Most UIs default mode of operation sends the same input to both text encoders, but at least comfy has nodes that support sending separate text to them. OTOH, while there may be some cases where sending different text to the two encoders helps in a predictable way, AFAIK most of the testing people has done has shown that optimal prompt adherence usually comes from sending the same to both.
thanks for any tipp guys :)
There are a bajillion local SD pipelines, but this one is, by far, the one with the highest quality output out-of-the-box, with short prompts. Its remarkable.
And thats because it integrates a bajillion SDXL augmentations that other UIs do not implement or enable by default. I've been using stable diffusion since 1.5 came out, and even having followed the space extensively, setting up an equivalent pipeline in ComfyUI (much less diffusers) would be a pain. Its like a "greatest hits and best defaults" for SDXL.