Sigmas2 Mult

Sigmas2 Mult is Sigmas2 Add's sibling in RES4LYF's sigma-math toolbox: two sigma schedules in, one out, but multiplied instead of summed. That difference matters more than it sounds - addition offsets a curve, multiplication reshapes it.

What it's for

A SIGMAS list is the noise level a sampler runs through at each step, and RES4LYF ships a whole family of nodes for editing that list directly rather than picking a preset scheduler. Multiplication is the tool you reach for when you want one schedule to act as an envelope on another - dampening some portion of the curve, exaggerating another, without shifting every value by a flat amount the way addition would.

How it works

Elementwise multiplication: sigmas_1[i] * sigmas_2[i] for every position i, producing a list the same length as the inputs. If sigmas_2 is a curve that dips toward zero in the middle and stays near one elsewhere, multiplying by it will pull down just the middle of sigmas_1 - a shaped attenuation rather than a uniform one. This is the same idea as an amplitude envelope in audio synthesis, applied to a noise schedule instead of a waveform.

The inputs and outputs that matter

Two required SIGMAS inputs - sigmas_1 and sigmas_2 - and nothing to tune beyond that. The single SIGMAS output goes wherever a custom schedule is accepted: RES4LYF's own ClownsharKSampler has a dedicated SIGMAS input that overrides its built-in scheduler and step settings entirely when something's connected to it, or you can chain the output into another sigma node before it gets there.

How to install it

• ComfyUI Manager - search "RES4LYF", install, restart.
• Manual - activate your venv, cd ComfyUI/custom_nodes && git clone https://github.com/ClownsharkBatwing/RES4LYF, cd RES4LYF, pip install -r requirements.txt (portable installs use the embedded pip.exe instead). Restart.

Common issues & troubleshooting

Match your step counts first. Multiplication has no defined behavior across mismatched-length lists, and the pack doesn't document what happens if you try - build both inputs from schedulers set to the same step count to avoid the question entirely.

Watch for a schedule that no longer decreases cleanly. Multiplying two arbitrary curves together can produce a result that isn't monotonic anymore, and a sampler generally expects noise level to trend downward across the run. If the output looks jagged, Sigmas Abs and Sigmas Cleanup are the tools to reach for before it goes into an actual sampler - Abs fixes sign, Cleanup enforces a minimum.

A near-zero sigmas_2 will crater the whole schedule at that point. Because it's multiplication, any value close to zero in one input collapses the corresponding step in the output almost to nothing. That's a legitimate way to force extra convergence at a specific point in the run, but it's easy to do by accident if sigmas_2 came from a node (like one of the pack's chaos or attractor generators) that wasn't built with this in mind.

No documented recipe. As with the rest of RES4LYF's sigma toolbox, this node isn't covered in the README beyond the general framing that the category is experimental. There's no community-tested "here's what to multiply by" - you're building and checking your own curves. Sigmas Count is worth wiring in to confirm step count before you commit to a full render on an untested combination.