https://github.com/Haoming02/comfyui-floodgate
A Custom Node for ComfyUI that allows you to control the logic flow
https://github.com/Haoming02/comfyui-floodgate
comfyui custom-nodes stable-diffusion
Last synced: 4 months ago
JSON representation
A Custom Node for ComfyUI that allows you to control the logic flow
- Host: GitHub
- URL: https://github.com/Haoming02/comfyui-floodgate
- Owner: Haoming02
- License: mit
- Created: 2023-12-20T07:57:41.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-08-02T06:21:25.000Z (9 months ago)
- Last Synced: 2024-12-18T06:33:36.079Z (4 months ago)
- Topics: comfyui, custom-nodes, stable-diffusion
- Language: Python
- Homepage:
- Size: 916 KB
- Stars: 29
- Watchers: 3
- Forks: 6
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-comfyui - **Floodgate**
README
# ComfyUI Floodgate
This is an Extension for [ComfyUI](https://github.com/comfyanonymous/ComfyUI), which allows you to easily control the logic flow!
Motivation
While **Hires. Fix** *(or similar workflows)* can significantly improve the output, it also takes a longer time to process. Thus, many will simply run the base resolution until a good seed is found before enabling it. However, for `ComfyUI` this means connecting and disconnecting multiple nodes every single time...
Solution
Introducing, **Floodgate**!
Simply toggle between the logic flows. No more reconnecting multiple nodes!
How to Use
Connect the output of a node *(**eg.** `LATENT`)* to the `source` of the Floodgate node, then connect each path to the desired remaining workflow. Simply click on `gate_open` to toggle between the paths to take. The path not chosen will not be executed. Furthermore, since `ComfyUI` caches the intermediate results, opening the Floodgate will not require the precedent nodes to be processed again!
Features
1. Connect any arbitrary types
- *(input/output types still have to match)*
2. Multiple Floodgates in one workflow
3. Control each Floodgate individually
**Note:** The logic flow is parsed during the queuing stage, **not** the execution stage. As a result, the boolean value has to be already determined when you press `Queue Prompt`, such as from the toggle or a primitive node. If you use a node that outputs a boolean during execution, this will not work.