Cutoff for ComfyUI

what is cutoff?

cutoff is a script/extension for the Automatic1111 webui that lets users limit the effect certain attributes have on specified subsets of the prompt. I.e. when the prompt is a cute girl, white shirt with green tie, red shoes, blue hair, yellow eyes, pink skirt, cutoff lets you specify that the word blue belongs to the hair and not the shoes, and green tot he tie and not the skirt, etc. This is an implementation of cutoff in the form of 3 nodes that can be used in ComfyUI.

how does this work?

When you provide stable diffusion with some text, that text gets tokenized and CLIP creates a vector (embedding) for each token in the text. So if we have a prompt containing "blue hair, yellow eyes" some of the vectors coming out of CLIP will correspond to the "blue hair" part, and some to the "yellow eyes". When CLIP does this it tries to take the context of the entire sentence into consideration. Unfortunately CLIP isn't always as great at figuring out that the "blue" in "blue hair" should really only modify the noun "hair" and not the noun "eyes" a bit further in the sentence.

So how do we deal with this? we can mask out the tokens corresponding to "blue" and ask CLIP to create another embedding. In this new embedding we have a set of vectors corresponding to "yellow eyes" that are not affected by "blue", because blue wasn't part of the tokens. If we then take the difference between our original vectors and these new vectors we now have a direction we can travel in for the eyes to become more affected by "yellow" and less by "blue". If we do this for all the color relations in text we can travel to an embedding where each of these relations are more isolated. Of course this effect isn't limited to just colors.

ComfyUI nodes

To achieve all of this, the following 4 nodes are introduced:

Cutoff BasePrompt: this node takes the full original prompt

Cutoff Set Region: this node sets a "region" of influence for specific target words, and comes with the following inputs:

region_text: defines the set of tokens that the target words should affect, this should be a part of the original prompt. It is possible to define multiple regions in a single CLIPSetRegion node by stating every region on a new line.
target_text: defines the set of tokens that will be masked off (i.e. the tokens we wish to limit to the region) this is a space separated list of words. If you want to match a sequence of words use underscores instead of spaces, e.g. "a_series_of_connected_tokens". If you want to match a word that actually contains underscores escape the underscore, e.g. "the\_target\_tokens". You can target textual inversion embeddings using the default syntax but do note that any underscores in the name of the embedding have to be escaped in this input field.
weight: how far to travel in the direction of the isolated vector

Cutoff Regions To Conditioning: this node converts the base prompt and regions into an actual conditioning to be used in the rest of ComfyUI, and comes with the following inputs:

mask_token: the token to be used for masking. If left blank it will default to the <endoftext> token. If the string converts to multiple tokens it will give a warning in the console and only use the first token in the list.
strict_mask: When 0.0 the specified target tokens will not affect the other specified areas but do affect anything outside of those areas. When set to 1.0 the specified target tokens will only affect their own region.
start_from_masked: When 0.0 the starting point to travel from is the original prompt. When set to 1.0 the starting point to travel from is the completely masked off prompt. Note that specifically when all region weights are 1.0 there is no difference between the two

Cutoff Regions To Conditioning (ADV): provides the same functionality as the above node but also provides options on how to interpret prompt weighting. More on these settings can be found here.

You can find these nodes under conditioning>cutoff

SDXL

The nodes won't throw any errors when used with SDXL, but at least for 0.9 I didn't found it to be working that well.

Finally, Here are some example images that you can load into ComfyUI: