🔂 CR Batch Process Switch

This is a mode toggle for graphs that can run two ways: process one image, or process a batch. Instead of building two separate workflows, you wire both an image and an image_batch in, flip one dropdown, and the node passes through whichever mode you picked. The rest of your graph downstream doesn't need to change.

It's one of Comfyroll Studio's process switches (Suzie1 / RockOfFire), alongside Img2Img Process Switch and Hires Fix Process Switch. They're all the same idea - a single control that reconfigures which branch of a flexible workflow is live. No generation, just routing.

How it works

The Input dropdown has two settings, image and image batch. Whichever you select, that connection is what comes out the single IMAGE output; the other input is ignored. So you can keep a single-image test path and a full-batch production path both wired up at once, and switch between them with one click instead of rerouting wires.

The inputs that matter

• Input - the mode selector: image or image batch. This is the whole control.
• image (optional) - your single-image branch.
• image_batch (optional) - your batch branch.

Both image inputs are optional so you only need to connect the branch you're actually using, but the point of the node is to have both wired and toggle between them. Output is a single IMAGE plus the show_help link, which is just a wiki reference you can leave dangling.

Where this earns its place is a workflow you run in two rhythms: quick single-image iteration while you're dialing in a prompt or settings, then a full batch once you're happy. Rather than maintain two graphs that drift apart, you keep one and flip the switch.

How to install it

• ComfyUI Manager: search Comfyroll Studio, install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, then restart.

No models - it's a routing utility.

Common issues

The catch that bites people with any switch node in ComfyUI: selecting a mode doesn't stop the other branch from executing. If your image_batch input is driven by an expensive upstream chain, that chain still runs even when you've switched to image mode - ComfyUI evaluates connected nodes regardless of which one this switch forwards. If you're switching to save compute, this node alone won't do it; you'd want to mute or bypass the unused branch instead.

Second, make sure the branch you selected is actually connected. Switch to image mode with nothing plugged into the image input and you'll hand an empty output downstream, which errors where it's consumed. And if the node's missing from your menu, that's the Comfyroll pack failing to load - a pack-level problem, not this node.