Enviral Scheduler Name

The scheduler is the least-thought-about knob in KSampler and often the one that makes or breaks a model. Pick karras for a model tuned to it and get clean convergence; pick it for a guidance-distilled model and you can get mush. And like every other native dropdown, you can't wire a string into KSampler's scheduler field.

Enviral Scheduler Name is the adapter for exactly that socket. Dropdown of the current scheduler list, linked-string input accepted, native combo output for KSampler.

How it works

Options come live from comfy.samplers.KSampler.SCHEDULERS, so the list tracks your ComfyUI version: simple, sgm_uniform, karras, exponential, ddim_uniform, beta, normal, linear_quadratic, kl_optimal. If a future ComfyUI adds a scheduler, it appears here without a node update.

String matching is the same forgiving scheme as the rest of the pack's selectors: exact, then case/path-normalized, then unique suffix, with closest-match suggestions in the validation error if your string is garbage.

Input and output

• scheduler - dropdown or linked string; defaults to simple.
• Output scheduler - native combo, straight into KSampler's scheduler.

Two sockets. That's it.

Install

Ships in the Enviral Design Node Pack. ComfyUI Manager: search "Enviral Design Node Pack". Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/EnviralDesign/comfyUI-enviral-design-node-pack

then restart. No dependencies beyond what ComfyUI already has.

Why you'd bother

It pairs naturally with Enviral Sampler Name in "recipe" graphs: one Custom Combo string drives sampler, another drives scheduler, and KSampler just executes. That's genuinely handy for workflows that branch between SDXL-era models (karras) and modern distilled models (simple or sgm_uniform at CFG ~1) - the correct scheduler depends on the model family, and a string-driven picker lets one graph adapt. If you never switch schedulers, you don't need it. If you do, this removes the last hardcoded menu in the chain.