Scheduler Select name

Scheduler Select name is the string-returning twin of PgSchedulerSelect. Same dropdown over ComfyUI's schedulers - normal, karras, exponential, ddim_uniform, sgm_uniform, beta, simple, and friends - but instead of building a SCHEDULER object it just hands back the name you picked as a plain string. The display name says "name," and it means it.

Why would you want the name instead of the object? Because not every node accepts a SCHEDULER input. Some loaders, converters, and combo-style nodes take the scheduler as a plain string value - often one that travels inside a bigger bundle or gets re-encoded elsewhere. When a dropdown's value is really just a label that some other node parses, returning the label itself is the honest implementation. It's the same split the pack makes for samplers: Sampler Select returns an object, Sampler Select name (PgSamplerSelectCombo) returns a string.

How it works

The dropdown builds from KSampler.SCHEDULERS at import, so it tracks your ComfyUI version (restart to refresh it). process() returns the selected name unchanged on the scheduler output. That's the entire mechanism - no object construction, no state, nothing to go wrong.

The practical case that makes this pair of nodes worth keeping around: you build one workflow where a scheduler name has to reach a node that only takes strings, and another where the object type is required. Rather than switching node packs or wrestling with conversion, the PG pack just gives you both flavors. Minor, but it's the kind of foresight that keeps a graph from accumulating red wires.

The input and output

• scheduler_name - dropdown over the installed scheduler names.
• Output: scheduler, typed as the literal list of scheduler names - i.e., a string that ComfyUI validates against those choices. So you get type-checking benefits even though it's text.

Install

Comes with PG Nodes:

ComfyUI Manager → search "PG Nodes" → Install → restart

Manual: git clone https://github.com/GizmoR13/PG-Nodes into custom_nodes (rename to PG-nodes), restart. Found under PG/Select. No dependencies, no model files.

Common issues

• Can't plug it into a SCHEDULER input. Right - it's a string, not an object. If your target node wants the real thing, swap to Scheduler Select. That's why both exist.
• List looks stale. Rebuild happens at import; restart after updating ComfyUI to see new scheduler names.

Real talk: this is a compatibility shim, and it's fine for that. If your workflow never needs a string scheduler name, you can skip it and use the object version. But when a loader or a third-party node insists on a name string, having this exact node already installed saves you a frustrating search through node packs.