Sign In

👑 FRED_simple_FLUX__with_lora_v1 ⚙️

29
340
5
Updated: Jan 7, 2025
tool
Type
Workflows
Stats
201
Reviews
Published
Jan 7, 2025
Base Model
Flux.1 D
Hash
AutoV2
48EE5B3043
The FLUX.1 [dev] Model is licensed by Black Forest Labs. Inc. under the FLUX.1 [dev] Non-Commercial License. Copyright Black Forest Labs. Inc.
IN NO EVENT SHALL BLACK FOREST LABS, INC. BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH USE OF THIS MODEL.

👍 *** Like this workflow if it helped you generate amazing results! ***👍

👑 COMFYUI WORKFLOW, Simple flux generation for my loras ⚙️

NEW REVISION V1.0s, Simplified workflow without ezXY nodes.

***Notes***

In order for this to work with ComfyUI_ezXY repro from github, a file should be modified and comfyui restarted after.

Modify the file config.yaml for line 4 and 7. Where you see "True", put "False"

I'll create a new version of the workflow to remove nodes from that repro when I come back home. Some also wanted me to remove the top 2 groups that is used to save the image with the lora name on the image in a different folder, if you disagree with that removal, please post a comment.

***********************

After some request, asking me how I can generate those quality image from lora:
Here is the answer, a simplified workflow to generate image using flux.1 Dev model along with my loras.

You can use it as is, by only modifying what are in the red box.

1- The lora to use (some of the prompt are already set for a person, adjust if it's not your case)

2- The prompt context to add, as the background, cloth and such

To refine the result, you can play around with blue box.

De default setting should be good for most of you.

If you get a out of memory, or an, allocation on device, error, change the 1.4 latent upscale to 1.25 or bypass that node. But if you're computer can handle it, you'll see, it worth it.

When you're happy with the result you can upscale. To do so, simply activate the last group.

That group also divide the image by tile to show you how the UltimateSDupscale node will process the image. The best is to have the face entirely in 1 tile, but other tile should all get the context of the person it upscale or you'll get strange thing happening. For a upper body shot, a 2 rows with 3 cols work great. If you get strange result, put that at 2 cols.

The Controlnet Tile group is there only if you're result giving too much deformation. If you activate it, you can rise the desnoise of the ultimateSDupscale to around 0.5.

But those 2 groups are optional as, you'll see, the first result is already amazing.

The Workflow also save results at a specific places:

1- The normal result will got in (every day will be a new folder, so you will not end with a very high quantity image inside 1 folder resulting in an very low latency access to that folder): ...output/FLUX/Normal/YYYY-MM-DD

2- It will also output in an other folder if the 2 groups on top are on: ...output/FLUX/lora_test/YYYY-MM-DD

3- And if you want, if the group for ultimateSDupscale is on, in: ...output/FLUX/UltimateSDflux/YYYY-MM-DD