MiniMax H3 Clip Bin Picker (Gallery Loader)

The Clip Bin Picker is the payoff for the whole archive system this pack builds. Where the Saver files clips away, MiniMaxClipBinPicker ("MiniMax H3 Clip Bin Picker (Gallery Loader)") lets you look at what you've got - as an actual visual gallery with preview cards - and load one shot's latent and tail frame as the context for the next segment. It turns "which take do I continue from?" into a glance at a screen instead of a spelunk through output/ guessing which clip_0004 was the keeper.

The killer detail: it outputs the full joint AV latent of the chosen historical clip, which is exactly what the Continuation Applier needs as context_latent. So the loop becomes: generate → Saver → run again → Picker picks the latest or a specific rated shot → Applier continues from it → repeat. And because you can reach back to any rated clip, not just the newest, you get branching - retake from shot 2's ending instead of being forced down a single linear chain.

Modes and the fields that matter

• project_name - which project bin to read. Projects are isolated, so this is also your "different story" selector.
• mode - the behavioral switch:
  • Auto (recommended) - if the bin is empty it behaves as a first-clip generator with zero context; once clips exist it automatically continues the latest. No rewiring between clips.
  • Force Initial - start a fresh first clip, ignoring all history in the bin.
  • Strict Chaining - must chain from a chosen/latest shot; errors out if the bin is empty. Useful for pipelines that should never silently start fresh.
• filter_rating - only consider clips at or above a star threshold (All / 3+ / 4+ / 5). If nothing matches, it falls back to all clips and warns. This is how you keep 1-star test garbage out of your continuation.
• clip_selection - latest (default) grabs the newest qualifying clip; or type a specific clip_id (e.g. clip_20260908…) to jump back to a historical shot and branch; or type a shot tag name to match by label.
• custom_clip_path - advanced: an absolute path to a clip folder anywhere on disk, for pulling in assets outside the default bin location.

Outputs and where they go

• latent - the loaded clip's joint AV latent → Continuation Applier's context_latent. The whole reason this node exists.
• tail_frame and first_frame - images you can use as a visual/conditioning reference for the next segment (or just preview).
• prompt - the original prompt stored with that clip, handy as a starting point for the next segment's text.
• clip_id - the chosen clip's ID → feed it to the next Clip Bin Saver's parent_clip_id so the lineage records that this new shot was continued from that one.

One behavior to know before it surprises you: in initial mode (Auto with an empty bin, or Force Initial) the node returns a placeholder - latent is None, the images are a placeholder card, and clip_id is the literal [INITIAL_GENERATION]. That's deliberate, and it's exactly why the pack also ships the "Safe" VAE decode nodes: a downstream VAEDecode that receives None samples would crash, while the safe variants gracefully return empty output. So if you see placeholder cards on your first run, that's the system working - don't panic and rewire everything.

The gallery itself

The pack ships a small web extension (the web/ folder) that turns the Picker into a real media browser: hover a card and the archived video plays a silent motion preview; click the ▶ MP4 badge (or double-click) for a full modal player with sound, timeline scrubbing, the stored prompt and shot parameters, and a "set as continuation source" action. None of that motion preview exists if clips were archived without save_video/ffmpeg (see the Saver page for that gotcha), but the still cards always work.

Install

Manager (search "MiniMaxH3 PrefixStream") or:

cd ComfyUI/custom_nodes
git clone https://github.com/knoic/ComfyUI-MiniMaxH3-PrefixStream.git
cd ComfyUI-MiniMaxH3-PrefixStream
pip install -r requirements.txt

Restart ComfyUI and hard-refresh the browser (Ctrl+F5) - that refresh matters here, because the gallery is frontend JS and a stale browser cache is the usual reason the interactive player doesn't appear after install. Node lives under MiniMaxH3/ClipBin. And the standing reminder that applies to every H3 workflow: the weights themselves carry the MiniMax H3 Community License territory restrictions, which this pack doesn't alter.