沐阳 H3 · 导演台动作源（内部）

沐阳 H3 · 导演台动作源（内部） (H3DirectorActionSource) is one of those internal nodes the README tells you not to wire by hand - "nodes marked 内部 are managed by the Director or long-video expansion and normally do not need manual wiring" - but if you're going to understand the Director's motion-transfer path, this is the piece that does the heavy lifting. It's the node that turns a single action reference video into a full per-segment plan.

Here's the job. In the Director's storyboard, a motion-transfer shot has one action video. This node loads it, and from the card's timeline_json it computes how that video splits across your segments: given segment_seconds (default 10) and overlap_frames (default 22), it builds the plan_json that says how many segments there are, how many frames each gets, and how they overlap on H3's time grid. Alongside the plan it hands back the video's frames and its soundtrack, already sliced to the action-source role - the 动作参考视频 and 动作参考音频 outputs that the per-segment pipeline then carves up further.

Inputs

• timeline_json - the Director's storyboard timeline; this is where the action-video asset lives.
• fallback_prompt - used when a shot needs a prompt and none is provided.
• segment_seconds - target per-segment duration (default 10, bounded 4–20 in the pack's segment math).
• overlap_frames - the continuity overlap, default 22, same number you see everywhere else in the pack.
• start_segment - resume support: 1 means run the whole thing; on a resume you set the first un-generated segment.

Outputs: plan_json, 动作参考视频 (IMAGE), and 动作参考音频 (AUDIO).

One rule worth knowing because it's the failure mode people hit: the node demands exactly one action video on the card. Zero videos and it errors; two videos and it errors. The Director's contract is one action source per motion-transfer shot, and this node enforces it loudly.

Install and context

Same pack, same install: ComfyUI Manager search "ComfyUI-MiniMaxH3-Myang", or git clone https://github.com/civilcoco/ComfyUI-MiniMaxH3-Myang into custom_nodes, restart. No extra Python dependencies.

Treat this as a "know what it does, don't build your graph around it" node. If you're debugging the Director's motion transfer and the plan looks wrong or the reference isn't what you expect, this is where the slicing starts. And the pack-wide reminder stands: H3's local weights are licensed territory-restrictively (US/EU/UK/South Korea excluded), so check terms before you commit a project to them.