Batch Sequence Plus (mtb)

This is Batch Sequence with an actual video editor's transition drawer bolted on. Where the plain version hard-cuts between image batches, Batch Sequence Plus blends the join - crossfades, slides, wipes - so two separately-rendered segments read as one continuous shot instead of a jump cut. It's part of MTB Nodes' mtb/batch family, melMass's toolbox for building ComfyUI graphs that operate frame-by-frame rather than image-by-image.

What it's actually for

If you've rendered a video in pieces - different prompts, different seeds, maybe different models per segment - stitching them with a hard cut is fine when the content changes are meant to read as a scene change. It's jarring when they're not. Crossfade smooths a transition where the content is similar enough that a dissolve feels natural (a face turning, a scene continuing). The slide and wipe variants read more like a deliberate stylistic cut - useful for montage-style edits or anything you want to feel intentionally "edited" rather than seamless.

The inputs and output that matter

• transition - 12 options: none (a hard cut, same as the plain Batch Sequence), crossfade, four slide_* directions, four wipe_* directions, and two band_wipe variants (horizontal/vertical). Start with crossfade if you're not sure - it's the least likely to look like an effect.
• overlap_frames (0–120, default 0) - how many frames the transition blends over. At 0, transition has nothing to work with regardless of which type you picked, so this is the setting that actually turns the effect on. Something in the 8–15 frame range at typical animation frame rates reads as a smooth cut without dragging on.
• reverse - plays the whole assembled, transitioned sequence backwards.

Like its sibling, this node doesn't declare a fixed list of image-batch inputs in its schema - it uses the same dynamic-inputs pattern the pack's Debug node names directly, where wiring in another batch grows a new input slot on the node automatically.

Output is a single IMAGE - the joined, transitioned batch.

Installing it

ComfyUI Manager: search MTB Nodes, install, restart. By hand:

cd ComfyUI/custom_nodes
git clone https://github.com/melMass/comfy_mtb

then restart ComfyUI. Pure image-processing math - no model weights to fetch.

Common issues

overlap_frames set higher than the shortest of your two adjacent segments doesn't have enough real frames to blend from - keep it comfortably under the length of your shortest input batch. And as with plain Batch Sequence, feeding it mismatched resolutions between segments will fail rather than auto-resize; match sizes upstream first.

The general MTB gotcha applies here too: the pack logs [comfy_mtb] Some nodes (N) could not be loaded at startup rather than crashing outright when something fails to import, with a pointer to http://127.0.0.1:8188/mtb - confirmed by other users' real install logs. If this node is missing after installing the pack, check that line before reinstalling.