Prompt Encode Style & Normalization

This is the slightly bigger brother of Prompt Encode Style - same job, one extra knob. Where the basic node emits STYLE(A1111) , this one can emit STYLE(A1111, length) : the Prompt Control encode-style tag plus a prompt-weight normalization mode. If you've never heard of prompt-weight normalization, the node is still safe to use - leave it on none and you have exactly the basic node with an extra dropdown.

For the two inputs, the tooltips are the whole story:

• encode_style (default A1111) - the Prompt Control encoding style written into the tag. Choices: A1111, Comfy, Comfy++, Compel, Down Weight, Perp. The one that matters most for WebUI refugees is A1111; it makes Prompt Control interpret weighting syntax the way their old UI did.
• normalization (default none) - the weight normalization mode written into the tag: none, length, mean, or length+mean.

What normalization actually does: prompts with a lot of (word:1.4) weight syntax can end up with effective conditioning that's stronger than the model expects - a prompt that's all emphasis has no baseline. Normalization rescales the weights so the prompt's overall strength lands somewhere sane: length divides by prompt length, mean centers the weights on their average, and length+mean does both. It's a "my 400-word prompt of pure emphasis is scorching the image" fix, not a daily knob. If your regional prompts pile on weight syntax and the output looks over-amped no matter what you do, that's the case this dropdown exists for.

Output is one string, encode_style, ready to wire into any prompt-assembly step. Same ecosystem caveat as the basic node: STYLE(...) is Prompt Control syntax, so this node is meaningful only if ComfyUI Prompt Control is installed and interpreting your prompts. Without it, the string is inert text. SimpleSyrup treats Prompt Control as an optional integration - the pack loads fine without it, and these nodes exist to serve the Prompt-Control-based regional/scheduled prompt workflows the pack supports.

It's a two-dropdown utility and it knows it. Don't reach for it unless you're already in a Prompt Control workflow and you want the encode style and normalization defined in one visible place instead of memorizing tag syntax. That's the honest value: consistency and legibility, not new capability.

Install: the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/Artificial-Sweetener/SimpleSyrup
cd SimpleSyrup && pip install -r requirements.txt

or ComfyUI Manager → search SimpleSyrup → Install → restart, with a current ComfyUI (v3 extension API). No models, no heavy dependencies. If the emitted tag has no effect on your renders, Prompt Control isn't in the graph - nothing else interprets STYLE(...), and no amount of normalization dropdowns changes that.