MiniMax H3 Director Groups Combine

If the Director Group nodes are each shot in your scene, MiniMax H3 Director Groups Combine is the clipboard that holds them in order. It's the smallest node in this pack and possibly the easiest to take for granted: several group inputs in, one ordered groups list out, ready to feed the Director. One Group feeding straight into the Director doesn't need it. Two or more do.

What it actually does

The node has exactly one input family - groups, an Autogrow set of slots - and one output, groups (typed MMX_DIR_GROUP). No required inputs at all, no widgets to set, no prompt, no duration. You connect each Director Group's group output into a slot; when you fill the last empty slot, another one appears, up to the node's limit. Connect a Group node's output, and it grows.

Order is the whole game here. Slots are consumed in connection order - group_0, group_1, and so on - and the output preserves that sequence. That means the order you wire the slots is the order your shots play, so wire deliberately: your opening shot belongs on the first slot, not whichever one happened to be handy.

Empty slots are silently skipped. That's a feature when you're iterating (leave a slot unplugged and it just drops out of the run), and it means you don't have to clean up a half-built Combine before queueing.

The one rule that bites

Don't mix families. The Combine refuses to merge Image-to-Video groups (the t2v/i2v/fl2v packer) with Reference-to-Video groups in one list - it raises a clear error rather than quietly misbehaving. If you're building a scene that uses both kinds of shots, you run two Combines and feed them to the Director's two sockets (i2v_groups for one, r2v_groups for the other), not one mash-up list. And a connected-but-empty Combine - nothing wired at all - errors too, so keep the ones you care about fed.

Wiring it into the Director

The flow reads top to bottom:

[Group: shot 1] --group--> Combine --groups--> Director.i2v_groups
[Group: shot 2] --group-----^                        (or r2v_groups)

Once the list lands on the Director, the external groups take priority over the Director's built-in UI cards for execution - the cards gray out, and "select run" lets you pick which group indices actually sample. Match the socket to the family: i2v-family groups → i2v_groups with task_type t2v/i2v/fl2v; r2v-family groups → r2v_groups with task_type r2v (or the v2v/rv2v reference modes). Don't feed both sockets at once.

That's the whole node. If you're stuck, it's almost never Combine's fault - check the upstream Groups have the media you think they do (a <Picture 1> tag in the prompt is meaningless if the slot is empty), and check the Director is actually receiving the list. Combine just sorts the paperwork; the Director does the expensive part.