SchedulerEfficiencyToString (Citron Image Saver)

Thirteen schedule names, one string. This is the output-only variant of the Efficiency scheduler selector: it doesn't feed anything except the save node's scheduler_name field, and if that's all you need, it's the shortest wire on the canvas.

How it works

One input, scheduler: the nine standard schedules (simple, sgm_uniform, karras, exponential, ddim_uniform, beta, normal, linear_quadratic, kl_optimal) plus AYS SD1, AYS SDXL, AYS SVD and GITS. One output, scheduler_name (STRING), value unchanged.

That's it - no combo-typed second output, so it can't drive a sampler. Use it when your sampler is an Efficiency megapack node holding the scheduler as a widget and you'd rather not convert that widget into an input just to echo the value into metadata. If you want one dropdown controlling both the sampler socket and the recorded name, use Scheduler Selector (Eff.) instead.

Two things to keep straight while you're here. The Efficiency list is the narrower of the pack's two extended lists: no OSS schedules, and GITS is written bare, without the [coeff=1.2] suffix the Inspire selector uses. Pick the wrong one and you get a validation error that reads like a typo but is really a version of the same schedule from a different pack. And the list is hardcoded - it'll offer AYS SDXL on a machine with no Efficiency Nodes installed, which is fine for metadata and not fine for sampling.

Is any of this worth wiring? For a sweep, yes. Set AYS SDXL, run twelve steps, compare against simple at the same count, keep the winner - and be able to tell afterwards which file was which without opening them. For a one-off generation, the honest answer is that the default normal in the saver's field isn't going to hurt anyone who isn't publishing. But if you post to CivitAI, the parameters block is the thing other people read, and "Scheduler: normal" on a Flux image that ran AYS SDXL is just wrong.

One nice property of the whole pack's design shows up here: everything is a value node, so you can convert any sampler's scheduler widget to an input and drive it from the corresponding selector - the string and the actual schedule then share a single source of truth, and the metadata can't drift. This node is the lighter option when you don't want to touch the sampler at all.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/citronlegacy/ComfyUI-CitronNodes
# restart ComfyUI

ComfyUI Manager may not have this indexed - the README says "coming soon" and the repo metadata is placeholder - so clone. piexif is the only pip dependency and it's required for the pack to import at all:

pip install piexif

Nothing to download. It lands under Citron_ImageSaver/utils.

Common issues

• It won't connect to my KSampler. By design - string output only. Use Scheduler Selector (Eff.) if you need the combo side.
• GITS[coeff=1.2] missing. Wrong node; that spelling is in the Inspire family.
• Metadata still says normal. The wire isn't reaching the saver's scheduler_name input.
• Queue fails after picking AYS. Efficiency Nodes isn't installed, or the value went into a stock KSampler. Both produce the same "not in list" style failure.