MiniMax H3 Motion Director Assets

MiniMax H3 Motion Director Assets is the packer that gathers one reference group's media into a single bundle for the Director. It doesn't generate anything, doesn't sample, doesn't even have settings - it's a container, and it exists because the Director wants its references tidy.

When you're running a MiniMax H3 r2v, rv2v or fl2v shot, you feed the model reference material: identity pictures, reference video, audio. Doing that through a maze of loose IMAGE and AUDIO wires gets messy fast. This node collects whatever you connect into one assets output and hands it up the chain:

MiniMax H3 Motion Director Assets
        ↓
MiniMax H3 Motion Director Inputs
        ↓
MiniMax H3 Motion Director

How it works

The Assets node's input sockets are dynamic, and their shape is dictated by the mode set on the connected Director - which is exactly why it feels like it "changes" depending on context:

• FL2V → first_image / last_image only
• R2V → Picture 1–9, Video 1–3, Audio 1–3
• RV2V → Picture 1–9, Audio 1–3

At execution, pack() gathers whatever is connected into a single MMX_MOTION_DIR_ASSETS payload - no copying, no processing, it just holds references. The one output is that assets socket, which feeds the matching fl_assets_N, ref_assets_N or rv_assets_N socket on the Inputs node. That's the whole job.

Two practical details from the schema. The image and video slots take IMAGE tensors; the audio slots want real ComfyUI AUDIO values (the waveform dicts that a load-audio or the Director's own audio output produces). And the R2V group caps at 9 pictures, 3 videos, 3 audio per assets group - plenty for a character or scene reference, but it's a hard ceiling.

Using it

Wire it up only when your shot needs references. For a plain T2V or I2V run you can skip it entirely - I2V takes its start image directly on the Inputs node, and the Assets node is strictly for FL2V / R2V / RV2V media groups. If its sockets look missing or empty, check that you've actually connected the chain (Assets → Inputs → Director) and that the Director's mode matches the reference group you're filling.

Also: Mixed mode v1 doesn't use this node. The timeline in the Director has its own media UI, and the external group system (this node plus Inputs) only applies to standalone modes. Don't hunt for why your Assets node is idle in a Mixed project - that's by design.

Install

Same pack as the Director, so the install is shared. ComfyUI Manager: search "MiniMax H3 Motion Director", or:

cd ComfyUI/custom_nodes
git clone https://github.com/j955229/ComfyUI-MiniMax-H3-Motion-Director.git
cd ComfyUI-MiniMax-H3-Motion-Director
python -m pip install -r requirements.txt

Restart ComfyUI. It brings no model files of its own - the heavy lifting (the H3 UNET, video/audio VAEs, minimax CLIP) all lives in the Director part of the pack.

It's an unglamorous node, and that's fine. In a multi-segment H3 project, the media bag is the difference between "which wire was the character reference again?" and a reference set you can swap and reuse.