Scheduler Selector (Restart)

One dropdown, one output, zero processing. Scheduler Selector (Restart) presents the eight schedulers that the ComfyUI-Restart sampler pack understands - normal, karras, exponential, sgm_uniform, simple, ddim_uniform, beta and simple_test - and outputs whichever you pick as a plain scheduler string. Its whole reason to exist is that "Restart" nodes (samplers that periodically re-add noise mid-sampling) have their own slightly nonstandard scheduler list, and people kept typing simple_test wrong or feeding a scheduler the Restart node didn't accept.

How it works

Same architecture as every selector in this pack: the input widget is the output. You choose from the dropdown, execute() returns the string, and the typed output plugs directly into a sampler or scheduler port that expects one of those values. VALIDATE_INPUTS always returns true, so it'll never reject anything you type even if you stray outside the listed set - which is both a feature (manual values allowed) and a tiny footgun (typos pass through silently).

The inputs that matter

• scheduler_restart - the one required dropdown. Output scheduler echoes it.

That's it. For a Restart sampler workflow, the pairing to remember is the sampler name plus this schedule; the two travel together in Restart-pack examples.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2

Restart ComfyUI or install via ComfyUI Manager (search "ComfyUI-RvTools_v2"). No model downloads, no extra deps.

Honest take

This is one of the thinnest nodes in the pack, and it's marked DEPRECATED - both because the author moved on and because a stock KSampler's own scheduler dropdown already contains every one of these eight values. The only case where this node earns its place is a mixed-pack graph where you want to guarantee the value arriving at a Restart node is one it accepts, or where you're parameterizing the schedule from a switch further up the graph and need a clean typed source. Otherwise you can skip it. And the usual RvTools caveats apply: the pack is unmaintained (ComfyUI_Eclipse is the successor), and if an old workflow references the v1 RvTools version of this node, that repo is dead and Manager can't fetch it - swap in the v2 node manually.