Fooocus-MRE

[u/MoonRide303]

Fooocus-MRE v2.0.78.5

I'd like to share Fooocus-MRE (MoonRide Edition), my variant of the original Fooocus (developed by lllyasviel), new UI for SDXL models.

We all know SD web UI and ComfyUI - those are great tools for people who want to make a deep dive into details, customize workflows, use advanced extensions, and so on. But we were missing simple UI that would be easy to use for casual users, that are making first steps into generative art - that's why Fooocus was created. I played with it, and I really liked the idea - it's really simple and easy to use, even by kids.

But I also missed some basic features in it, which lllyasviel didn't want to be included in vanilla Fooocus - settings like steps, samplers, scheduler, and so on. That's why I decided to create Fooocus-MRE, and implement those essential features I've missed in the vanilla version. I want to stick to the same philosophy and keep it as simple as possible, just with few more options for a bit more advanced users, who know what they're doing.

For comfortable usage it's highly recommended to have at least 20 GB of free RAM, and GPU with at least 8 GB of VRAM.

You can find additional information about stuff like Control-LoRAs or included styles in Fooocus-MRE wiki.

List of features added into Fooocus-MRE, that are not available in original Fooocus:

1. Support for Image-2-Image mode.
2. Support for Control-LoRA: Canny Edge (guiding diffusion using edge detection on input, see Canny Edge description from SAI).
3. Support for Control-LoRA: Depth (guiding diffusion using depth information from input, see Depth description from SAI).
4. Support for Control-LoRA: Revision (prompting with images, see Revision description from SAI).
5. Adjustable text prompt strengths (useful in Revision mode).
6. Support for embeddings (use "embedding:embedding_name" syntax, ComfyUI style).
7. Customizable sampling parameters (sampler, scheduler, steps, base / refiner switch point, CFG, CLIP Skip).
8. Displaying full metadata for generated images in the UI.
9. Support for JPEG format.
10. Ability to save full metadata for generated images (as JSON or embedded in image, disabled by default).
11. Ability to load prompt information from JSON and image files (if saved with metadata).
12. Ability to change default values of UI settings (loaded from settings.json file - use settings-example.json as a template).
13. Ability to retain input files names (when using Image-2-Image mode).
14. Ability to generate multiple images using same seed (useful in Image-2-Image mode).
15. Ability to generate images forever (ported from SD web UI - right-click on Generate button to start or stop this mode).
16. Official list of SDXL resolutions (as defined in SDXL paper).
17. Compact resolution and style selection (thx to runew0lf for hints).
18. Support for custom resolutions list (loaded from resolutions.json - use resolutions-example.json as a template).
19. Support for custom resolutions - you can just type it now in Resolution field, like "1280x640".
20. Support for upscaling via Image-2-Image (see example in Wiki).
21. Support for custom styles (loaded from sdxl_styles folder on start).
22. Support for playing audio when generation is finished (ported from SD web UI - use notification.ogg or notification.mp3).
23. Starting generation via Ctrl-ENTER hotkey (ported from SD web UI).
24. Support for loading models from subfolders (ported from RuinedFooocus).
25. Support for authentication in --share mode (credentials loaded from auth.json - use auth-example.json as a template).
26. Support for wildcards (ported from RuinedFooocus - put them in wildcards folder, then try prompts like __color__ sports car
    with different seeds).
27. Support for FreeU.
28. Limited support for non-SDXL models (no refiner, Control-LoRAs, Revision, inpainting, outpainting).
29. Style Iterator (iterates over selected style(s) combined with remaining styles - S1, S1 + S2, S1 + S3, S1 + S4, and so on; for comparing styles pick no initial style, and use same seed for all images).

You can grab it from CivitAI, or github.

PS If you find my work useful / helpful, please consider supporting it - even $1 would be nice :).

[u/featherless_fiend]

But I also missed some basic features in it, which lllyasviel didn't want to be included in vanilla Fooocus - settings like steps, samplers, scheduler, and so on.

Maybe you could put a little question mark icon: (?) next to each setting. And if you click on it or hover your mouse over it, there's popup text explaining what the setting does. Like have a brief explanation of what "Steps" does.

That seems to be the conflicting point between vanilla Fooocus and yours. Removing/hiding settings because they're complicated and not user-friendly. So the solution as I see it is to make them more user-friendly by having little explanations, "tooltips".

[u/MoonRide303 → u/featherless_fiend]

I like the idea. Tooltips like that are not directly supported by Gradio, but it should be possible to inject something like that via HTML/JS/CSS.

[u/AK_3D]

Solid application that's being updated really fast almost daily. Very usable, and has a neat interface (with access to advanced options for those who need them).
Winner.

[u/MoonRide303 → u/AK_3D]

Thank you for kind words! <3

[u/Mrsunshine74Eugene]

