Skip to content

Latest commit

 

History

History
322 lines (278 loc) · 16 KB

README.md

File metadata and controls

322 lines (278 loc) · 16 KB
icon

SD Prompt Reader Node

GitHub GitHub tag (with filter) GitHub tag (with filter) Code style: black

This is a subproject of the SD Prompt Reader. It helps you extract metadata from images in any format supported by the SD Prompt Reader and saves the images with additional metadata to ensure compatibility with metadata detection on websites such as Civitai.

Supported FormatsInstallationUsageChange LogCredits

Supported Formats

PNG JPEG WEBP TXT*
A1111's webUI
Easy Diffusion
StableSwarmUI*
StableSwarmUI (prior to 0.5.8-alpha)*
Fooocus-MRE*
NovelAI (stealth pnginfo)
NovelAI (legacy)
InvokeAI
InvokeAI (prior to 2.3.5-post.2)
InvokeAI (prior to 1.15)
ComfyUI*
Draw Things
Naifu(4chan)

See SD Prompt Reader for details

Installation

Note

While ZIP package is available, it is strongly recommended not to use it for installation.

Install and update via ComfyUI Manager (Recommended)

Search for SD Prompt Reader in the ComfyUI Manager and install it.

Install manually

Please make sure to install the submodules along with the main repository.

  1. cd to the custom_node folder
  2. Clone this repo
    git clone --recursive https://github.com/receyuki/comfyui-prompt-reader-node.git
  3. Install dependencies
    cd comfyui-prompt-reader-node
    pip install -r requirements.txt

Update

When updating, don't forget to include the submodules along with the main repository.

git pull --recurse-submodules

Usage

Prompt Reader Node

reader node

Important

Due to custom nodes and complex workflows potentially causing issues with SD Prompt Reader's ability to read image metadata correctly, it is recommended to embed the Prompt Saver Node within the workflow to ensure maximum compatibility.

More Information

parameter_index

  • For images containing multiple sets of parameters, such as those processed through hires-fix or refiner, you will need to modify the parameter_index to select the parameters you need

SDXL

  • For images generated by SDXL and containing multiple sets of prompts, the text_g will be combined with text_l into a single prompt

Batch Read

  • For batch processing, please use the Batch Loader node. When using the Batch Loader node for bulk reading, the preview image will not update, and the text box will only display the metadata of the last image.
connect batch loader to prompt reader

Additional Parameters

  • To read parameters other than the existing output, please connect the settings to the Parameter Extractor node.
connect prompt reader to parameter extractor

MODEL_NAME

  • MODEL_NAME is a special output that matches the model name in the metadata with the existing models on the server according to the following priority:
    1. Identical path, filename, and extension.
    2. Identical filename, and extension. e.g. sd_xl_base.safetensors will be matched with SDXL\sd_xl_base.safetensors, and vice versa.
    3. Identical filename. e.g. sd_xl_base will be matched with SDXL\sd_xl_base.safetensors, and vice versa.
    4. If a matching model cannot be found, the original name will be outputted.

Prompt Saver Node

saver node
  • The Prompt Saver Node and the Parameter Generator Node are designed to be used together.
  • The Prompt Saver Node will write additional metadata in the A1111 format to the output images to be compatible with any tools that support the A1111 format, including SD Prompt Reader and Civitai.
  • Due to custom nodes and complex workflows potentially causing issues with SD Prompt Reader's ability to read image metadata correctly, it's recommended to embed this node within the workflow to ensure maximum compatibility.

Tip

Since it's not possible to directly extract metadata from KSampler, it's necessary to use the Parameter Generator Node to generate parameters and simultaneously output them to the Prompt Saver Node and KSampler Node.

More Information

Image Format

  • Only PNG format supports embedding both metadata and workflow at the same time. Other formats can only embed metadata.

Duplicate Filename

  • When the filename already exists, an index will be added at the end of the filename, e.g. file.png, file_1.png, file_2.png.

