Nodes/saya-comfy-couple-plus/Saya Dual CLIP Text Encode
ComfyUI Node

Saya Dual CLIP Text Encode

A CLIP encode with a kill switch (and no, it's not 'dual' like you think)

By alphaziod·Created 3 months ago·Updated about 15 hours ago· 3
Saya Dual CLIP Text Encode
  • clip
  • conditioning
text
send_datatrue

First, a name correction so you don't go looking for the wrong thing: "Dual" here doesn't mean dual text prompts or two CLIP models. This is a bog-standard single-prompt text encoder - same clip in, conditioning out as ComfyUI's core CLIPTextEncode - with one extra button that makes it interesting. The button is send_data, and it's the whole reason this node exists in the pack.

When send_data is on (the default), the node tokenizes your text and encodes it exactly like a normal CLIP text encode, using encode_from_tokens_scheduled under the hood. When it's off, it skips encoding entirely and returns an empty conditioning ([]).

Why would you ever want that? Because it gives you a clean, explicit way to disable one prompt branch of a workflow without hacking at bypass states. The pack's couple architecture wants the same graph shape whether you're generating solo or duo: a person-2 encode is always present in the layout, and in a solo run it should contribute nothing. Rather than building bypass logic everywhere, the author's workflows just flip send_data off on the empty branch and the node emits a legitimately-empty conditioning that the couple node already knows how to treat (an empty person 2 conditioning is what triggers its solo mode). It's the node-version of turning a wire off at the source instead of clipping it downstream.

Inputs

  • clip - your CLIP encoder (from a checkpoint, dual-CLIP, or UNET loader).
  • text - the prompt, multiline.
  • send_data - the toggle. True encodes; false returns the empty conditioning.

That's it. One output, conditioning, feeding wherever you'd feed an encode - in this pack typically the main_positive / person_1_positive / person_2_positive / negative inputs of the SayaComfyCouple node.

When you'd actually use it

Honestly? If you're not inside the Saya couple/phase architecture, reach for the core CLIPTextEncode and don't think twice. This node is a convenience for the specific pattern where one graph must support both solo and duo generation, or where a "rescue" phase needs to be able to null out a prompt that isn't relevant. The value is the ergonomics - one node that can both encode and not-encode depending on a boolean, so a workflow can be saved with both behaviors in place and switched by a single widget.

One thing to keep in mind: an empty conditioning and a "no connection" are different things to downstream nodes. The couple node in this pack treats an empty person-2 conditioning as "solo"; a dangling wire would just fail. So the off-state here is intentional, not a workaround for a broken graph.

Install via ComfyUI Manager (search saya-comfy-couple-plus) or clone https://github.com/alphaziod/saya-comfy-couple-plus into custom_nodes and restart ComfyUI. Dependencies are just numpy and Pillow, nothing to download. The pack is WIP and under active refactor, so if a saved workflow shows stale ports after an update, restart fully and re-add the node.

Categorysaya/rescue

Inputs (3)

NameTypeDefaultDescription
clipCLIP
textSTRING
send_dataBOOLEANtrue

Outputs (1)

NameTypeDescription
conditioningCONDITIONING