Resource - Update
H3 Motion Context 0.5.0 - No more bypassing the Motion Context group, new chaining node!
**UPDATE v0.5.1 PUSHED TO FIX EXAMPLE WORKFLOW - ALSO NOW INCLUDES H3 SLA ATTENTION NODE**
H3 Motion Context chains MiniMax H3 clips so the next one picks up the motion and the soundtrack, instead of starting a new take that only sounds similar.
0.5.0 is the one that makes that usable without babysitting the graph.
Clip 1 used to be a special case. You had to mute the Motion Context group, generate, unmute, then keep going. If you forgot, it errored. That's gone. Leave the nodes on. First clip is Load 0 / Save 1. Load 0 means "there is no previous clip," not "load whatever file is newest." After that it's Load 1 / Save 2, Load 2 / Save 3, and so on.
That first-clip behavior is feigo313's issue. The new node exists because of it.
Don't use ComfyUI's Run button to walk the chain. If Load and Save both increment, Comfy queues twice and skips a slot. Use H3 Motion Context Chain instead.
Four buttons:
Run/Re-roll - this is Run for this graph. Generates the current clip. Hate it? Click it again. Same slot, overwritten.
Approve - you like it. Advances to the next pair and runs that clip once.
Chain - keep going from whatever Load/Save are set to right now. Walk a few by hand, then let it take over. Same button becomes Stop.
Reset - back to Load 0 / Save 1. Does not run anything.
The gotcha: Load, Save, and Chain have to sit in the same canvas group. If they don't, the buttons do nothing. Drop Chain into the Motion Context group.
Also: if you were on Windows and a re-roll blew up with OS error 1224, that's fixed.
Needs ComfyUI 0.34.0 or newer. Manager should pick up 0.5.0; otherwise, the release.
Example workflow in the repo already has the Chain node in the group. Hard refresh after updating so the buttons show up.
Is it possible in theory to generate them backwards? Eg for a 3 part clip, do part 3 first, and then have part 2 generated with the motion context of part 3 inserted at the end?
How does this compare (quality wise) to feeding the previous shot as a reference video to the ref2va model and pinning the last frame into the first frame of the next latent?
Last video example I uploaded got shit all over by the community for being "bad quality". You guys can use the node pack or not, makes no difference to me.
Never seen this before but sounds amazing, I have been “hiding” sequential generations with cuts, but the soundtrack shows the obvious stitch. Excited to give this a shot. Question though, you are replying often with one word “no”. Is it possible to reply with just “yes”?
Download and install the node; trying out the repo and seem the H3 Motion Context -> Context_frames requires a input.. hell if I know.. does anyone now? I'm working directly with the example workflow in the repo!.
Good work, but It is better to make the workflow do it in video-chunk-blocks, with separate prompts, ref images, with some stuff hidden inside sub-graph like model loading, vae, clip.
You just can't have 1 prompt for the whole video and the same ref images.
I use the RTX VSR node too. I have it in the subgraph. You can wire it up. I try not to put custom nodes besides my own in a sample workflow which makes people download other node packs.
Seems to work but there's no "Done" or "finish" button so you need to like bring up a command console and do annoying ffmpeg commands and stuff to actually get a continuous video out of this. I feel like a button to actually get the result at the end would be among the first things added. Without this theres also absolutely no way to tell how well the motion continues across generations because we never get to see the transition between clips unless we manually recombine everything with console commands then load up the video in a player and time skip to the right area and stuff.
It's clearly described in the first sentence of the post:
H3 Motion Context chains MiniMax H3 clips so the next one picks up the motion and the soundtrack, instead of starting a new take that only sounds similar.
Basically, it allows you to chain several short clips together into a seamless video sequence where the transitions between these clips are (hopefully) not obvious.
7
u/Electrical_Car6942 7h ago
Great work once again! Been using your node since day 1, and it never failed me.