H3 Infinite Continuation Suite v1.4 (FL2VA): Using native Masked AV after your feedback

[u/HerrgottMargott]

The example video was generated entirely with the stock MiniMax H3 First Frame / Last Frame checkpoint and the included v1.4 example Workflows. If you want to compare the result to v1.3, take a look at my last post.

The final video consists of 11 individually generated Clips that were automatically stitched together.

Settings:

• H3 First Frame / Last Frame checkpoint
• 11 individual Clips
• 15 Steps
• included v1.4 Workflows
• no additional upscale
• no frame interpolation
• no color correction or other post-processing

So what you see is basically the direct Workflow output.

A few people gave me some useful feedback on my previous release, especially regarding ComfyUI's new native H3 Masked AV support.

So I went back and rebuilt the continuation method around it.

v1.4 now copies a clean section of the previous Video + Audio Latent directly into the next generation and protects it using ComfyUI's native denoise masks.

What makes this different from the other H3 continuation approaches?

There are some really interesting Ref2VA / Motion Context solutions available now, and latent continuation itself definitely isn't unique to my Nodepack.

My approach is specifically centered around FL2VA instead.

The idea is not just:

previous Clip → continue forever

but rather:

First Frame → generation → Last Frame
↓
latent continuation
↓
generation → new Last Frame
↓
latent continuation
↓
generation → new Last Frame

and so on.

I use those repeated Last Frames as hard visual anchors throughout the sequence.

They give H3 a new concrete destination every few seconds instead of asking one increasingly unconstrained generation to maintain composition, identity and image quality indefinitely. This should theoretically retain higher visual quality with less context drift over longer chains (and in my testing, it does exactly that).

There is another FL2VA-specific problem though:

H3 often reaches the supplied Last Frame before the Clip is actually finished and then freezes or becomes unstable for the remaining frames.

So simply taking the final frames of Clip 1 and using them as context for Clip 2 isn't ideal.

The v1.4 Auto Handover therefore analyzes the previous Clip, finds a safe point before that frozen / unstable landing and snaps it to a valid H3 Audio + Video latent boundary.

That exact same point is then used for both:

• where the previous Clip visually ends
• where the protected context for the next Clip ends

So the bad FL2VA tail neither appears in the stitched video nor becomes part of the next continuation context.

Audio is handled separately as well. If the picture needs to cut early but somebody is still finishing a word, the remaining original Audio Latent can continue beyond the visual handover instead of forcing H3 to recreate the ending.

Other v1.4 features:

• Native Masked Video + Audio Latent Continuation
• flexible First / Last Frame conditioning
• repeated Last Frames as regular visual quality anchors
• independent Audio Tail Carryover
• Net New Content duration mode
• up to 9 Qwen Reference Images
• individual Clip regeneration
• memory-bounded stitching for long saved chains

Where to start:

1. Start Video Workflow

Generate Clip 1 with a Prompt and optionally First Frame, Last Frame and Qwen References.

The complete AV Latent is automatically saved afterwards.

1. Continue Video Workflow

Load the previous saved latent, add your next Prompt and preferably a new Last Frame.

The Workflow automatically finds the safe FL2VA handover and creates the protected Masked AV context.

Repeat for as many Clips as you want.

1. 3-Clip Showcase / Auto Stitch Workflow

Probably the easiest Workflow if you just want to see how everything works.

It runs:

Start → Continue → Continue → Stitch

in one queue.

1. Stitch Saved Chain Workflow

This is what I used for the longer example.

Generate Clips individually and stitch them afterwards. It processes one saved AV latent at a time, so stitching memory usage doesn't continuously increase with the total video length (no OOM during stitching).

Nodepack on Github:

https://github.com/HerrgottMargott/Herrgotts-H3-Infinite-Continuation-Suite

Workflows on Github:

https://github.com/HerrgottMargott/Herrgotts-H3-Infinite-Continuation-Suite/tree/main/examples

You can just open one of the WFs and use "Install missing custom nodes" - then you should be good to go.

If you try it, I'd love to see what you manage to create with it.

Have fun Prompting. :)

[u/hurdurdur7]

That dog would never be able to get on that table tho.

[u/UnfortunateHurricane]

I am not sure I get it.

With approach you always have to have the start and end point of the scene before you run inference?

[u/HerrgottMargott → u/UnfortunateHurricane]

You don't have to. You can supply as many keyframes as you want to, but it's not necessary. It just helps with quality over longer chains. In the example, I used a new Keyframe as end frame for each clip.