DeviceSelectorMultiGPU

Every other node in this pack has its own device dropdown baked in. DeviceSelectorMultiGPU is the odd one out - it isn't a loader at all. It takes one required input, device, and produces one output: a value named device, typed MULTIGPUDEVICE. No MODEL, no CLIP, nothing you'd wire straight into a sampler.

What it's actually for

The pack's own README notes that its device-selection idea extends well beyond the core ComfyUI loaders covered here - WanVideoWrapper alone gets eight bespoke MultiGPU nodes, on top of integrations for GGUF, Florence2, Pulid, and more. Some of those downstream integrations are built to accept a device as a graph input - a socket you connect - rather than a per-node dropdown you click through by hand. DeviceSelectorMultiGPU exists for exactly that case: set the device once, then pipe that single MULTIGPUDEVICE output into every node downstream that expects it, instead of repeating the same dropdown choice across a dozen separate loaders.

Think of it as a variable rather than a widget. If you're building a workflow template you plan to reuse across machines with different GPU counts, having one node own "which device" instead of scattering that decision across every loader makes the template much easier to retarget later.

How to use it

Drop it in, pick a device from the dropdown, and connect its output to whichever node in your graph exposes a matching device input. If you're only running one or two loaders, this genuinely buys you nothing beyond what their own built-in dropdowns already do - it earns its place once a graph is big enough that "wait, which GPU is the vision encoder on again?" becomes a real question, or once you're standardizing a workflow you intend to share or reuse.

How to install it

ComfyUI Manager: search ComfyUI-MultiGPU, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/pollockjj/ComfyUI-MultiGPU

then restart. No extra dependencies, nothing to download.

Common issues & troubleshooting

It does nothing if you forget to wire it up. An unconnected DeviceSelectorMultiGPU isn't an error - it just sits there, quietly not affecting anything. If you added one expecting a device change and nothing happened, check the connection first.

The device list is only as long as what your machine reports. It reflects cpu plus whatever CUDA (or other accelerator) indices ComfyUI detects at startup. On a single-GPU box, you'll only ever see cpu and one card - that's not a bug, it's an accurate reflection of your hardware.

Most of the loaders in this batch don't take a MULTIGPUDEVICE input at all. UNETLoaderMultiGPU, CLIPLoaderMultiGPU, and the rest of the core-ComfyUI-wrapping nodes each have their own built-in device dropdown and don't expose a socket for this node's output. DeviceSelectorMultiGPU is for the subset of nodes - mostly third-party integrations - built to accept a device as a connection rather than a choice; it isn't a universal override for every device setting in your graph.