Batch Video Streams

Batch Video Streams answers a question you only hit once you've been doing video for a while: "what if a video file has more than one picture stream?" It happens more than you'd think - a file with a main angle plus a bonus angle, or a master plus a lower-bitrate copy. Real tools solve this with batching: collect all the streams into one list, then index into it later. That's exactly what this node's shape proposes, in the ComfyUI Core Video Nodes pack (Immac/ComfyUI-CoreVideoMocks).

Two required inputs, both force-input STRINGs: video_stream_1 and video_stream_2. One output, batched_video_streams, also a STRING. The idea: wire the two streams in, and downstream the pack's Get Video Stream node picks one by index with its stream_index input. Read that pair together and you've got the whole multi-stream story - batch them, then choose one.

What actually happens

Nothing much, and that's the point. This is an RFC pack - GitHub's description is literally "A set of mock nodes for RFC purposes" - so the output is the string "Mock Batched Video Streams: ... + ...". The concatenation is real (you can see both inputs echoed back), but there's no actual batch structure behind it. It's the API shape of a batching node with the engine removed.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/Immac/ComfyUI-CoreVideoMocks

Restart ComfyUI. No pip dependencies, no models, no ffmpeg - pure Python on ComfyUI's own folder_paths, or via ComfyUI Manager ("ComfyUI Core Video Nodes").

Worth using?

As a working tool, no - same verdict as the rest of this two-star, no-footprint pack. As a way to understand the container/stream/batch mental model, it's actually fine. The author's own README notes the batch concept is borrowed from their companion project, ComfyUIGenericBatchMockNodes, because a container can legitimately hold multiple streams of the same type. If you're designing a real video pipeline, model your batch-and-index stage on this shape - it's the right one.