Nodes/ComfyUI-RvTools_v2/Pipe Out Sampler Settings (Flux+Seed)
ComfyUI Node

Pipe Out Sampler Settings (Flux+Seed)

Flux sampling settings with the seed on the same pipe

By r-vage·Created about a year ago·Updated 5 months ago· 23
Pipe Out Sampler Settings (Flux+Seed)
  • pipe
  • pipe
  • sampler
  • scheduler
  • steps
  • cfg
  • flux_guidance
  • denoise
  • seed

Of the half-dozen sampler-settings Pipe Out nodes in RvTools, this one is the middle child, and the honest take is that it's the one you'll reach for most in practice. It unpacks a Flux sampler pipe that includes the seed, which is the single most useful value to keep in the bundle - because seed is the thing you change between runs.

"Pipe Out Sampler Settings (Flux+Seed)" takes one pipe input and hands back sampler, scheduler, steps, cfg, flux_guidance, denoise, and seed, plus the pipe itself passed through. Seven fields, and the only real difference from the plain Flux variant is that seed rides along. Mechanically that's it - a tuple unpack in a trench coat, like every node in this family.

Why does seed-in-the-pipe matter? Because it's the axis of iteration. When you're tuning a Flux workflow, you fix the seed to test one variable at a time, then bump it to see variation. If the seed is bundled with the other sampler settings, it travels the same path as everything else and can't get lost in a bypassed node or a group boundary. Iterating a bunch of prompts or seeds through one workflow is exactly the "batch through the same graph" pattern that pipes exist for.

The fields themselves follow the same rules as the base Flux variant: Euler-family sampler on a conservative scheduler, low step counts, flux_guidance doing the work CFG did on SD1.5, denoise for img2img strength. The cfg output is still there even though Flux mostly ignores it - it travels in the pipe because the pack's pipe layouts keep a common shape, so if you ever swap the same bundle toward a non-Flux sampler it still has a value to feed. Handy, and worth knowing before you wonder why "cfg" is doing nothing.

Installing it

It's part of ComfyUI-RvTools_v2. ComfyUI Manager: search "ComfyUI-RvTools_v2". Or the manual route:

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

Restart ComfyUI after cloning. The pack's dependencies (torch, numpy, Pillow, opencv-python, pilgram, pynvml, piexif) install through Manager; no model downloads, no keys.

Where people get burned

  • Pick the variant that matches your pipe. The Flux+Seed unpacker wants the seven-field pipe with seed. Feed it the plain Flux pipe (no seed) and you'll hit a tuple ValueError at runtime - the wire colors are all the same, so this won't be caught until you queue.
  • Seed vs. random. If the seed output arrives as a fixed value, every queue is the same image; that's the point. To vary, drive the seed from a random source upstream in the matching Pipe In node, not here.
  • Deprecation. The RvTools v2 pack is unmaintained, superseded by ComfyUI_Eclipse per its README. Works as installed; plan migration for new work.
Category🫦 RvTools II/ Pipe

Inputs (1)

NameTypeDefaultDescription
pipepipe

Outputs (8)

NameTypeDescription
pipepipe
sampler*
scheduler*
stepsINT
cfgFLOAT
flux_guidanceFLOAT
denoiseFLOAT
seedINT