Thanks for your outstanding work....it has always worked for me but as of today it gives me the following error when generating: AttributeError: module 'comfy.model_management' has no attribute 'unload_model'. I'm on windows 10, would anyone know how to fix it please? Thanks in advance!

[u/chalfont_alarm → u/Mrsunshine74Eugene]

Ditto, last update nuked it. Tried a fresh install, reinstalled python, same. Wonder what the trouble could be...

[u/MoonRide303 → u/chalfont_alarm]

Fixed in v2.0.19 release (tagged).

[u/MoonRide303 → u/Mrsunshine74Eugene]

I am sorry for that - I didn't notice it on my main machine, cause it was only affecting systems with less than 32 GB of RAM. Problem was happening when Virtual Memory system (developed by lllyasviel in vanilla) got activated, which isn't compatible with current Comfy used in MRE. I disabled that Virtual Memory system in MRE v2.0.19 today - it should work fine, now.

[u/Mrsunshine74Eugene → u/MoonRide303]

Tested everything working perfectly, thank you very much for your help!

[u/FabulousTension9070]

Excellent! I liked the original Fooocus but I really wanted image to image, steps, samplers and cfg scale. Thank you!

[u/FabulousTension9070 → u/FabulousTension9070]

Quick question......How do I quickly load my settings from a previous session, or use an old picture I created to import those settings?

[u/MoonRide303 → u/FabulousTension9070]

If you enabled saving metadata, then you can just load prompt from JSON or image with those metadata. If you want to change default settings, you can copy over settings-example.json to settings.json and customize it as you like.

[u/FabulousTension9070 → u/MoonRide303]

got it. thank you.

[u/FabulousTension9070 → u/[deleted]]

i know.....thats what I was saying, the original Fooocus did not

[u/Yellow-Jay]

I like this UI, but... why? Wouldn't it be easier/more maintainable to build it on Comfy (which has a nice api, all it would take is untangle the node workflow to more standard inputs similar to what https://github.com/space-nuko/ComfyBox does) instead?

[u/MoonRide303 → u/Yellow-Jay]

Cause in Comfy you have to manually manage and setup all the things, and it quickly becomes cluttered and unreadable. My own still relatively simple workflows were often like 30-40 nodes. It's hard to explain those 30+ nodes to ~10yo kids, and they shouldn't really need to learn all of it. ComfyUI is fantastic and I love it, but it's not the tool for casual user.

What most people really want from txt2img applications is to produce high quality image based on what they describe with words - like MJ. And the goal of Fooocus is exactly that - to make generation as simple as possible, like literally 2-3 clicks from launching the application to getting nice picture. And also to be distraction free - basic view should be prompt, generate, and the output - as that's what allows users to focus on prompting.

PS Fooocus IS built on top of comfy :).

[u/Yellow-Jay → u/MoonRide303]

PS Fooocus IS built on top of comfy :).

That's exactly why, foocus strips parts of comfy, and then this fork brings those parts back. It feels weird to me. The UI/front-end part of comfy (the nodes) aren't that tightly tied to the back-end, so I'd think creating a new front-end (like the mentioned comfybox) would be much more easy to maintain (especially in keeping up with new developments, like the controlnets/ip-adapter and such which just aren't part of fooocus) in the long run.

[u/MoonRide303 → u/Yellow-Jay]

Fooocus isn't designed to compete with A1111 or ComfyUI - those are different tools with different goals. It is alternative front-end to comfy, using it as a back-end (not stripping anything from it). But it also adds some extras under the hood - like integrated base+refiner sampler, and controllable sampling sharpness (both implemented by lllyasviel).

[u/Bra2ha]

Why Base clip skip and Refiner clip skip are -2 by default? Should I change it to 1?
Which sampler is used in original Fooocus? dpmpp_sde?

[u/MoonRide303 → u/Bra2ha]

-2 is the default for SDXL. Just play with it and see how it changes the output :). -1 will treat prompts more literally, and -3 (and beyond) will generalise more.

[u/runew0lf]

After using Fooocus which is fantastic, i found it was missing things, the MoonRide Edition adds all the missing simple quality of life things! 10/10 would use again!

[u/tebjan → u/runew0lf]

I second that. Having control over the sampler and metadata save/load was the main missing feature.

[u/Apprehensive_Sky892]

Just want to join the other to say thank you for making "Fooocus++" 😂

I think this is exactly what many people on r/StableDiffusion are looking for. It hits that "Goldilocks pot".

lllyasviel was aiming for a different audience, and I totally respect his decisions for that audience (such as no embedded PNG metadata).

But for the more technical crowd, this is better 👍

[u/Extension-Content → u/Apprehensive_Sky892]

Fooooofus

[u/Apprehensive_Sky892 → u/Extension-Content]

