The workflow is designed for a single image. I didn't test much it for batches more then one. Since v10.3 you can make multiple images in one job.
The features of that workflow (in the newest version):
Basic generation and editing (TXT2IMG, IMG2IMG, inpaint);
LORAs with control of automatic adding keyword into prompt (through LORA Manager);
Advanced generation (multiply TXT2IMG control-net , inpaint, outpaint, onlymasked inpaint);
Checkpoint loader lora with some additional features for Pony (scores presets, rating presets, negative presets and so on);
Saving metadata in Civitai's format;
Advanced prompting (styles selector, control on lora's keyword, negative/positive presets, morphing support, prompt formatting);
5 separated detailer groups with some pre-set settings, additional/combined prompt for each of them. You may add more detailer groups to connect them in the same way or delete it if necessary. I think it is pretty simple;
Almost fully switch-toggle control: if you use the workflow as is, you don't need any manual connection, muting, bypassing, activating.
(The previews of the adetailers are exceptions. They have global toggles, but sometimes it's more useful to activate or bypass some of them manually. I didn't find a better decision for it.Since v11, there are no toggles for it; the previews are inside adetailers groups.)Model upscale
Lama object remover
Not totally, but mostly nodes in the 'backend' (nodes under Lora Manager node) have tips on nodes and their links that give some help if you want to bring some modification;
Detailed (probably too detailed) a readme node with explanation of the logic of work and some advice.
Few bookmarks/shortcuts for fast navigation
Token counter for positive (+Lora's keyword + styles)
Florance-2 tag caption
The main goal of this workflow is to make the basic functionality of the WebUI and some extensions I use as functional as possible, mostly for Pony, as a residual matter — sd and sdxl. Some of these attempts have already failed.
Yolo/segmentation models:
https://huggingface.co/ashllay/YOLO_Models/tree/main
https://huggingface.co/Anzhc/Anzhcs_YOLOs
Additional prompting:
https://github.com/asagi4/comfyui-prompt-control
Credits:
The main concept is from this workflow https://civarchive.com/models/1507055/text-to-img-complete-workflow-multi-loras-adetailer-wildcards-and-more-comfyui by @Mittoshura.
Description
V14.6:
I replaced WAS Node Suite's nodes with my own. The WAS Node Suite is no longer needed for this workflow.
Changed the sampler and scheduler nodes for the metadata collector.
Required my extension v2.1.6 or newer.
V14.8:
Fixed additional details in the subgraph.
Changed the token count method.
Changed the order of prompt parts.
Changed the way latent previews are displayed.
«Disconnected» labels are not aesthetically pleasing, but at least it works.
Replaced boolean nodes on my own.
Required my extension v2.4.0 or newer.
FAQ
Comments (7)
i use 14.5 Cannot read properties of undefined (reading 'output') how can i fix it?
To launch ComfyUI with the argument --front-end-version Comfy-Org/[email protected] ( in theory more older should works too). It seems there are problems with newer frontends; it's about the status of muted subgraphs. An alternative solution is to unpack all subgraphs that have gotten a mute status and change the toggle system on group toggle. But this will turn the workflow into a huge peace of garbage.
No outer link found for slot [8] vae
in 16.1 how can i fix?
@DemonAlone No outer link found for slot [8] vae
how can I fix it now 16.1
@kg843 Is there any node or subgraph with a red border under the Lora manager node?
@DemonAlone No, all the missing nodes have been installed.
@kg843 This isn't about a missing node; rather, it's pretty rare — I had an issue with concatenating nodes, something very floating and exotic. I fixed it myself, but maybe there's a deeper reason. Perhaps the problem still lies in the front end (but I haven't encountered them on common stable and nightly versions). There is a subgraph called "prompt concat" under Lora loader. Unpack it and try if this helps you, or perhaps one of those nodes will show the issue.
