Detailer Pipe Switch

The DETAILER_PIPE is the compact bundle of settings that Impact Pack's detailer nodes use - detector, model, prompt, denoise, and all the rest, carried down a single wire. The Detailer Pipe Switch is a two-position toggle for exactly that bundle: Input 1 or 2 picks which DETAILER_PIPE flows through to the node that runs the detail pass.

Where this fits in a real workflow

Face and hand detailing is how you rescue an otherwise-good image - the automated inpainting pass that crops the face region, re-samples it at higher detail, and pastes it back. In ComfyUI, Impact Pack's FaceDetailer is the community-standard answer to ADetailer from the A1111 world, and it's fed by a detailer pipe that bundles all its settings.

The problem the switch solves: a "fix the face" setup and a "fix the hands" setup are two different bundles - different detector models, often different prompts and denoise strengths. Without a switch, you'd either maintain two separate detailer branches or rebuild the pipe every time you swapped intent. With the switch, you build both pipes once, wire them into input1 and input2, and flip a widget.

The more interesting habit: use one slot as an off switch. Leave input2 empty, set Input to 2, and the switch passes None - which disables the detail pass entirely. That's your A/B test for "does this detailing actually improve the image?" You also get the workflow's generic bypass convention, spelled out in the README: if the switch itself is bypassed, it passes whatever is on input1. Bypass means "default to slot 1", so keep your usually-wanted pipe there.

What's on the node

• Input - the 1-or-2 widget that does the selecting.
• input1 / input2 - optional DETAILER_PIPE inputs, both forceInput (wire-only). These come from Impact Pack's Detailer Pipe Setup / Detailer For AnimateDiff style nodes, or from other RvTools detailer pipe passers.
• DETAILER_PIPE output - the chosen bundle, feeding a FaceDetailer or DetectorCustomEffect node.

One honest note: this switch only makes sense if you're already living in the detailer-pipe world. If you run detailing through raw node wiring instead of pipes, a generic model switch does the same job. It's a pipe-life convenience, not a capability.

Install

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

Or via ComfyUI Manager, searching "ComfyUI-RvTools_v2". It does not bundle Impact Pack - that's a separate install, and you'll need it (plus the detector models it wants) before this switch has anything to route. The pack's own deps are the standard torch/numpy/Pillow/opencv-python/pilgram set.

The standing caveat

The README flags the whole pack as unmaintained and points to ComfyUI_Eclipse as the successor. The RvTools lineage also has a rough install history - the original repo was yanked from GitHub in early 2025, breaking shared workflows and sending people scrambling to copy node folders between installs (documented in the r/comfyui thread on it). v2 installs cleanly and keeps legacy workflows alive; for new builds, Eclipse is where the author moved.