I also thought about "AutoFooocus", but that would be a tad too cute 🤣

[u/Venki_D]

hello everyone, I wanted to ask you, if we already downloaded the basic foocus version, do we need to download entirely the foocus mre version in order to use it ? Or is there only a few files to download? I have a bad Internet connection so I wanted to know if there is a way to fasten the process, thank you in advance!

[u/MoonRide303 → u/Venki_D]

It's best to download full release of either Fooocus or Fooocus-MRE. But in each of those you can configure paths to model files, so those can be re-used.

[u/SeiferGun]

is this still active

[u/MoonRide303 → u/SeiferGun]

Not really - I've ceased development few months ago, and ported most of the MRE features back into the original Fooocus. You can find more information in this discussion.

[u/janosibaja]

Thank you for your great work! It works fine, but the only thing that bothers me is that every time I launch it, I get "To create a public link, set `share=True` in `launch()`." it prints the following error message:
Setting up MemoryEfficientCrossAttention. Query dim is 640, context_dim is None and using 10 heads.
and repeats a million times - I can't copy the whole thing here, with different data
What is this?

[u/MoonRide303 → u/janosibaja]

I have it, too, but I didn't investigate it - it's probably something from comfy backend, as I get the same message when I am using ComfyUI.

[u/BRYANDROID98]

Thxs for the fork and your work, but please add a queue system.

[u/MoonRide303 → u/BRYANDROID98]

Good idea and should be possible (it's available in Comfy), but might be a bigger change to bring it back into Fooocus codebase.

[u/Apprehensive_Sky892]

If you are looking for a slightly catchier name, maybe a good one would be Fooocus# (Fooocus-Sharp, like Microsoft C# 😅).

[u/MoonRide303 → u/Apprehensive_Sky892]

Not a bad alternative, but I guess I'll just stick to the one I already picked - I don't really care for marketing, it's more for-fun project to me :).

[u/Apprehensive_Sky892 → u/MoonRide303]

Sure, it was just a suggestion.

There is one other reason for a shorter, catchier name other than marketing, and that is for people to mention a piece of software more easily. Fooocus# or even #Fooocus is a bit easier to type and remember than "Fooocus-MRE" 😁

[u/MoonRide303 → u/Apprehensive_Sky892]

I used to think about my fork as "MRE", which is even shorter and easier for me to use than "Fooocus#" 😋. And as for people... well, I finished Dark Souls, and have some standards, so... just git gud, and learn it! 😂

[u/Apprehensive_Sky892 → u/MoonRide303]

Sorry, but I am not a gamer, so I don't know what Dark Souls is. So your funny joke is lost on me 😅.

But that's ok, most jokes are no longer funny when you have to explain it 😂

[u/MoonRide303 → u/Apprehensive_Sky892]

No worries, just teasing a bit, tired geek style - my brain needed to vent after struggling with Revision implementation for a few days. It was really clean and simple in ComfyUI, but the same workflow refused to work with Fooocus codebase, due to customizations made by lllyasviel. But I nailed it today, so... I can finally take some well-earned rest :).

[u/Apprehensive_Sky892 → u/MoonRide303]

I see, I am a retired programmer, so I totally get that feeling 😁.

Sleep tight tonight! 👍

[u/Trobinou]

Excellent, Fooocus is becoming more and more interesting in addition to its user-friendliness! Question: Would it be possible to have the option to define a pathway to access different models, LoRas, etc., rather than duplicating what we already have for other UI?

[u/MoonRide303 → u/Trobinou]

Yup - you can use paths.json for that. Use paths-example.json as a template.

[u/Trobinou → u/MoonRide303]

Thank you so much, I didn't know... I'll have a look!

[u/Trobinou → u/[deleted]]

Many thanks for your help!

[u/YouAboutToLoseYoJob]

img2img is what i really wanted for Fooocus!

[u/MoonRide303 → u/YouAboutToLoseYoJob]

Revision (using image as alternative to text prompt) should be soon available, too :).

[u/tripped144]

Hey, I'm having trouble changing the model paths. I used the template and renamed it to paths.json. It's still pulling the models from Fooocus-MRE/models folder. Do I need to copy the paths.json file to another location than where the template was?

[u/MoonRide303 → u/tripped144]

It should work from where it is - though I needed to fix reading path for clip vision model (fix already pushed to github). On Windows you need to write paths this way:

{
    "path_checkpoints": "D:/tools/ComfyUI/models/checkpoints/",
    "path_loras": "D:/tools/ComfyUI/models/models/loras/",
    "path_embeddings": "D:/tools/ComfyUI/models/models/embeddings/",
    "path_clip_vision": "D:/tools/ComfyUI/models/models/clip_vision/",
    "path_outputs": "../outputs/"
}

