38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
# FLUX Notes
|
|
|
|
## Current useful collected workflows
|
|
|
|
- `models/flux/all-in-one-fluxdev-v0-2/`
|
|
- `models/flux/flow-upscaler/`
|
|
- `models/flux/flux-fill-inpainting/`
|
|
- `models/flux/flux-redux-reference-restyle/`
|
|
- `models/flux/flux-union-controlnet/`
|
|
|
|
## Current strongest roles
|
|
|
|
- `flow-upscaler`:
|
|
- strongest practical upscale-oriented FLUX workflow so far
|
|
- `flux-fill-inpainting`:
|
|
- cleanest dedicated edit/inpaint route
|
|
- `flux-redux-reference-restyle`:
|
|
- good reference-led variation / restyling baseline
|
|
- `flux-union-controlnet`:
|
|
- strongest structure-control baseline
|
|
- `all-in-one-fluxdev-v0-2`:
|
|
- useful as a source mine, not necessarily as a final master
|
|
|
|
## Current heuristics
|
|
|
|
- Prefer clean specialist graphs over giant all-in-one graphs when building optimized masters.
|
|
- Use big all-in-one graphs as idea mines for nodes/settings, not as the final default.
|
|
- Control, edit, and upscale workflows matter more than plain text-to-image for the current interest group.
|
|
|
|
## Best current optimization direction
|
|
|
|
- `optimized/upscale-restoration/` should likely borrow first from `flow-upscaler`
|
|
- `optimized/image-edit/` should likely compare:
|
|
- `flux-fill-inpainting`
|
|
- `flux-redux-reference-restyle`
|
|
- `flux-union-controlnet`
|
|
- `all-in-one-fluxdev-v0-2` is the place to steal useful sub-ideas if a cleaner graph needs a missing feature
|