SchedulerInspireToString (Citron Image Saver)

Sixteen scheduler names in, one string out. This is the string-only sibling of the (inspire) scheduler selector, for the case where the schedule is already being set somewhere you don't want to touch and all you need is the label for your metadata.

How it works

One required input, scheduler, with the nine core schedules plus the Inspire Pack additions: AYS SDXL, AYS SD1, AYS SVD, GITS[coeff=1.2], OSS FLUX, OSS Wan, OSS Chroma. One output, scheduler_name, a STRING carrying exactly what you picked.

Note the exact spellings - GITS[coeff=1.2] includes the bracket and coefficient, which is why hand-typing these names into a save node is such a bad habit. One missing character and your metadata no longer matches the value the sampler accepted, and nothing warns you.

Use it when you're running a megapack sampler whose scheduler is a widget, and you don't want to convert that widget to an input just to echo it into the save node. If you do want one dropdown driving both the sampler and the metadata, use Scheduler Selector (inspire) instead - it has the combo-typed output as well. This node is the cheap half.

Same honest caveat as its selector sibling: the list is hardcoded here, not read from your install. It offers OSS Wan whether or not ComfyUI-Inspire-Pack is present, and those values are only valid to the Inspire sampler. Recording one is harmless; feeding one into core's KSampler fails validation.

Whether the Inspire schedules are worth the trouble depends on what you're running. The AYS family is a hand-tuned step schedule per model family, so it wants the step counts it was tuned for; the OSS ones are optimal-step schedules aimed at Flux, Wan and Chroma specifically. On those architectures the difference from simple is real but not dramatic, and it's the sort of thing worth one A/B, not a permanent belief. On SDXL, where karras already does the heavy lifting, AYS SDXL is a reasonable alternative to try at low step counts and rarely a revelation.

The reason to have the node at all: after a sweep, the first question you'll ask is "which schedule was that?" A file that answers it is worth the one wire.

Install

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

Manual clone is the dependable route - the README still lists ComfyUI Manager support as "coming soon" and the repo's packaging metadata is placeholder. The pack's only pip dependency is piexif, imported by the saver module; a missing copy takes every node in the pack down:

pip install piexif

No models. Category: Citron_ImageSaver/utils.

Common issues

• Value not in list when I queue. An Inspire-only name reached the stock KSampler. Either it drives the Inspire sampler or it shouldn't be selected.
• Metadata shows a different scheduler than the sampler. Two selections again. Drive the sampler's scheduler from a selector, or accept this node as a record of intent only.
• OSS Chroma isn't in my workflow's dropdown. You're looking at the plain scheduler selector or the Efficiency one. Only the inspire pair has the OSS names.
• Nothing written to the file. The saver's scheduler_name input isn't connected to this output.