Sigmas From Text

The most literal node in the pack. Sigmas From Text is a text box that turns numbers you type into an actual sigma schedule. Paste a list of sigma values, get a SIGMAS output your sampler can use. That's the entire feature, and it's more useful than it sounds.

Why type a schedule by hand? Two real reasons. One, you found a specific schedule someone shared - a sequence of sigmas that works great for a particular model - and you just want to use it verbatim without rebuilding it from scheduler knobs. Two, you're experimenting and want total control: exact values, exact step count, no scheduler math in the way. It's the bring-your-own-schedule option.

How it works

You type numbers into the multiline box - a sigma per entry, descending toward zero the way schedules run. The node parses them into a SIGMAS object. Feed that into a sampler's sigmas input and it overrides the sampler's built-in scheduler and step count entirely: your typed list is the schedule, and its length is your step count.

The inputs and outputs that matter

There's exactly one input and one output:

• text (STRING, multiline) - your sigma values. This is the node.
• sigmas (SIGMAS, output) - wire into the sampler.

The number of values you type sets the number of steps. A schedule that ends at (or near) 0 denoises fully; one that stops short leaves residual noise, which is occasionally what you want for img2img-style partial passes.

How to install it

ComfyUI Manager: search RES4LYF, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF
cd RES4LYF
pip install -r requirements.txt

Portable ComfyUI: use the embedded pip. Restart and hard-refresh with F5. No downloads.

Common issues & troubleshooting

It won't parse my text. Formatting is the usual culprit. Keep it to plain numbers with a consistent separator (one per line is safest), no stray letters or trailing punctuation. If you copied a schedule out of a log, strip the brackets and commas the source added.

The image is noisy / not fully denoised. Your last sigma probably isn't 0 (or close to it). A proper schedule descends to zero. If you meant to leave noise in for a partial pass, that's fine - but if you wanted a clean image, end the list at 0.

Values out of order. Sigmas should decrease across the schedule. A list that jumps around will produce garbage. Sort it descending unless you're deliberately doing something exotic.

Pairs nicely with TextLoadFile. If you keep a few favorite schedules around, save them as .txt files and load them with the pack's TextLoadFile node into this one, instead of retyping. And if you'd rather generate a schedule than type it, that's what the scheduler nodes (or plain beta57) are for - this node is specifically for when you already have the numbers.