Hashes & Auto-Detection on Civitai

  • When calculate_hash is enabled, the node will compute the hash values of checkpoint, VAE, Lora, and embedding/Textual Inversion, and write them into the metadata. After the server restarts, or a new checkpoint, VAE, Lora, or embedding/Textual Inversion is loaded, the first image generation may take a longer time for hash calculation. The hash value will be stored in temporary storage without the need for repeated calculation, until the server is restarted.
  • When resource_hash is enabled, the resource hashes will be written into the metadata to support auto-detection on Civitai. This function will only run when calculate_hash is enabled.
  • If you need to calculate the hash of Lora, please use the Lora Loader Node or the Lora Selector Node. The hash value of the embedding/Textual Inversion will be automatically detected from the prompt.

save_metadata_file

  • When the save_metadata_file is turned on, the metadata will be saved as a TXT file with the same name alongside the image.

date_format & time_format

filename & path

  • %counter cannot be used for path, it can only be used for filename. This %counter is slightly different from the %counter in the built-in Saver node, it will count all image files in the path.

  • Please refer to the following table for placeholders supported by the filename and path.

    %seed %date
    %steps %time
    %cfg %counter
    %model %extension
    %sampler %quality
    %scheduler

Parameter Generator Node

generator node
  • Since it's not possible to directly extract metadata from KSampler, it's necessary to use the Parameter Generator Node to generate parameters and simultaneously output them to both the Prompt Saver Node and KSampler Node.

Tip

The Parameter Generator Node can also be used as a control panel for complex ComfyUI workflows, just like the AP workflow.

More Information

Optimal Resolution

refiner_start

  • refiner_start refers to the proportion of steps completed when the refiner starts running, i.e., the proportion of base steps to total steps. This is used to calculate the start_at_step (REFINER_START_STEP) required by the refiner KSampler under the selected step ratio.

Batch Loader Node

loader node
  • The Batch Loader Node is specifically designed for the Prompt Reader Node to batch-read image files in a directory and cannot be used with other custom nodes.
More Information
  • For batch processing, please connect the IMAGE output of the Batch Loader Node to the image input of the Prompt Reader Node.
connect prompt reader to parameter extractor

path

  • The path supports relative paths such as ./input/ or absolute paths like C:/Users/receyuki/Pictures.
  • Both \ and / are acceptable.
  • You can also input a single file or a list of files into the path, in which case the image_load_limit and start_index will not function.

Parameter Extractor Node

extractor node
  • The Parameter Extractor Node is an extension of the Prompt Reader Node, designed to retrieve the values of all parameters in the settings (including those parameters that the Prompt Reader Node cannot output). e.g. Hires upscaler
More Information
  • Connect the SETTINGS of the Prompt Reader Node to the settings of the Parameter Extractor Node. After the first run, the parameter list will be loaded.
connect prompt reader to parameter extractor

Prompt Merger Node & Type Converter Node

merger and converter node
  • Since the A1111 format cannot store text_g and text_l separately, SDXL users need to use the Prompt Merger Node to combine text_g and text_l into a single prompt.
  • Since model_name, sampler_name, and scheduler are special types that cannot be directly used by some other nodes, You can use the Type Converter Node to convert them into STRING type.

Lora Loader Node & Lora Selector Node

lora loader and selector node
  • The Lora Loader Node and Lora Selector Node are used to write Lora data into metadata and support auto-detection on Civitai.
More Information
  • Replace the original loader with the Lora Loader Node, or connect the LORA_NAME output of the Lora Selector Node to the lora_name input of other lora loaders (built-in or custom), and link the NEXT_LORA output to the lora_name input of the Prompt Saver Node. Both of these nodes have the same function, please choose according to your needs.

Multiple Loras

  • If you need to load multiple Loras, please connect the Lora Loader Node or Lora Selector Node head to tail through last_lora and NEXT_LORA, and connect the NEXT_LORA at the end of the Lora chain to the lora_name input of the Prompt Saver Node.
  1. Lora Loader chain
lora loader chain
  1. Lora Selector chain
lora loader chain

Example Workflow

Simple Example
example workflow
Lora Example
example workflow
Hires-fix Example
example workflow
SDXL Example
example workflow

Credits