沐阳 H3 · 进度信号（内部）

Long video generation is slow, and "slow with a frozen UI" is how people give up on a run that's actually working fine. 沐阳 H3 · 进度信号（内部） (H3ProgressSignal) is the pack's answer: an internal node that sits in the execution chain and broadcasts live progress to the frontend as each segment actually completes. It's a passthrough in the data sense - image in, same image out - and a broadcaster in the UI sense.

The design detail worth appreciating: it's placed at key points in the expanded graph (after sampling, after drift, after the second pass, after a segment finishes), and because its function only runs when ComfyUI truly executes that point in the chain, the events are real-time rather than a one-time flash at graph-build time. It sends a myh3_progress event via ComfyUI's PromptServer.send_sync, carrying the run ID, owner ID, segment index, total segments, stage, prompt and brief. If save_preview is on, it also decodes and saves a preview frame per signal so you can eyeball what's happening without opening a video player.

Inputs

• images / audio - the segment's output; passed straight through unchanged.
• segment_index / total_segments - where we are in the run.
• stage - e.g. sampled; the panel uses it to show which phase is active.
• run_id / owner_id - which run and which panel instance this signal belongs to.
• prompt / brief - the segment's text, for the panel's context.
• save_preview - whether to write a preview frame (default on).

Outputs: images and audio, exactly what went in.

Install and the "please don't add this manually" bit

Pack install is standard: ComfyUI Manager search "ComfyUI-MiniMaxH3-Myang", or git clone https://github.com/civilcoco/ComfyUI-MiniMaxH3-Myang into custom_nodes, restart. No extra Python deps.

The description literally says "请勿手动添加" - do not add manually. If you drop one of these into a graph by hand, the practical consequence is mostly harmless (it's a passthrough, after all), but you'll be fighting the Director/LongVideo graph's own signaling. You'll meet this node when debugging: if the console shows the "H3ProgressSignal 执行" log line, the signal node genuinely executed; if it doesn't, the node was never pulled into the execution graph - the source comment calls that out as the first thing to check when progress events seem missing. Standard long-run advice also applies: ComfyUI updates change the H3 layouts this pack patches, so re-validate a two-segment run after an update before trusting a long chain.