Input Parameters (Citron Image Saver)

This is the node I'd actually put on the canvas first. Six widgets - seed, steps, cfg, sampler, scheduler, denoise - and eight outputs, so the same numbers that drive your sampler also feed your save node, your filename template, and anything else in the graph that wants them. One place to change a value, no drift, and metadata that can't contradict reality.

The pack's README calls it "Combined node for seed, steps, cfg, sampler, scheduler and denoise," which is exactly right and slightly undersells it: the useful part is that it hands out both the combo-typed and the string-typed version of the sampler and scheduler, which is otherwise a two-node adapter job.

How it works

Six inputs, all required, all with the docstrings ComfyUI's own KSampler uses - the CFG tooltip is verbatim the core one about balancing creativity against prompt adherence. seed goes up to the 64-bit ceiling and has control_after_generate attached, so the familiar fixed/increment/decrement/randomize dropdown is there. steps runs 1–10000. cfg runs 0–100 in 0.1 steps; the SD-lineage sweet spot lives in 5–9, distilled and flow models want about 1, and at exactly 1 ComfyUI skips the unconditional pass entirely, which is a real speed win rather than a rounding detail. sampler is the 44-name core list, scheduler the nine-name list, denoise 0–1 in 0.01 steps.

Eight outputs: seed, steps, cfg, sampler, sampler_name, scheduler, scheduler_name, denoise. The values go through untouched; sampler and sampler_name carry the same selection in two types, and so do scheduler and scheduler_name.

That split is the entire value proposition. Wire sampler into the KSampler's sampler input (converted to a socket) and sampler_name into the Citron saver's sampler_name text input. Same for scheduler. Now try a different sampler and both the run and the record change together. Everything else - steps, cfg, seed, denoise - goes to the sampler and to the saver and, if you're using the templated filename, into %steps and %cfg as well.

What it doesn't cover: prompts, model name, width/height, clip skip. Those come from elsewhere - a String Literal for prompts, the pack's checkpoint/UNet loader for the model name, a width/height literal for size. This node is the sampler's parameter block, not the whole metadata block.

One quirk worth expecting: because these are six widgets feeding eight outputs, the canvas gets a bundle of wires from a single small node, and people often assume it's a "package" that must be unpacked before use. It isn't - the outputs are ordinary typed sockets, and you wire the ones you need. Leave the rest dangling.

Install

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

Manager search is unreliable - README says support is "coming soon", the repo metadata is placeholder - so clone it. Only pip dependency is piexif, needed by the savers and required for the pack to import at all:

pip install piexif

No models. It's under Citron_ImageSaver/utils.

Common issues

• Sampler or scheduler won't connect. You're wiring the string output into a combo socket. Use sampler/scheduler for the KSampler and the *_name versions for the saver.
• Metadata disagrees with the run. Some other node is still driving the sampler from its own widget. The sampler's widget wins over a dangling wire every time.
• Seed changed after the run instead of before. That's control_after_generate doing what it says - it fires after the queue finishes, so the number in the box isn't the one that ran. Switching ComfyUI's global widget control mode to "before" fixes that permanently.
• CFG of 1 makes the metadata look wrong. It isn't - CFG 1 genuinely means the negative pass was skipped, so the negative prompt in the file did nothing.