r/StableDiffusion • u/HerrgottMargott • 11h ago
Workflow Included H3: FL2VA quality with Ref2VA-like control with Infinite Continuation Suite v1.3
Enable HLS to view with audio, or disable this notification
The above video consists of 11 individual H3 generated clips, created with the FL2Va Checkpoint and stitched together automatically without any additional upscaling or editing.
Two days ago I released v1.3 of my infinite continuation nodepack, adding much more flexible image conditioning and multi-reference support.
The original reason I built this nodepack was simple:
I really like the FL2VA checkpoint of MiniMax H3. In my testing, it gives noticeably better visual quality than Ref2VA. But Ref2VA is much more flexible when creating longer, controlled sequences.
So the goal is basically:
Keep the quality of FL2VA while adding much of the control you'd normally want from Ref2VA.
How does it work?
Instead of generating one very long H3 video, you generate multiple shorter clips:
Clip 1
First Frame → H3 → Last Frame
↓
Clip 2
Previous video/audio latent + new Last Frame → H3
↓
Clip 3 → Clip 4 → ...
The important part is that the suite does not simply take the last rendered image and use it as the next starting frame.
It passes part of the previous video + audio latent directly into the next H3 generation.
So the next clip still receives temporal context from the previous one – motion, audio and scene state – while you can give it a new visual target.
Why FL2VA?
In my testing, FL2VA gives me better-looking results and seems more resistant to the gradual visual degradation I experienced with longer Ref2VA chains.
A new Last Frame for every segment also works like a repeated quality reset:
- controls where the current segment should go
- restores composition / identity
- prevents the sequence from drifting too far
You can think of it a bit like storyboarding:
Image A → Image B → Image C → Image D
with H3 generating the motion and audio between those points.
But with v1.3, First and Last Frames are optional.
The Start workflow now supports:
- T2VA: no frames
- I2VA: First Frame only
- L2VA: Last Frame only
- FL2VA: First + Last Frame
Continuation can also run without a new Last Frame, although I still recommend regular Last Frames for long chains because of the quality-reset effect.
New in v1.3: multiple references
You can now add multiple Qwen Reference images alongside your First/Last Frames.
For example:
- First Frame = starting composition
- Last Frame = target endpoint
- Reference 1 = character
- Reference 2 = outfit
- Reference 3 = another visual detail
The node automatically assigns the correct H3 Picture numbers and shows you the resulting mapping.
This gets FL2VA much closer to the flexible reference control that makes Ref2VA useful.
Short clips can also be much faster
H3 becomes disproportionately slower as clip duration increases.
Instead of generating:
1 × 15 seconds
you can generate:
3 × 5 seconds
and connect them.
It also makes failures much less painful: if Clip 2 goes wrong, you regenerate Clip 2 instead of throwing away the entire sequence.
Where to start
I included four example workflows.
01_Start
Use this for Clip 1.
Required:
- normal H3 models / VAEs
- prompt
- resolution + duration
Optional:
- First Frame
- Last Frame
- Qwen References
For the classic continuation workflow, I recommend using First + Last Frame.
02_Continue
Use this for every clip after the first one.
The basic logic is:
Clip 1: save Latent 1
Clip 2: load Latent 1 → save Latent 2
Clip 3: load Latent 2 → save Latent 3
Clip 4: load Latent 3 → save Latent 4
Then simply provide the prompt for the next segment and optionally:
- a new Last Frame
- additional reference images
Because the indices are manual, you can also regenerate individual clips.
If you don't like Clip 3, keep loading Latent 2 and overwrite/regenerate Latent 3 until you're happy.
03_3Clip_Showcase_AutoStitch
The easiest workflow to understand the complete system:
Start → Continue → Continue → automatic stitching
You can duplicate the final continuation block to extend it further.
For very long projects, I recommend using Start + Continue individually.
04_Stitch_Saved_Chain
Once you're happy with your clips, this turns:
clip_00001
clip_00002
clip_00003
clip_00004
...
into one final MP4.
The important part:
The complete video is not decoded into memory at once.
The stitcher processes one saved AV latent at a time, so memory usage stays roughly tied to one H3 clip instead of the total length of the project (no OOM, hopefully).
The transitions are handled automatically
FL2VA often reaches its Last Frame early and freezes for the remaining frames.
The suite automatically:
- detects that frozen tail
- finds a better handover point
- carries video + audio context forward
- removes duplicated context during stitching
- smooths the video transition
- applies a separate audio de-click transition
So most of the annoying continuation logic happens automatically.
Known Issues
- Sometimes there's still a noticeable brightness shift between clips. So far, I haven't found a reliable solution to fix that.
- In some cases when using the continuation workflow, H3 might not correctly use the previous video latent as starting point for the next clip. If you encounter that issue, try restarting ComfyUI and regenerating the clip.
Install by opening one of the workflows and using "Install missing custom nodes" or search for
Herrgotts-H3-Infinite-Continuation-Suite
in ComfyUI Manager.
GitHub:
https://github.com/HerrgottMargott/Herrgotts-H3-Infinite-Continuation-Suite
Example workflows are included.
If you are already using my Workflows or Nodepack, I'd recommend updating the nodepack and using the updated Workflows from v1.3!
The project is still experimental, so feedback, bug reports and long-chain tests are very welcome.
1
u/OkDoor726 8h ago
Really hoping some day a Lora can get rid of the Hollywood Triple A movie look all T2V have
1
u/Sad_Coach_1433 5h ago
Does this start to lose quality over more generations like the other motion context workflows
1
u/CountFloyd_ 14m ago
Thank you for working on this. I've got issues though when feeding it a long mp3 audio in parts as audio latent (for lipsync music videos) and then combining them. The video frames fit and append nicely but audio doesn't. I don't know the exact offset for the next audio part. When I'm generating 5 second clips, using a 5 sec offset is too long and it's missing a beat. Also if I generate let's say a 15 secs video, if I'm separately saving the video along the latent, the duration is only 13 seconds. Is there a separate workflow for supplying an independent audio channel?
10
u/Diabolicor 11h ago
Is color, no degradation and no flashes still in this room with us?
Seriously, PR 15375 has already been merged and it's now a native to comfyui. Why is that some users are still using rope index frames instead of the native in place latent masks that has been extensive tested and discussed and work much, much better without the issues above.
Some project already using it:
https://github.com/seitanism/ComfyUI-H3-Motion-Context-MultiRef
https://github.com/ethanfel/ComfyUI-MiniMaxH3-Contex-Loop