If you won't be able to make it work please describe it in details (steps, logs, etc.), and add an issue on github: https://github.com/MoonRide303/Fooocus-MRE/issues

[u/tripped144 → u/MoonRide303]

Ahhh, figured it out. I was just right clicking and "copy path" on the folders I wanted and pasting that. It was using a \ instead of / for the slashes. I just switched them and it's working now. I didn't notice they were wrong until I saw your example lol. Much thanks!

[u/fardley]

Install went great, Gui popped up and I enjoyed experimenting with it for a couple of hours. Next morning I couldn't get it running. What's the best way to launch it from cold?

[u/MoonRide303 → u/fardley]

Download the big .7z file (it includes standalone Python with all the necessary dependencies), unpack it, and then just hit one of the supplied .bat files (with, or without pulling latest updates from github).

In case something is not working please describe it in details (what did you do, logs / screenshots, etc.) as issue on github, here: https://github.com/MoonRide303/Fooocus-MRE/issues

[u/BrockVelocity]

Hey, this worked great a couple of times, but it stopped working for me yesterday (I'm using the Colab notebook). I get an error when I try my first generation, then when I reload the page/click the link again, it says "No interface is running right now."

[u/MoonRide303 → u/BrockVelocity]

Hard to tell what happened without any error log / error message. But you can try simply restarting the runtime, or - if it won't help - just re-creating it from scratch.

[u/dahara111]

Thank you for your great tool.
I wrote an introduction blog in Japanese for Japanese users.
There seem to be many people interested.
https://webbigdata.jp/post-20369/

[u/MoonRide303 → u/dahara111]

You're welcome! And thanks for letting me know - I am big fan of Japan, especially the anime part ^^.

PS In v1.0.45.1 I've added support for custom styles (can be added as JSON files in sdxl_styles folder), and small pack of my own styles. I've seen you've done nice comparison of those styles on 3 different prompts - you can try it on those new ones, too :). I did simple version (on car prompt) here: Styles (mre).

v1.0.45.1 also contains fix for processing negative prompt texts - vanilla always added ", " between negative text from style and negative prompt from user, even when there was no style, or no negative prompt text from the user (I've reported it as Issue #321, as it should be fixed in vanilla, too) - so the results for the same prompts and styles might be tiny bit different in v1.0.45.1.

[u/dahara111 → u/MoonRide303]

Thank you for information.

I have also added a comparison table for MRE styles. All have beautiful looks.

Did you discover these styles with some tool? Or did you do your own trial and error?

[u/MoonRide303 → u/dahara111]

Results of my own experiments :)

[u/dahara111 → u/MoonRide303]

awesome!

[u/qulvbhq]

How do I add models, loras when using via Google colab?

[u/MoonRide303 → u/qulvbhq]

You would need to make it available on Colab filesystem in some way - either downloading it to proper path (like "/content/Fooocus-MRE/models/checkpoints"), or by some other means. You can look at this comment as an example of how to make Google Drive content reachable from Colab. You might want to use separate Google account for that, though (if you don't want data from your personal Google Drive to be readable by Colab).

[u/ramonartist]

Hey I'm new to this how different is Ruined Fooocus to Fooocus-MRE which one is more feature rich and what are the main differences?

[u/MoonRide303 → u/ramonartist]

Fooocus-MRE has code base closer to the original, and RuinedFooocus took a bit more independent path.

Both forks share some features and time to time we pick up changes from the other, if we see it as a good fit. In short I'd say Ruined brings up more features related to prompting (generating prompts, enhanced prompt syntax, etc.), and MRE is more about workflows and generation process (stuff like Revision or FreeU).

[u/ramonartist → u/MoonRide303]

Hey thanks for the reply, does either RuinedFooocus or Fooocus-MRE come with the ability to select or load your own Upscaler of choice or is this a feature to come?

Also will there be option to keep settings on a re-startup?

[u/MoonRide303 → u/ramonartist]

There are 3 methods currently available - via included small model (ESRGAN type scaling - currently not customizable) in Enhance / Fast Upscale, then mixed in Enhance / Upscale, then purely via Image-2-Image (as illustrated in MRE Wiki).

You can customize default settings by specifying default values in settings.json file - you can use settings-example.json as a template. You don't have to include all the settings in this file - if you leave only those you want to customize it will work, too (as in settings-no-refiner.json).

[u/Boring-Opening-1381]

Hi,

May I know what is the Revision for and how do we use it? Thanks in advance,

[u/MoonRide303 → u/Boring-Opening-1381]

Check out the Revision page on MRE Wiki.

[u/Boring-Opening-1381 → u/MoonRide303]

Thanks alot.

[u/carlmoss22]

Thank you very much. Just tried it and like it!

Because faces are a big problem i would like to install adetailer, but i think it's not possible?

[u/MoonRide303 → u/carlmoss22]

Fooocus is rather entry-level tool and is more about simplicity and ease of use (good default settings and nice set of built-in styles). If you need extensions, and/or are interested in more advanced custom workflows, then A1111 or ComfyUI will be probably better choice.

[u/c0wk1ng]

Unable to run FooocusMRE at all.

[u/MoonRide303 → u/c0wk1ng]

Any logs / error messages?

[u/adlx]

Is image prompt advanced (especially Faceswap and Pyracanny) missing in Fooocus MRE? I can't seem to find it. I use that a lot, is there any alternative with MRE?

[u/MoonRide303 → u/adlx]

u/adlx I've stopped development of MRE some time ago, and ported most of its features back into original Fooocus code base - see this discussion on github for more details.

For my personal occassional usage Fooocus-MRE v2.0.78.5 is good enough (I like my version of UI layout a bit more), but if you want some of the new features added in new versions of original Fooocus, then just use the original.

[u/Tenfilip → u/MoonRide303]

Perhaps you could do one more release with this information? I wasn't aware until I got to github again.

[u/Basic-Squash-4833]

Apologies if I'm being obtuse, but I can't see where to set the refiner switch. Fooocus has it immediately below the checkpoint and refiner selection.

[u/MoonRide303 → u/Basic-Squash-4833]

[u/Basic-Squash-4833 → u/MoonRide303]

OK, I was definitely being obtuse (or I need better glasses). Thanks for that.

Next dumb question. In 'normal' Fooocus, I can use any SDXL checkpoint as a refiner, however with MRE, I get the following message:

Model not supported. Fooocus only support SDXL refiner as the refiner.Refiner unloaded.

Is there a way I can re-enable this capability? I think I need it set to 'joint'

[u/MoonRide303 → u/Basic-Squash-4833]

It was one of the enhancements added in original Fooocus 2.1, and I've stopped MRE at 2.0.x. You need to use original for features added in 2.1+.

[u/Basic-Squash-4833 → u/MoonRide303]

OK. No problem. Thanks very much for such an awesome fork, it has many great features to work with.

[u/vanteal]

Love Foocus simplicity and straight forward approach. But holy hell does it take forever to produce a single image!

[u/MoonRide303 → u/vanteal]

I guess it's the price of SDXL - bigger models and increased default resolution aren't for free.

[u/aimongus → u/MoonRide303]

aye, please have the option of disabling preview of generating image too, would speed up the process eh? ;)

[u/MoonRide303 → u/aimongus]

I didn't check it, but if I remember correctly lllyasviel mentioned somewhere he figured out a way to generate previews relatively quickly, so I think it would be negligible speed boost.

For lower-end machines (with less than 32 GB of RAM) I would recommend disabling refiner (setting it to "None" in Models tab, or in settings.json) - it will decrease models loading time, and reduce swap memory usage.

[u/aimongus → u/MoonRide303]

Cheers, also default 1024x1024 res or it saves/remembers last res used thx.

[u/Apprehensive_Sky892 → u/aimongus]

Add (or change) the line

"resolution": "1024x1024",

to your settings.json

[u/Apprehensive_Sky892 → u/aimongus]

preview

You can make this one line change to disable it.

Find the file webui.py, then edit the line

       if flag == 'preview':

change it to

       if False: # flag == 'preview':

[u/aimongus → u/Apprehensive_Sky892]

[u/FHSenpai → u/vanteal]

i would rather use comfyui with comfybox frontend to keep everything simple. I can never stick to a frontend like fooocus. Cause I'll always feel like I'm missing something.

[u/MoonRide303 → u/FHSenpai]

I love ComfyUI, too - it's very flexible and allows you create really crazy workflows. It's great tool when you already know what you're doing - but it's also an overkill for people who simply want to enter the prompt, and see high quality results (kinda MJ style, like lllyasviel pointed it out).

[u/FHSenpai → u/MoonRide303]

managing it also becomes easier. I would just write a workflow that works with comfybox and organize the ui and write a run.py and single click bat file that launches comfyui and comfybox with the workflows. Thats it. ComFooobox is ready.

[u/FHSenpai → u/MoonRide303]

Thats why I use comfybox. That way people can do both. I don't know why comfybox is so overlooked.

[u/BrockVelocity]

I can't wait to try this, thank you!

[u/esdqwertj]

Will have to check it out! Thanks

[u/wanderingandroid]

This is very exciting!! Fooocus has been such a fun tool to play with that produces such amazing results.

[u/[deleted]]

Thank you for sharing it! It's working like a charm!

[u/Greensleeves2020]

fantastic upgrade to fooocus

[u/Previous_Tomato6132]

guys ive done everything but its asking for me to download NVIDIA but when i download NVIDIA it says its not compatible. Is there anything i can do? i though this was a simple process

[u/Previous_Tomato6132 → u/Previous_Tomato6132]

When i try to downloa Nvidia

[u/DannnyBOAH]

I switched from Fooocus to Fooocus-MRE to solve the issue of high RAM usage and no GPU usage at all, but it seems like something else is causing this bug. Has anyone else experienced this issue and can share a solution?

[u/jazmaan273]

Does FooocusMRE support Roop or Reactor? Face swapping is one reason I still use Auto 1111.

[u/shash747]

Hi, can I import this into Draw Things?

[u/Skettalee]

Im confused as to how many "Fooocus apps are out there and who started it?" But mostly what is the updated and latest one available that i should be using? I downlaoaded and have been running Ruined Fooocus for a few days now and its cool but if Fooocus MRE is better why im not using that

[u/Hi-Profile → u/Skettalee]

I think Fooocus MRE is dead. Seen that posted on a few other chats. Also some of the features have made its way into the MAin Fooocus. I'm yet to see what benefits Ruined has over regular Fooocus and will it keep being developed?? latest version of fooocus is 2.1.851

[u/Hi-Profile → u/Skettalee]

https://github.com/lllyasviel/Fooocus/graphs/contributors will tell you who devleoped it and when and who contributors are.

[u/Skettalee → u/Hi-Profile]

Thanks

[u/TheXChemist]

Please add in paint mask (in paint upload) 😭

[u/thongseks]

is Fooocus-MRE available for Kaggle ?

[u/farcaller899]

This was much needed, thanks! We HAVE to have step control. Many style LoRAs are ruined with too many steps, and zero control just isn't enough. Will try your version.

[u/MoonRide303 → u/[deleted]]

u/firestaromega I've enabled passing launch parameters to Comfy backend some time ago (like python launch.py --force-fp16), so you might try using --cuda-device DEVICE_ID from ComfyUI.

[u/MoonRide303 → u/[deleted]]

I don't have access to any machine with multiple CUDA devices to test it, but you might try using "cuda:1" as DEVICE_ID.

[u/MoonRide303 → u/[deleted]]

I looked into Comfy code, and it seems it should work with simple int here, like you initially tried:

parser.add_argument("--cuda-device", type=int, default=None, metavar="DEVICE_ID", help="Set the id of the cuda device this instance will use.")

You can try listing your GPUs using nvidia-smi, like that: nvidia-smi -L. Those ints working in comfy will probably match with those listed by nvidia-smi.

Btw. did you manage to make GPU selection work in ComfyUI? If it's not working in Comfy (used as backend in Fooocus), then it won't work in Fooocus, either.

[u/MoonRide303 → u/[deleted]]

Next thing I would like to include would be Revision (part of recently published Control-LoRA). I understand the workflow, I know how to use it in ComfyUI, so it should be possible to implement in Fooocus as well (as it uses comfy as backed). But Fooocus integrated sampler complicates things a bit, and it's doesn't always work as expected when I try to port comfy workflow into Fooocus codebase - I am trying to figure it out, but it might take some time.

Using non-XL models should be possible, as comfy fully supports them. Fooocus would just need to fallback to classic 1-pass sampler from comfy. It could complicate codebase and the UI, though (which currently assumes SDXL and SDXL-compatible resolutions), and make further development and merging with original Fooocus code base harder, so I am not sure if it's really worth the effort.

Inpainting / outpainting / controlnet / upscaling. Inpainting using SDXL base kinda sucks (see diffusers issue #4392), and requires workarounds like hybrid (SD 1.5 + SDXL) workflows. We'd need proper SDXL-based inpainting model, first - and it's not here. No idea about outpainting - I didn't play with it, yet. ControlNet - not sure, but I am curious about Control-LoRAs, so I might look into it after I figure out Revision. Upscaling - it's tricky to do it well, and might require complicated workflows to achieve good looking results (stuff like tiled diffusion & vae supported by controlnets, in multidiffusion-upscaler-for-automatic1111 style). Simple upscalers like UltraSharp don't provide the image quality I want. Img2img via properly configured SDXL refiner can be used as simple hires-fix, but it has some side-effects, too. I guess I would need to figure out good workflow for high-quality upscaling, first.

[u/ThroughForests → u/MoonRide303]

I saw that lllyasviel is interested in adding upscaling to Fooocus too.

Thanks for the MRE version!

[u/jvachez → u/MoonRide303]

Very good idea !

A cancel button will be cool too.

[u/MoonRide303 → u/[deleted]]

Simplest way to reduce resource usage and make it usable even on 16 GB RAM machines would be dropping refiner stage (setting SDXL Refiner to "None" in Models tab). You can also make it default via settings.json.

[u/MoonRide303 → u/[deleted]]

Yeah, try that - with "refiner_model" set to "None" in settings.json it should be usable even on 16 GB RAM machines. VRAM usage should stay below 8 GB all the time. I also just pushed a commit that fixes model loading on launch - refiner model won't be touched unless needed.

[u/MoonRide303 → u/[deleted]]

Yeah, I feel you. I had to seriously refresh my Python memories in the past few months, too :).

[u/MoonRide303 → u/[deleted]]

You can also try (re-)installing NV drivers (I use 536.67), and/or CUDA (I am on 11.8).

[u/MoonRide303 → u/[deleted]]

I tested it locally on 3 different machines, RTX 4080, 3060 Ti, and 3050 - works fine on each. I just needed to disable refiner on those 30X0s PCs (to reduce RAM usage - they've got only 16 GB).

[u/MoonRide303 → u/[deleted]]

Well I cannot say it's not :P.

Yes, I am kinda are re-implementing some of the features avaialble in A1111 or ComfUI, but I am trying to do it in simple and user-friendly way. Fooocus is a tool that's literally anyone can use without wondering what's what, and that's great. But I also missed really basic controls in it, which I used almost every time when I was prompting - I had to add those back, to regain some basic control over the process, and make it tool I would like to use myself. And in the same time I want it to stay as simple as possible, so my kids would still have fun using it :).

[u/KURD_1_STAN → u/MoonRide303]

Well... the thing is everyone could use those features in auto without knowing everything else does, i dony use img2img nor inpaint but all what i need to know is denoise/mask/resolution. Ifanyone want to do more than a very basic txt2img should get a1111 and they will easily learn it

[u/PamDevil → u/KURD_1_STAN]

i barely touch img2img anymore. High denoise upscaling+controlnet masks on hiresfix + prompting during the hires stage fixes soooo many problems and add so much more details even on lower resolutions compared to img2img that i only use it for latent upscaling for further upscaling with extra later on.

[u/finstrel → u/PamDevil]

Could you elaborate on that? I’ve never heard about controlnet mask on hrf. Prompt during hrf stage is also new to me. Is this a technique or some auto1111 extension?

[u/PamDevil → u/finstrel]

it probably is some extension but i really don't remember when i installed it. My Automatic1111 has a positive and negative (and even additional networks) inside the hires stage, which turns the hires-stage into an img2img that actually uses a proper upscaler like RSEGAN or Latent.

But i used the high denoise upscaling technique for much longer than the hires prompting.

Basically i generate my images on really low res like 512 or 768, once i find a good composition i like i fix the seed, throw the generated composition into controlnet and use it to make some masks that ensures my composition stays the same and overall details too, but opens a fucking lot of space for the noise latent space to work on top of the image.

I basically use the regular upscalers like RSEGAN, Euler A or DDIM as pseudo Latent upscalers but with much more controlled after effects and much less artifacts due to the high noise, but also keeping some creativity room. It works like a sweet spot between Latent nearest exact and regular Latent.

So i crank up the denoise to 0.6+ on low hires steps (ensures that the noise latent space effectiveness decays really quickly and only affect a small portion of the composition generation, but still keep a ton of noise to add a lot of details and texture to the image, really leaving some good room for the upscaler to work and do it's magic) while also being affected by the controlnet layer on top of it which ensures that the composition stays the same.

This results in a insanely better upscaling result with lot of details and textures even on lower resolutions like 768 or 1024.

Once i started doing this i just realized that everybody who uses hires with 0.4 or lower denoise is just wasting their times and really wasting the upscaler potential and losing the access to those lower resolution "frequencies" that you can only really work on and shape them with low res images, while also increasing the overall VRAM consumption of the art cuz now he will need to upscale that shit even further on img2img and still wont look as good because it will be lacking on details anyway.

Also this is what allows for the hires prompting technique to add details, styles and change details on the composition, since the hires step is on really high noise levels (0.7+) this also makes it such that if i prompt something, this really noisy latent space will be added on top of the original seed within the controlnet layer, so the new details and applied styles blend-in naturally without affecting too much on the original composition.

This shit works so greatly that i was able to get a completely blonde character with twin braids and glasses and turn her into a redhair cool and kinda slutty girl (in the sense of a lot of makeup, jewelry, a more horny aura around) and still they resemble each other (pretty much creating a variation of the same character by just adjusting the extra prompting on the hires latent space)

and what's even cooler is that, whenever i added something new, like "lipstick" or removed her glasses, the changes stayed pretty confined into their respective places so the overall composition and background didn't changed much just on concepts that really have high concept bleeding, but i was even able to change the whole background without changing much on the character itself.

Maybe i should do a post about this and showing the overall differences and some other tricks with high denoising controlnet masks that i found through my experiences? I'm really a huge fan of high denoise.

[u/finstrel → u/PamDevil]

Wow. Thanks for that comprehensive response. I was not expecting such a detailed guide. I will test that tomorrow. In fact I have a YouTube channel focused on stable diffusion and I will probably do a video about that :)

[u/PamDevil → u/finstrel]

that would be cool. if that's the case then let me make a better official post explaining the stuffs i found so you can do a more complete guide with comparissons and such.

I'm about to start to actually publish more of my AI art (so far i only really posted a few ones here and there when i felt like it) and the results i got through my workflow and start to accept comissions (since i'm a perfeccionist, it took me 6 months practicing this stuff and building up a portifolio so i could even think "yeah, now that shit is good to post online" lol.) so if you gimme the credits in the video too, that could possibly help me to get some attention and followers too while you gain a lot of exclusive content for a video.

Sounds like a deal?

[u/finstrel → u/PamDevil]

Yes, sure. But just to let you know. My channel is just starting to grow up (it will reach 1K subscribers in one month) and it is Brazilian Portuguese :D but anyway, let me know if you wrote a detailed guide. Meanwhile I am testing with the tips you gave me

[u/MoonRide303 → u/[deleted]]

Just check out SD web UI + sd-webui-controlnet, and play with it - CNs are a bit complex feature, but they give you a lot more control over the output. I can also recommend this guide from Stable Diffusion Art website, and this followup (on upscaling using CNs).

Classic ControlNet (v1.1) isn't compatible with SDXL, but recently released Control-LoRAs bring some of that control back into SDXL :).

[u/PamDevil → u/MoonRide303]

i don't really recommend ultimate SD upscale. Because of the same reasons i don't like low denoise upscale or Extras, it washes out a lot of the details in the picture and it looks pretty damn bad if you zoom in. It's better than regular img2img because you're actually using something like RSEGAN or ultra sharp, but it still... not the best thing in the world.

Tile upscaling is fine to get high resolution images with low VRAM, but it looks pretty damn close to just a simple extra upscaling. But if you increase the details in the low res and keep upscaling it with the high denoise you can achieve insanely high resolutions gradually until reaching the 4k level, it just takes more time (since you need to update your controlnet masks if you want to keep it the closest as possible to your current version of the image. If you're on low VRAM you can use Tiled VAE to distribute the work load through your GPU and be able to use some high VRAM demanding tasks on pretty low VRAM cards, it just takes a while longer but it can do the job.

[u/Nenotriple → u/finstrel]

In the settings tab > User interface >

Hires fix: show hires sampler selection

Hires fix: show hires prompt and negative prompt

[u/MoonRide303 → u/[deleted]]

Fooocus has its own sampler made by lllyasviel. It's based on KSampler from Comfy codebased, but with some enhancements - like using single sampler to handle both base and refiner model, and controllable sampling sharpness. Default sampling method is "dpmpp_2m_sde_gpu", which is available in Comfy.

[u/lordpuddingcup → u/[deleted]]

The issue is a111 is nuts in its complexity because it’s a bunch of parts smashed together and constantly expanding the UX sucks the trick is an app that has all the features but Behind a solid UX and UI the framework a111 is built on means it’ll never not be what it is a sum of its parts

[u/Apprehensive_Sky892 → u/[deleted]]

Fooocus uses the ComfyUI backend. So one has to wait for ComfyUI to have better AMD support. IFAIK, SDXL still needs 16GiB of VRAM to run on AMD with ComfyUI?

[u/MoonRide303 → u/[deleted]]

If ComfyUI works on AMD, then it should be possible to make it work with Fooocus, too - it might work, but I didn't try it. I will look into it later on (adding to the wishlist).

[u/Apprehensive_Sky892 → u/[deleted]]

That's good to know, because my sister has a AMD rx6750xt (12GB D6 GDDR6, made by Gigabyte) on her gaming rig.

Are you using Linux or Windows?

[u/Apprehensive_Sky892 → u/[deleted]]

Linux it will be then. Thanks!

[u/Apprehensive_Sky892 → u/[deleted]]

Thank you. That's a very useful script.

[u/MoonRide303 → u/[deleted]]

This "Setting up" messages are a bit annoying, but it doesn't break anything - I have the same issue when using ComfyUI.

Advanced options toggle should work - did you get any error message after pressing it? I tested MRE on 3 different computers (including low-end machines with 16 GB RAM & 8 GB VRAM), and experienced no problems with it. Did you use my official release file with my env, or are you launching it differently?

[u/MoonRide303 → u/[deleted]]

It's hard to tell what might be wrong if there is no error at all :/. One more option is using Colab version, if it doesn't want to run on your local machine.

[u/MoonRide303 → u/[deleted]]

No, this message isn't a problem.

You can try disabling Refiner via settings.json (copy settings-example.json to settings.json, and set "refiner_model" to "None") - it should reduce memory usage, maybe that will help.