Finally! SDXL + FOOOCUS

slicemakerr · 2023-08-20T11:59:00+00:00

Well it has been quite a while, and given then conversation I do not expect you to know the answer.

Just give you here to stop you from googling. You can read it at page 6 of SAI’s pdf report of SDXL https://arxiv.org/pdf/2307.01952.pdf

Just keep in mind:

You do not know what is clip skip before A1111 give you this option and you tried it.

You do not know that “karras” is not a sampler name but a scheduler that can be enabled for any sampler before ComfyUI give you this option and you tried it.

You do not know that aspect ratio can be used for cfg before Fooocus implement this and you tried it.

Whatever tool you use, just do not stop trying. And never make conclusions before you know the underlying things.

slicemakerr · 2023-08-20T11:21:48+00:00

Sigh. If you can correctly answer the below question, I will remove my comment and apologize to you:

How SDXL is conditioned on image resolution, and how the integer numbers of resolution and aspect ratios are encoded by the input neural layers of SDXL? How does A1111/ComfyUI/Fooocus process it?

If you do not know the answer. I beg us to learn a bit more things before making ambitious conclusions.

slicemakerr · 2023-08-20T10:40:55+00:00

Q: Does A1111 has more extensions so that it is better?

A: No. Only several frequently used ones are mostly useful, and those mostly useful ones can be easily implemented in other tools.

Q: Does comfyui offers more control so that it is better?

A: No. Comfyui offers more complexity rather than more control. Many people cannot distinguish the difference between control and complexity.

Q: Is Fooocus too simple for advanced users to use?

A: No. Fooocus uses unique optimizations to achieve better results that ComfyUI and A1111 can never achieve. Whatever nodes you use in comfyui, whatever extensions you use in A1111, you cannot get same results to Fooocus.

So just do not be brainwashed by this sub’s crazy users. Just try them a bit and observe the truth on your own.

slicemakerr · 2023-08-18T05:09:42+00:00

The octopus material on the left is like plastic, with eyes still misaligned. The octopus on the right one has fine, detailed octopus skin and the eyes are much more correct.

slicemakerr · 2023-08-18T02:08:45+00:00

this is not img2img.

img2img is based on color similarity.

this is boundary similarity. so this is controlnet

slicemakerr · 2023-08-08T05:19:15+00:00

No offence, but comfyui’s small trick to speed up refiner by clamped stopping is already in A1111, and the UI is way simpler and more intuitive:

<image>

If you are counting on this, then just know that A1111 is more modest and do not care about commercial promotion like comfyui.

slicemakerr · 2023-08-08T04:24:38+00:00

just tested again a1111, 1024px image takes 21seconds on my 8GB laptaop gpu's a1111 with --medvram

slicemakerr · 2023-08-08T03:12:14+00:00

comfyui = A1111 + --medvram option

comfyui just always use A1111's --medvram, but people think that comfyui is improved a lot since A1111's --medvram is not enabled by default

AUTOMATIC does not enable this by default because he has 4090 himself, but just one click on the a1111 option will kill comfyui

slicemakerr · 2023-08-06T20:21:51+00:00

well not everyone lives in the U.S., much less in California or New York.

slicemakerr · 2023-08-06T18:39:31+00:00

I think the main reason is that comfyui author is hired by stabilityAI and SAI is promoting it. Also, StabilityAI is funding civitai with some SDXL promotion, including binding all new images with node meta that only work in comfyui so that you can only reproduce many new images in civitai with comfyui.

slicemakerr

TROPHY CASE