Pipe Out Sampler Settings (Dual-Scheduler)

Some sampler setups are pickier than others, and this node is for the picky ones: it unpacks a pipe that carries two schedulers, not one. Its output list is sampler, scheduler, scheduler_2, steps, cfg, flux_guidance, plus upscale_model and scale_by. That second scheduler slot is the whole personality of this variant.

Where does a second scheduler come from? Some workflows split the denoise run - a first pass with one noise schedule, a refine or upscale pass with another. On a dual-scheduler pipe, both choices travel together so they can't drift out of sync. That's also why it carries an upscale_model and a scale_by value: this pipe was built for the "sample, then upscale-sample" pattern, not single-pass generation. If you're doing hires-fix-style two-phase sampling and want the whole configuration to move as one bundle, this is the node that hands you the pieces at the end.

Mechanically it's identical to every other RvTools Pipe Out: one pipe input, the same pipe passed through untouched, and each bundled field split out to its own output. Open the source and it's a tuple unpack. The values themselves were bundled upstream by a matching sampler-settings Pipe In node - wire the wrong partner into this unpacker and the shape won't match.

The honest warning: this one is marked DEPRECATED, and so is its category. RvTools v2 itself is unmaintained, with the README pointing to the successor pack ComfyUI_Eclipse. The dual-scheduler variant is also the most niche of the sampler-settings family - most modern Flux and SDXL work has settled on a single scheduler (Euler-family for flow models, DPM++ 2M Karras for SDXL), so a second scheduler slot mostly shows up in older or very custom workflows. If you see this node in a downloaded workflow, it usually means the author was doing two-phase sampling and kept the settings bundled for cleanliness. It'll run, but it's not where you'd build new work today.

Installing it

It's in the ComfyUI-RvTools_v2 pack. ComfyUI Manager: search "ComfyUI-RvTools_v2". Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2

Restart ComfyUI. Dependencies (torch, numpy, Pillow, opencv-python, pilgram, pynvml, piexif) install via Manager. No models, no keys.

Where people get burned

• Tuple mismatch. Every Pipe Out node expects its own exact pipe shape. The dual-scheduler pipe has nine fields; a plain sampler pipe has four. Mix them and you get a ValueError: not enough values to unpack at runtime, not at wiring time.
• Deprecation. This is a v1-era pipe layout, superseded inside the pack and by the pack's own successor. Don't build new workflows on it.
• Two schedulers means you need two scheduler consumers. If your sampler only takes one, scheduler_2 just dangles unused - that's fine, but then you're carrying a dead field.