NS Many Sliders

NS Many Sliders is exactly what the name says: a bank of up to fifteen sliders, each ranging −1 to 1, that all collapse into a single comma-separated string on the output. That's the whole node. No model patching, no image processing, no hidden AI. Just a row of knobs and a string.

So why would you want that? Because there's a class of ComfyUI workflow where you're tuning a list of numbers - per-channel strengths, prompt modifier weights, animation parameters - and you'd rather do it on visible sliders than by editing a text field or renumbering a batch. The node's own origin makes the intent clear: it was first a standalone repo (ComfyUI-NS-ManySliders) that the author plans to redesign as "switchable with presets" before folding it further into this pack. It's a utility, not a feature.

How it works

On the surface it's dead simple: slider_count (1–15, default 15) sets how many of the value_0 through value_14 sliders are active, and the node returns them as values - a single STRING like "0.3,-0.2,0,0.5,...".

Under the hood there's a YAML twist worth knowing about. The node reads a config file at nodes/ManySliders/settings.yaml on every refresh, and that file controls the slider count, range, step and default:

sliders:
  count: 15
  min_value: -1.0
  max_value: 1.0
  default_value: 0.0
  step: 0.1

Edit min_value, max_value, step or default_value there, restart (or let the node's file-watching pick it up), and every slider respects your new range. This is genuinely handy - most ComfyUI slider nodes hard-code their bounds - but it's also the first place people get confused, because the widgets you see on the node can disagree with what the node actually outputs if the file changed under it.

The gotcha: it's a string, not numbers

Here's the thing that trips everyone up the first time. The output is typed STRING, not a list of floats. If you wire values straight into a node expecting numbers, it'll fail or silently do the wrong thing. Whatever consumes this needs to parse the comma-separated text - or you use it in a context that expects a serialized list. The pack's own prompt/parameter tooling is where this slots in naturally; don't expect to plug it directly into a KSampler.

Second gotcha: the sliders only go −1 to 1 by default. If you need, say, 0–100, that's a settings.yaml edit, not something you can do in the ComfyUI sidebar.

When you'd reach for it

You're building a workflow that takes a hand-tunable list of values - maybe you're driving a custom sampler or a parameterized prompt node - and you want the tuning surface to be sliders instead of a text box. That's this node's entire job, and it does it without drama. It won't do anything smarter than produce a string, and it's honest about that. For parameter sweeps where you set up a dozen knobs and tweak between runs, it beats retyping a list every time.

Installing it

Part of the ComfyUI-NS-Util pack. ComfyUI Manager → Install via Git URL:

https://github.com/NakamuraShippo/ComfyUI-NS-Util

or clone:

cd ComfyUI/custom_nodes
git clone https://github.com/NakamuraShippo/ComfyUI-NS-Util

Restart ComfyUI and it's there. Dependencies are light - pyyaml (which the settings file needs) plus the pack's other usuals. No model files, no downloads.

One tip: if the slider count or range on the node ever looks wrong, check nodes/ManySliders/settings.yaml before you blame the install. The node genuinely reads it on every load, and a hand-edited count that's lower than the slider_count you requested just clamps to the file's value.