Image Queue Processor Plus

Plus is aidec's "everything in one box" take on the image queue. The author announced it in the README as the node that would fold Image Queue Processor and the directory loader together to simplify the graph a little - and here it is. If the other queue nodes felt like they needed too much wiring around them, this is the one that tries to be self-sufficient.

It's also the most feature-loaded node in the pack, and correspondingly the newest and least battle-tested. You get a loop cap, an on/off loop switch, an optional second image lane, filename and path passthrough, an md5 hash of the current image, and hooks into the pack's Data Temp store for accumulating results across iterations. That's a lot of surface for a solo hobby pack, so treat the extra knobs as "handy if you need them" rather than load-bearing.

How it works

Same serial-queue heart as the rest of the pack: a server-side counter emits the image at current_index, advances, and - being an output node with trigger_next on - re-queues the workflow to march through the batch on its own. What Plus adds is control over how far it marches. max_index caps the loop so you can process just the first N; enable_loop turns the auto-walk on or off entirely, so you can also use it as a plain index-picker.

The inputs that matter

• images - the batch to walk.
• start_index / max_index - the window. Start at 0, stop at max_index (default 10). This is how you run a slice instead of the whole thing.
• trigger_next - the auto-advance.
• enable_loop - on to iterate, off to just grab one index.
• additional_image (optional) - a second image lane carried alongside the main one, handy when your pipeline needs a paired reference.
• filenames / file_paths (optional) - pass in the name/path strings (say, from Load Images From Dir Batch) so the node can echo the right filename per index.
• data_tmp_var / use_data_tmp (optional) - wire it into the Data Temp store to stash results as the loop runs.

Outputs cover image, current_index, total, completed, status, plus filename, file_path, and md5 for the current image. The md5 is the unusual one - useful if you're deduping or logging exactly which file produced which result.

Installing it

cd ComfyUI/custom_nodes && git clone https://github.com/aidec/Comfyui_TextBatch_aidec, then restart ComfyUI (or ComfyUI Manager → Install via Git URL). No models, no heavy dependencies. Category: TextBatch.

Where people get burned

• max_index will surprise you. It defaults to 10, so if you point Plus at a 300-image folder and don't touch it, you'll get 10 images and wonder where the rest went. Set it to your real count (or wire it from a counter).
• The extra inputs are optional for a reason. The Data Temp integration and the second image lane are experimental conveniences - get the basic loop working first, then add them, so you can tell what broke.
• Pack-wide quirks still apply. First queue may fire once (queue again), start_index doesn't self-reset, and you should keep to a single ComfyUI tab so the shared counter doesn't get scrambled.

If you specifically want low-memory folder img2img and nothing fancy, Image Queue Processor Pro is the simpler, more proven pick. Plus is for when you actually want the loop cap, the paired lane, or the result accumulation it bolts on.