Load Latent Batch Pipe MXD

The single-latent loader is great until you realize you have forty of them. That's when you reach for Load Latent Batch Pipe MXD: it loads every .latent in a folder at once, each with its own .cond.pt sidecar pulled in, and hands the whole set back as a list of MXD_LATENT_PIPEs. Feed that into an unpack node and you've got a batch of WAN 2.2 I2V jobs ready to re-sample in one pass.

How it works

Where Load Latent Pipe MXD takes a dropdown and loads one file, this one takes a subfolder and sweeps everything in it. For each .latent it finds, it reads the matching .cond.pt sidecar to recover that run's conditioning, steps, cfg, sampler, scheduler and shift, and bundles them into a pipe. The output is marked as a list (OUTPUT_IS_LIST), so one connection carries all the pipes - a downstream unpack node, or a per-item processor, sees them as a batch rather than a single item. It's the natural companion to a save step that wrote a folder of finished latents: load folder → unpack → resample or upscale every one.

Inputs

Just one that matters: subfolder - the folder under ComfyUI/input/latents to scan. It's a dropdown populated from the latents directory, so you don't type paths by hand. Because the whole job is "give me everything in here," there's no per-file picker and no run_folder toggle - batching is the point.

Wiring it in

The latent_pipe list output goes to an Unpack Latent Pipe MXD, which splits each pipe back into samples, positive, negative, shift and the sampler settings. From there the batch flows through your KSampler branch the same way any batch would. The one-wire pipe format means you can swap between this node and the single loader without re-wiring the downstream graph - change one node, keep everything else.

Installing

ComfyUI Manager → search "Maxed Out" → install, then restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Maxed-Out-99/ComfyUI-MaxedOut.git

No pip dependencies, no model downloads.

Common issues

Two things bite people. First, like the single loader, this round-trips latents this pack wrote - a folder of foreign .latent files without sidecars loads as pipes with empty conditioning and default settings, which is probably not what you wanted. Second, mind the memory: loading a folder of 1080p WAN latents materializes all of them at once, so a huge folder can spike VRAM. If you're running into OOM, split the folder into smaller batches rather than dumping everything in one pass. And if your dropdown doesn't show a subfolder you just created, restart or refresh - the list is populated when the workflow loads.