Sign In

Advanced Flux workflow for the insane\bored.

4
Advanced Flux workflow for the insane\bored.

Before I get to the insane stuff let me get a couple of sections out of the way. I use Florence sometimes to help in creating my prompts, so it is included but not connected to the workflow. The group is set to disabled. The Flux IPAdapter and and Flux ControlNet groups can also be set to "Never" when they are not needed.

I also start with the refine group turn off until I have something that I like and looks pretty good in the render section.

I have three checkpoint model loaders in the workflow, just in case I want to try something NF4 or GGUF but I mostly use the diffusion loader and a Lora loader. I use GGUF for the CLIP models in order to save memory (I typically use a Q5 quantization).

Here are the two advanced/insane areas to play with. On the left side is the CLIPAttentionMultiply node and some notes on settings I found that have worked. On the right side is the CustomSchduler node. There is a note in the work flow with three example custom schedules.

I have left a disabled basic scheduler in the workflow for when I want to compare results with a known schedule. I use a debug node to print out known schedules, but it is difficult to find a debug node that works at all and it can cause the workflow to fail to load. Let me know if you have a debug node that works well for you.

I am sure there are plenty of getting started guides out there that will cover base shift and cfg, I just wanted to share some other parameter you could be playing with if, like me, you are too curious for your own good.

4

Comments