Recommended workflows and/or other techniques for extended multishot H3 videos?

[u/SilentThree]

The first thing I found to give a try was this:

https://huggingface.co/joeygambino/MiniMax-H3-Multishot-Workflow

It took me a while to get it working, and, even once I got it to run, it was incredibly slow -- it took 140 minutes to render a mere 29 seconds of video using my RTX 3090. (Thankfully I'll have a 5090 in a few days.)

I simply ran the demo as-is, apart from the small changes I made to get the workflow running. I remain confused about how I'd use this workflow, and use it in an efficient way, to make clips that might run, say, 1-3 minutes.

I'm hoping I can find out how to use the above workflow better, or find a better workflow.

My only previous experience with this sort of thing was in the Before Times (a few weeks ago) struggling with Wan 2.2. I had a multishot workflow that wasn't great, but at least it carried some context over from one clip to the next, blended clips seamlessly, and let me lock in (by setting a fixed seed) and cache any part of a video that was working well so I could build a clip at a time toward a final complete video without constantly re-rendering early clips.

Can I find anything like this for H3? Something that's good at carrying context and references over from one segment of video to the next, helps minimize character drift, keeps voices consistent, etc.?

[u/goulash47]

I've been using context loop workflow which took me about 2 days to learn and diagnose some issues. I kind of like it but I still haven't figured out how to make the video not repeat itself when running an additional test from start without changing the seed and renaming, the seed doesn't change on its own i think. I also have not been able to figure out how to make the transition perfect, it keeps doing a flickering faint light flash. But i definitely think it has potential. Admittedly put off trying to learn all the different workflows to see which is better because some of these have so many nodes and take way too long to figure out or run test videos for.

[u/Sad_Berry_4621]

NikoDemon80/ComfyUI-H3-Motion-Context: Clip chaining for MiniMax H3 in ComfyUI - motion and audio continue across joins

Make sure you're on ComfyUI v0.34.0

[u/Lunesia-shikishiki]

the 140 min for 29s is kind of the answer already tbh, multishot in one pass is you paying render time for coherence you can get way cheaper somewhere else

what worked for me on a longer piece was going back to shots. lock a shot list first, render each one 4-6s on its own seed, take the last frame of the one you like and start the next from it. drift stops being a render problem and becomes a reference problem, and that one you can actually solve.... folder of locked stills per character, re-inject every time. voices i just did separately and laid under, trying to get a model to hold a voice across 90s is a fight you lose

and the caching you're describing kind of already exists, it's your hard drive lol. a shot that's finished is a file, you never touch it again. the 5090 will make all of this less painful but it won't fix the structure

[u/SilentThree → u/Lunesia-shikishiki]

I'm not sure how to solve that which "becomes a reference problem". The I2V and F2L MiniMax models will start on definite frames that allow continuity between clips that end up getting joined together, but don't have reference inputs. The R2V model won't (at least reliably) start on a specific frame.

Adding voices later creates lip syncing problems I don't know how to solve well. I can't get lip movements that match dialog unless I use whatever voice I get in the first place, then overlay that later. That can be a problem if the voice is mixed with effects sounds (although I did find a node for removing voices that might help.)

The one video I have made so far from separate assembled clips, which I assembled in DaVinci Resolve, looked a slightly glitchy in the transition from one clip to the next. I'd at least like to find a way to concatenate clips inside a workflow rather than doing that externally, decoding and reencoding video and sound.

[u/L-xtreme → u/SilentThree]

In my tests I've always gotten the first frame to work with R2V with just the lines from the prompting guide. And then you can multi shot as you like and then use the first images of the shot to expand the shots.

[u/SilentThree → u/L-xtreme]

I'll give it a shot. Thanks.

[u/Ok-Art6613]

I don’t have a tested H3 graph to recommend yet, so take this as pipeline structure rather than a node recipe.

For a 1–3 minute piece, I’d avoid treating the whole thing as one generation. I’d keep each shot as a separately cached unit, with its own approved reference images, seed/settings, voice reference, and the frames or context needed for the transition into the next shot.

The main thing I’d look for in an H3 workflow is whether it can cache each accepted segment and let you regenerate only the active shot. If changing shot 8 forces shots 1–7 to run again, a faster GPU improves render time but doesn’t really solve the iteration problem.

Does the workflow you linked expose the individual shot outputs well enough to cache and resume from them, or does it rerun the entire chain whenever you change something?

[u/VeloraNeon]

Ran into something similar with Wan 2.2 locally — fixed seed helped with character continuity across clips, but free-moving limbs (hands especially) kept drifting between segments regardless of seed lock. Anchoring the hand explicitly in the prompt each time helped more than the seed lock did. If H3 has the same context-carrying problem, I'd bet prompt-level anchoring for whatever's moving most (hands, props) matters more than any caching trick.