Scale Factor

Some nodes resize images, some nodes detect faces. This one just holds a number. SimpleSyrup.ScaleFactor outputs a single FLOAT multiplier, bounded from 1.0 to 5.0 in 0.1 steps, defaulting to 1.5. It exists so you can drive every "scale factor" input in a workflow from one visible slider instead of typing the same value into three widgets and hoping you remember to update them together.

In ComfyUI's plumbing layer this is a "typed primitive" - the kind of node that breaks a value out of a widget and lets the graph fan it out from a single socket. It's deliberately the boring version: no type inference, no magic. You slide it, it emits a float. The bounds are the feature. Most scale-factor inputs in this pack are clamped for a reason; a detailer that scales a crop by 8x is usually a mistake, and keeping the knob at 1.0–5.0 means you can't accidentally type 50 and explode your VRAM.

Where you'll actually reach for it:

• The pack's own detailers - Detail SEGS by Scale Factor and its tiled-diffusion sibling - take a scale_factor input. Wire this node in, and one slider controls how much every detected region gets enlarged before resampling.
• Any custom node whose FLOAT input has been converted to accept a wire. The 1.0–5.0 range is generous enough for upscaling passes and sane for detailing, so it works as a general-purpose multiplier.

The single input is value, and the single output is scale_factor. Semantics from the tooltip: 1.0 keeps the target at its current size, larger values scale it up, max is 5.0x. If you need to go past 5.0, this isn't the node - you'd want a plain float primitive for that, and you should probably question the workflow instead.

Installation is just the pack: ComfyUI Manager → search SimpleSyrup → Install → restart, or clone it manually:

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

SimpleSyrup uses ComfyUI's v3 extension API, so keep your ComfyUI install updated or the pack's nodes won't register. There's no real troubleshooting to do here - if the slider's output isn't reaching your target node, you converted the wrong widget to an input, which is the one thing that trips everyone up the first time.