Deeply Optimized for Low/Mid-Range GPUs (12GB VRAM)
How to use:
1: Open ComfyUI and load the JSON
2: Load the starting/reference image(s) in the big green box
3: Type out your prompt int he big green box
4: Click on "Run" to generate a 30 second image to video
Warning: Your prompt has to be detailed. If it's something simple, it will just kind of rubberband on whatever simple inputs you describe, like "A man just sitting in the chair". The more details you add, the more it stitches together a seamless transition between the three independent shots to create a cohesive 30-second video in a single runtime pass. Then again, if all you wanted to do was make a simple generation, you wouldn't need a 30-second workflow.
The only thing the three shot separates do is dictate WHERE in the 30 seconds the actions take place. So the first set of quotations takes place within ten seconds; the second set of quotations take place within 20 seconds; the third set of quotations takes place after the 20 second mark.
Reference-to-video support is built in but is disabled at the start. To enable it simply click the first button on the Faster Muter (red box) to enable up to 9 images to reference. It's that simple.
This production-grade, crash-proof ComfyUI pipeline leverages Joey Gambino's advanced H3MultishotMemorySampler subgraph infrastructure. It has been systematically tuned to shatter the native 15-second tracking boundaries of the local MiniMax H3 architecture—successfully compiling up to 30 continuous seconds of 3-shot cinematic video with synced native audio tracks in under 15 minutes on a standard 12GB NVIDIA graphics card (such as an RTX 5070).
🛠️ Required Custom Node Packages
If any node blocks present a red warning threshold on your interface canvas, navigate to your ComfyUI Manager, execute Install Missing Custom Nodes, and restart your server environment. Alternatively, verify that the following core repository directories are fully initialized and updated:
comfyui-h3-multishot(By Joey Gambino)Provides essential components:
H3MultishotMemorySampler,H3ScriptSplit,H3ClipLoaderAny.
ComfyUI-Spectrum-MiniMax-H3Provides essential components:
SpectrumApplyMiniMaxH3(Deploys advanced history parameters and signal stabilization to completely neutralize visual flickering).
ComfyUI-FreeMemoryProvides essential components:
FreeMemoryImage(Acts as the system traffic cop to violently drop massive video models from memory prior to the video save cycle).
comfyui-kjnodesProvides essential components:
PathchSageAttentionKJ(Integrates highly optimized SageAttention mathematical libraries to keep GPU memory channels open).
📥 Required Model Inventory & Destination Paths
Ensure all specific neural weights listed below are manually stored within your local file tree. Modified nomenclature or inaccurate directory placement will result in model loading exceptions.
📂 Model Directory Map
markdown
📂 ComfyUI/
└── 📂 models/
├── 📂 vae/
│ ├── 📄 minimax_h3_video_vae_fp16.safetensors
│ └── 📄 minimax_h3_audio_vae_fp32.safetensors
├── 📂 diffusion_models/
│ └── 📄 minimax_h3_fl2va_pruned_int8_convrot.safetensors
├── 📂 text_encoders/
│ └── 📄 qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
└── 📂 loras/
└── 📄 minimax_h3_fl2v_turbo_8step_v1.0_comfyui_bf16.safetensorsUse code with caution.
💾 Official Direct Asset Download Handles
Video VAE (FP16): minimax_h3_video_vae_fp16.safetensors
Audio VAE (FP32): minimax_h3_audio_vae_fp32.safetensors
Diffusion Model Architecture: minimax_h3_fl2va_pruned_int8_convrot.safetensors
Text Encoder Engine: qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
Turbo Model LoRA (8-Step Base): minimax_h3_fl2v_turbo_8step_v1.0_comfyui_bf16.safetensors
⚡ Mandatory Operational Environment Flags
To achieve absolute multi-shot stability and avoid unhandled Python environment abort failures during the long-form matrix sequence, you must explicitly configure your startup flags. Open your primary local execution script (e.g., run_nvidia_gpu.bat or initialization shell script) (or you can just open the ComfyUI desktop app and go to the Startup Args) and swap your launch command line argument array to match this configuration precisely:
bash
python main.py --disable-smart-memory --fp8_e4m3fn-text-enc --fp8_e4m3fn-unet Use code with caution.
Why these flags are mandatory:
--disable-smart-memory: Mandates a hard PyTorch memory clean immediately upon raw clip finalization, bypassing background tensor leaks.--fp8_e4m3fn-text-enc: Compresses the massive 32B text encoder into lightweight 8-bit allocation blocks, locking it comfortably inside mid-range physical memory bounds.
📐 How to Achieve the 30-Second Long-Form Configuration
The workflow relies on a fine-tuned balance between your spatial layout constraints and frame processing intervals. Apply these precise configurations on the node face to duplicate the 14-minute execution baseline:
The Core Media Input: Drop your foundational tracking frame directly into the
Load Image Here(Node 208) input bucket.The Spatial Configuration: Inside
ResolutionSelector(Node 115), anchor your values to4:3 (Standard)with a megapixel evaluation slider locked cleanly at0.4. This compact geometry drops pixel data overhead by more than 30% compared to heavy widescreen arrays, driving processing velocity forward.
Description
Upgraded from a 15-second single pass generation to a full 30 second single pass generation in under 15 minutes with high-quality full audio output and seamless stitching.
FAQ
Comments (16)
why the fuck this sample video is R-rated??? civitai - whyyyy? so the polar bear is nude??? pffff
if you consider the amount of furry content I can see why it might overdetect on nude animals :D
@escheresque oh, naughty bear!!!
i got a 130 second video before testing this changed duration to 30, does this mean we can make our videos longer im just playing about seeing what is possible
Yes, you can definitely make videos that are longer. The 10 second duration for 30 second output is the safety control tests. Meaning, any 12GB GPU with 64GB DDR5 RAM should be able to safely output 30 second videos in under 15 minutes flat without any issues. You can definitely experiment and make much longer videos, but whether it's safe or not has not been control tested for.
I will also try it with a 4060 Ti with 8GB VRAM and share the results.
how do i add loras?
You will have to add extra LoRAs in the sub-graph. Open up the image-to-video MiniMax H3 subgraph and connect additional LoRAs to the "Load LoRA" node, which is node #134. Just make sure it's not a turbo LoRA, as that is already attached.
i have Seen some saying simultaneous usage of Spectrum Node and Turbo Lora will mess up the output.
this Workflow using both, is that ok?
I have not had any issues with the output at all. The videos in the demonstration were generated using the exact workflow posted here to demonstrate stability, fluidity and continuity. If you have any issues, definitely let me know.
is this wf supposed to create a continued motion throughout? I'm asking because your prompt clearly implies scene changes between the shots. I've been using wan for a long time to create long scenes with static camera just starting any segment with the last frame of the previous one, and i'm trying to figure out how to do the same with MH3...
MiniMax H3 will sometimes choose how to adhere to the text prompts. I uploaded the various videos to show the different outcomes with the exact same prompt. You'll note that in one case it has a lingering 10 second static shot at the end -- so it CAN do long static takes without rubberbanding, but it's not always clear when it decides to rubberband or not. I've had some generations that did a solid 15 second static shot of a man talking before switching scenes. You'll have to mess about with the prompts to find what output works best for what kind of content you're trying to create.
Just add "Important: <your extra instructions>" to your prompt... MiniMax will keep it in mind as important instructions... Important: no scene change. (and more in detail description for flawless continuity. you can even prompt: Important: no scene change, no repeating scenes - be creative and fill gaps ... MiniMax will do it
With this workflow, my generations instantly went from : Will Smith eating spaghetti ... to --> 2001 : A space Odyssey ...
I gave you a thumbs up because you obviously put some work into this but I can't get it to produce usable output on my RTX3060 12gb w/ 32GB of system ram. The video generates well but the dialog sounds like Martian. It will eventually say the correct phrases from my prompt but not before wasting 5 seconds on gibberish. This happens with the included polar bear prompt and my created prompts. I am not getting any errors during generations. I have successfully generated clips using the standard MM workflows.
Yes, that is a typical issue with MiniMax H3, even some of my generations have this problem. To fix it, you can disable the turbo LoRA, which can help improve the audio stability as more steps means less gibberish. Alternatively, you can reduce the turbo steps to 8, and reduce the model strength to 0.8. This can help offset the audio gibberish MiniMax H3 frequently creates when making generations.
If I'm doing a quick gen test I'll turn on turbo mode, but if I'm doing something slightly higher quality I'll turn off turbo mode. It can take up to 25 minutes, but the output is cleaner. Another way around it -- if you want fast gen times but less gibberish -- is to explain within the prompt that there is no audio, or tell it to only generate specific types of audio, such as "Animate this object with smooth camera movement and subtle object motion. Priority: Audio only comes from environmental ambience, wind rushing, snow crunching, and breathing from the characters and animals".
Sometimes adding actual audio descriptions per each shot will create both continuity and reduce the gibberish. But also definitely tweak the settings, as the turbo LoRA oftentimes is the cause of the increased gibberish as fewer steps are used to clean up the audio generation.