MiniMax H3 Scheduled Video Ref

Sometimes one scene needs to move like the dance clip, another like the fight clip, and the loop shouldn't replay the same performance everywhere. This node registers one 24 fps reference video - plus its optional synchronized soundtrack - under a stable @tag, scopes it to the scenes you pick, and lets the scheduler assign compact <Video N> and <Audio N> labels per scene. It's the video counterpart to the scheduled picture ref, and it pairs cleanly into the same chain.

What it does

Connect your video (reference frames at 24 fps - if your loader source runs at another rate, run it through Reference Video Prep first). Set a tag like performance (becomes @performance in prompts; not a native number). Set scenes - blank for all, or 1, 1:4, 1,3,5:8. The audio input is the optional soundtrack of this same video; it stays index-paired with its video in stock Ref2VA and gets its own audio_tag (blank derives @<video_tag>_audio). Chain with previous for stable priority order.

Then the interesting one - timeline_mode:

• restart_each_scene (default) - every active scene receives the reference from frame 0. Simple, predictable, and what the original behavior always did.
• sequential - the 24 fps source advances along the Plan timeline, repeating the same overlap as Motion Context. This is the one to pick when your reference is one long continuous performance and each scene should see the next part of it. It requires Current Shot state connected to Scheduled Ref2VA.

Outputs: schedule (chain it or feed Scheduled Ref2VA), schedule_fingerprint, and status.

Like the other scheduled nodes, this one never inserts prompt text - you write @performance in the Plan prompt and the scheduler resolves it. And the tags are aliases, not fixed native numbers: active videos renumber from <Video 1> each scene, so removing an earlier entry doesn't break your prompt.

Install and gotchas

cd ComfyUI/custom_nodes
git clone https://github.com/ethanfel/ComfyUI-MiniMaxH3-Contex-Loop.git

Restart, or install via ComfyUI Manager under "MiniMax H3 Contex Loop". No pip dependencies; a current ComfyUI with native Add Guide (PR #15439) is expected. Models aren't bundled - check the MiniMax H3 Community License territory restriction.

Where people get caught: sequential mode with no state connected to Scheduled Ref2VA. The scheduler can't know scene starts without it, so the mode simply won't behave. And don't feed this node a video at the wrong frame rate - it assumes 24 fps input; normalize first.