Update README.md

This commit is contained in:
KLL535
2025-01-22 20:10:46 +03:00
committed by GitHub
parent 4373c1deae
commit e47cd69e5e
+3 -3
View File
@@ -3,7 +3,7 @@
### Why is this needed:
I needed to automate the process of generating images and could not find any straightforward ready-made solutions for this purpose. Hence, I developed my own solution. The primary idea is to replicate and expand `Forge's` functionality: specifically, the `Prompts from file or textbox` script. This will allow you to easily combine pre-prepared lists of prompts, LoRA, styles, allowing you to combine texts as you wish.
The resulting images prompt in metadata must be compatible with `Forge`, ideally appearing no different than those generated by it. However, I encountered a problem because `Forge` uses the internal name from the LoRA file metadata as the LoRA's name instead of the filename. Consequently, all existing solutions failed to comprehend my templates.
I also wish for the ability to write LoRA in any order and quantity within a text file using this format: `lora:name:1.0` or `lora:name:unet=1.0:te=0.75`. This should be automatically applied without the need to create separate nodes for each LoRA. Additionally, I would like it if the `CivitAI` platform could understand metadata. As the closest solution I found was the `alexopus/ComfyUI-Image-Saver` project. However, this alternative loses LORA written in `Forge` style by using the internal name instead of the filename.
I also wish for the ability to write LoRA in any order and quantity within a text file using this format: `<lora:name:1.0>` or `<lora:name:unet=1.0:te=0.75>`. This should be automatically applied without the need to create separate nodes for each LoRA. Additionally, I would like it if the `CivitAI` platform could understand metadata. As the closest solution I found was the `alexopus/ComfyUI-Image-Saver` project. However, this alternative loses LORA written in `Forge` style by using the internal name instead of the filename.
![workflow](https://github.com/user-attachments/assets/9014a2a0-c507-4872-b5eb-9a29b3b87518)
[!] You need to remove the first node with empty text, so that it does not block the execution of the chain, since the text in it does not change.
@@ -91,8 +91,8 @@ If not connected these lines will be missing:
- `height` - *INT*.
- `beta_schedule_alph` - *FLOAT*.
- `beta_schedule_beta` - *FLOAT*.
- `civitai_lora` - *STRING* - Loras name from Simple Lora Loader node.
- `civitai_lora_hash` - *STRING* - Loras hash from Simple Lora Loader node.
- `civitai_lora` - *STRING* - Loras name from `Simple Lora Loader` node.
- `civitai_lora_hash` - *STRING* - Loras hash from `Simple Lora Loader` node.
- `negative` - *STRING*.
#### Output:
- `metadata_text` - *STRING* - Metadata written to file.