# MiniMax H3 Cases & Guides — Complete Case and Tutorial Index Generated from data/cases.json and data/tutorial-guides.json. Total: 2508 cases and 25 tutorials. Complete verbatim public Prompts: 718. ## Tutorials ### ComfyUI zero to your first H3 video with audio - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/official-deployment/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/official-deployment/ - Track: run - Depth: deep - Status: active - Category: comfyui - Best for: First-time NVIDIA users who want a guided local MiniMax H3 run instead of reverse-engineering a node graph. - Goal: Start with a clean ComfyUI setup, place all five model files correctly, and render a playable T2VA MP4 with picture and synchronized audio. - Hardware: Windows or Linux with an NVIDIA GPU and ample disk space. Start at the template preview size when VRAM is limited instead of jumping to 1344×768. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: beginner - Estimated time: not specified - Applicable versions: ComfyUI 0.30+ · native H3 T2V template - Official T2V workflow JSON: https://github.com/Comfy-Org/workflow_templates/blob/main/templates/video_minimax_h3_t2v.json - Official Windows Desktop installation: https://docs.comfy.org/installation/desktop/windows - Linux / manual installation and Python environment: https://docs.comfy.org/installation/manual_install - Model files and folders: https://huggingface.co/Comfy-Org/MiniMax-H3 - Official outputs and prompt examples: https://huggingface.co/MiniMaxAI/MiniMax-H3/blob/main/docs/VIDEO_PROMPT_WRITING_GUIDE_base_en.md - Original source: https://docs.comfy.org/tutorials/video/minimax/minimax-h3 - Start here: 1. Install or update ComfyUI. Windows beginners should follow the linked official Desktop installer and launch the app after NVIDIA dependencies finish. For Linux/manual installs, first follow the manual guide to clone ComfyUI, activate its isolated Python environment and install the matching CUDA PyTorch build. Only that route uses the pip and main.py commands below, from the ComfyUI folder containing requirements.txt. Confirm the UI opens without CUDA errors before continuing. 2. Open Template Library → Video → MiniMax H3 T2V. Use the model-download popup when available; preserve the exact filenames for manual downloads. 3. Place minimax_h3_fl2va_pruned_int8_convrot.safetensors in ComfyUI/models/diffusion_models/. T2V and I2V use FL2VA; only R2V switches to Ref2VA weights. 4. Place qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors in ComfyUI/models/text_encoders/. Put both the video and audio VAEs in ComfyUI/models/vae/. A silent render is not a successful audio-video setup. 5. Place minimax_h3_fl2v_turbo_8step_v1.0_comfyui_bf16.safetensors in ComfyUI/models/loras/. It powers the optional turbo_mode; keep Turbo off and use the default 20 steps for the first baseline. 6. Restart ComfyUI or refresh the model list. Confirm every Loader finds the diffusion model, text encoder, both VAEs, and LoRA. Fix null, undefined, or red nodes before queuing. 7. Render a short clip at the template preview size, 16:9, and multiple=32. Describe the scene first, then shots and camera, then dialogue, effects, or music. Add no custom nodes or stacked accelerators yet. 8. Queue the graph and wait through VAE decode and MP4 assembly. Open the file and verify picture, duration, audio, and event or lip synchronization. Save this untouched graph as the baseline. 9. After the baseline passes, move to the native 1344×768 canvas or 0.98 MP in Resolution Selector. Do not choose 1.0 MP because it produces 1376×768, above the model area cap. 10. For first/last frames, connect first_frame or last_frame in the same FL2VA graph. For identity, style, motion, camera, or voice references, open the R2V template and switch to Ref2VA weights instead of mixing model families. - Commands: - python --version - python -m pip install -r requirements.txt - python main.py - ComfyUI/models/diffusion_models/minimax_h3_fl2va_pruned_int8_convrot.safetensors - ComfyUI/models/text_encoders/qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors - ComfyUI/models/vae/minimax_h3_video_vae_fp16.safetensors - ComfyUI/models/vae/minimax_h3_audio_vae_fp32.safetensors - ComfyUI/models/loras/minimax_h3_fl2v_turbo_8step_v1.0_comfyui_bf16.safetensors - Expected result: Render a short MP4 with synchronized audio that opens in a regular player, and save an untouched baseline workflow before adding third-party nodes. - Troubleshooting: - A model is missing from a Loader: Check the original filename and folder for all five files, refresh the model list, and fully restart ComfyUI. - The output is silent or out of sync: Confirm the audio VAE is loaded and reproduce a short 20-step render without third-party nodes. ### Turbo + lower VRAM: reduce 20 steps to 4–8 - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/nvidia-comfyui/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/nvidia-comfyui/ - Track: run - Depth: deep - Status: active - Category: acceleration - Best for: NVIDIA users who can already render with the official H3 graph but need faster iteration or lower VRAM use. - Goal: Add the community Turbo nodes to a working H3 ComfyUI baseline, render usable clips at 6–8 steps, and follow a controlled fallback order when VRAM runs out. - Hardware: An NVIDIA GPU. Record native peak VRAM and time first. Low-VRAM mode is a fallback, not the default quality setting. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: intermediate - Estimated time: not specified - Applicable versions: Larryvrh H3 Turbo · v4 step600 EMA · Native template Turbo and plugin Turbo use different setup paths - Turbo plugin and workflow instructions: https://github.com/Larryvrh/ComfyUI-MiniMax-H3-Turbo/tree/main/example_workflows - Turbo LoRA weights: https://huggingface.co/larryvrh/MiniMax-H3-Turbo-Lora - Watch the chaptered video tutorial: https://www.youtube.com/watch?v=G3YHSvXZP_g - Official native Turbo reference: https://docs.comfy.org/tutorials/video/minimax/minimax-h3 - Community usage: A viewer reports that previews help decide whether a render is worth waiting for. This is usability feedback, not a measured speed multiplier. https://www.youtube.com/watch?v=G3YHSvXZP_g&lc=UgyTbfwka0nzc96pWiZ4AaABAg - Community praise: Comments praise the workflow explanations and collected resources. Comments saying they plan to try it are not successful reproductions. https://www.youtube.com/watch?v=G3YHSvXZP_g&lc=UgzY0sgAQO3qR4zQHmN4AaABAg - Community issue: A viewer reports generation stuck at 0%, without hardware, logs or versions. No author resolution was visible for that comment; it does not establish a cause or universal compatibility. https://www.youtube.com/watch?v=G3YHSvXZP_g&lc=UgwQnHAYkAeXotwLTYB4AaABAg - Community fix: Issue #27 reports a tensor-size mismatch with ComfyUI 0.31.1, RTX 5090 and pruned Ref2VA plus reference audio. A contributor points to merged PR #16; the issue remains open. Update and check a short clip before combining references or continuation. https://github.com/Larryvrh/ComfyUI-MiniMax-H3-Turbo/issues/27 - Original source: https://github.com/Larryvrh/ComfyUI-MiniMax-H3-Turbo - Start here: 1. Run the native 20-step graph once and record total time, peak VRAM, fine detail, fast motion, and audio quality. This render is the only valid baseline. 2. Install MiniMax-H3 Turbo through ComfyUI-Manager, or clone it under ComfyUI/custom_nodes/. Fully restart ComfyUI and confirm there is no import error. 3. Place minimax_h3_turbo_v4_step600_ema.safetensors in ComfyUI/models/loras/. Prefer v4-600 for most work; compare the older v1-850 only when 4-step heavy motion shows trailing or smear. 4. Start from the official T2V or I2V graph. Insert MiniMax-H3 Turbo LoRA between Load Diffusion Model and SamplerCustomAdvanced, then select the downloaded checkpoint. 5. Feed SamplerCustomAdvanced from MiniMax-H3 Turbo Sampler and set BasicScheduler to simple. Keep conditioning, both VAE decoders, and audio output unchanged. 6. Start at 8 steps and strength=1.0, then test 6 steps. Use 4 steps for composition previews or strict budgets rather than assuming it is final quality. 7. Render again with the exact same seed, prompt, media, resolution, and duration. Compare time, face and hand detail, fast-motion trails, audio quality, and sync. Turbo must be the only changed variable. 8. If VRAM runs out, reduce preview resolution or duration first, disable nonessential previews or nodes second, and enable low_vram last. Low-VRAM mode lowers peak use but can soften quantized output. 9. For smear or blur on a specific clip, test strength around 1.05–1.2. For oversharp grain, test about 0.8–0.95. Change only one parameter per run. 10. Keep separate native and Turbo workflow files. Use Turbo for shot selection and bulk previews, then compare important finals against the native 20-step baseline. - Commands: - cd ComfyUI/custom_nodes - git clone https://github.com/larryvrh/ComfyUI-MiniMax-H3-Turbo - git -C ComfyUI-MiniMax-H3-Turbo pull - Expected result: Render a 6–8 step video with audio from the same seed, input, resolution, and duration, with a native 20-step comparison saved beside it. - Troubleshooting: - The new nodes do not appear in search: Confirm the repository is under custom_nodes, inspect startup import errors, and fully restart. - Four-step output smears or loses audio quality: Return to eight steps at strength 1.0 and remove Spectrum or EasyCache from the comparison. - Reference audio triggers a tensor-size mismatch: Check Issue #27 and merged PR #16, update the Turbo nodes and fully restart. If it persists, return to the official reference workflow without Turbo; low_vram is not an established fix. - Out of VRAM: generation stops: Reduce resolution and frame count, then enable low_vram as described in the Turbo README. Merging LoRA into a quantized base can soften output; compare against the native baseline. ### Run H3 on Mac from zero with pure C + Metal - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/mac-native/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/mac-native/ - Track: run - Depth: deep - Status: active - Category: getting-started - Best for: Apple Silicon users who can use Terminal and do not want to build an NVIDIA or ComfyUI stack. - Goal: Without Python, PyTorch, or ComfyUI, compile h3.c on Apple Silicon, validate the model, and generate a first MP4 with audio. - Hardware: Apple Silicon Mac. The author’s resident BF16 DiT uses about 37 GiB, plus headroom for text encoding, VAEs and macOS. Use the README’s SSD-streaming path if memory is tight; DiT storage is not the minimum total system RAM. Start at 512×512 and 22 frames. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: intermediate - Estimated time: not specified - Applicable versions: h3.c README · 2026-09-06 · Apple Silicon · FFmpeg / FFprobe - h3.c installation, commands and examples: https://github.com/antirez/h3.c - Original weights and model documentation: https://huggingface.co/MiniMaxAI/MiniMax-H3 - Original source: https://github.com/antirez/h3.c - Start here: 1. Run xcode-select --install in Terminal; macOS will say when it is already present. Install FFmpeg with Homebrew, then verify both ffmpeg and ffprobe. 2. Clone antirez/h3.c and enter the repository. Keep the code separate from the weight files; this guide expects the complete model at ./MiniMax-H3. 3. Download the complete MiniMaxAI/MiniMax-H3 Hugging Face snapshot into ./MiniMax-H3. Preserve filenames and do not download only the apparent main checkpoint. 4. Run make -j8, then create outputs. If compilation fails, confirm the active compiler is Apple clang and repair Command Line Tools before changing build flags. 5. Run ./h3 --info -d ./MiniMax-H3. It validates model layout and prints the Metal device without mapping every weight or generating media. Resolve missing files here. 6. Run the balanced 512×512, 22-frame, 20-step example first. The first invocation pays model-loading and filesystem-cache costs, so its total time is not a stable benchmark. 7. Add --show only in a terminal that supports image previews; omit it under memory pressure. Use --profile for phase timings and do not treat results from another chip as a guarantee. 8. Confirm outputs/fox-fast.mp4 plays with audio. Repeat the same command; the second run is a more useful performance comparison. 9. For interactive work, run ./h3 -d ./MiniMax-H3 --width 512 --height 512 --steps 6. Use !status, !seed random, !seconds 2, and !save output.mp4 to control the session. 10. Use !first opening.png and !last ending.png for boundary frames, or !ref-image person.png for a general reference. Ref2VA references cannot be mixed with !first or !last; clear the old mode first. - Commands: - xcode-select --install - brew install ffmpeg - git clone https://github.com/antirez/h3.c && cd h3.c - brew install hf - hf --help - hf download MiniMaxAI/MiniMax-H3 --local-dir MiniMax-H3 - make -j8 && mkdir -p outputs - ./h3 --info -d ./MiniMax-H3 - ./h3 --profile -d ./MiniMax-H3 -p "A red fox walks through fresh snow in a pine forest. Medium tracking shot, natural winter light, realistic fur, soft footsteps and wind." --width 512 --height 512 --frames 22 --steps 20 --layers 45 --reuse 2 -o outputs/fox-fast.mp4 - ./h3 -d ./MiniMax-H3 --width 512 --height 512 --steps 6 - make test - Expected result: h3 --info identifies the model and Metal device, and outputs/fox-fast.mp4 contains decodable video and audio tracks. - Troubleshooting: - Compiler or Metal build failure: Run xcode-select --install, confirm Apple clang is active, then run make clean and rebuild. - --info reports missing model files: Recheck the complete Hugging Face snapshot; do not download only the main checkpoint or rename files. ### Motion Context: chain H3 clips into a longer video - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/prompt-agent-skill/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/prompt-agent-skill/ - Track: create - Depth: deep - Status: active - Category: long-video - Best for: ComfyUI users with a stable single-clip H3 workflow who need longer sequences without obvious picture seams or restarted audio. - Goal: Install Motion Context, carry the previous audio-video latent into the next generation, and complete a two-clip chain with continuous picture and sound. - Hardware: An NVIDIA setup that already runs H3 reliably. Both clips must use identical resolution; validate with short native-sampling clips first. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: advanced - Estimated time: not specified - Applicable versions: ComfyUI 0.34+ · current Motion Context · ComfyUI 0.33.4 or older: use Motion Context v0.3.1 - Motion Context installation and wiring: https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context - Author example workflows: https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context/tree/main/example_workflows - Version changes and compatibility: https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context/blob/main/CHANGELOG.md - Original source: https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context - Start here: 1. Check the ComfyUI version and install compatible Motion Context. After restarting, confirm node registration and inspect layout checks on first use. 2. Duplicate the baseline or open the example JSON. Put Motion Context in the conditioning path, Save Latent after the sampler, and Load Latent into context_latent. 3. Place Load, Save and Chain in one canvas group. For clip one use Load=0 and Save=1; Load=0 reads no file and passes the first clip through. 4. Generate clip one with the Chain node Run/Re-roll control. Inspect it, then use Approve to advance both indices and queue the next clip. 5. Keep the same dimensions for clip two and begin its prompt with the preceding composition and motion. Avoid an immediate location change while evaluating continuity. 6. Pass decoded IMAGE and AUDIO through Trim and connect trim_frames. It removes the overlapping head used for continuity. 7. Play across the join and inspect repeated frames, motion direction, freezes and restarted sound. Extend to clip three only after checking the join, and save the workflow and indices. - Commands: - cd ComfyUI/custom_nodes - git clone https://github.com/NikoDemon80/ComfyUI-H3-Motion-Context - Expected result: Clip B continues clip A's motion direction and sound, duplicate context is removed after Trim, and both clips share one resolution with an inspectable join. - Troubleshooting: - Load Latent creates a circular graph: Use the pack's Save/Load Latent nodes across runs and set the previous/current clip_index explicitly. - The join repeats or audio drifts: Wire trim_frames into Motion Context Trim, keep match_tail enabled, and retry with 22 video and 24 audio context frames. ### From a clean machine to the first video with audio - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/local-deployment-zero-to-output/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/local-deployment-zero-to-output/ - Track: run - Depth: guide - Status: active - Category: getting-started - Best for: NVIDIA users deploying H3 for the first time. - Goal: Build a reproducible local H3 setup and prompt-writing baseline. - Hardware: An NVIDIA GPU; recheck VRAM and software versions against the source article and official README. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/servasyy_ai/status/2085251627880255525 - Start here: 1. Prepare dependencies and model directories from the source article. 2. Reproduce its audio-video baseline first. 3. Then replace shot, dialogue, and ambience using the official prompt syntax. ### How four essential H3 repositories fit together - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/four-essential-h3-repositories/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/four-essential-h3-repositories/ - Track: run - Depth: guide - Status: active - Category: getting-started - Best for: Users who have the base model working and are choosing extensions. - Goal: Place the official Skill, Turbo, Motion Context, and audio workflows into one clear path. - Hardware: Depends on the selected local inference route. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/servasyy_ai/status/2086101388132835743 - Start here: 1. Start with the official Skill for a prompt baseline. 2. Test Turbo alone when speed is the constraint. 3. Add Motion Context or T8 separately for continuity or detailed audio control. ### Attention backends, character LoRA, and low-VRAM paths - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/attention-low-vram-lora/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/attention-low-vram-lora/ - Track: run - Depth: guide - Status: active - Category: acceleration - Best for: Users with a base workflow who want performance or character-consistency improvements. - Goal: Add steadier settings, an attention backend, character LoRA, or a low-VRAM path based on the actual need. - Hardware: NVIDIA; each backend and quantization combination needs separate testing. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/servasyy_ai/status/2087562850781020535 - Start here: 1. Record baseline speed, VRAM, and quality. 2. Change one attention, LoRA, or quantization variable at a time. 3. Keep the comparison before promoting the choice into production. ### H3 prompts: plan shots, dialogue and sound - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/context-ir-local-pipeline/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/context-ir-local-pipeline/ - Track: create - Depth: deep - Status: active - Category: prompt - Best for: H3 beginners who have chosen a runtime and want to describe scenes, action, camera and sound clearly. - Goal: Choose the generation mode, understand an official prompt example, and check the alignment of shots, dialogue and sound. - Hardware: No local GPU is needed to read the guide. Rendering needs an existing local or cloud H3 setup. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: beginner - Estimated time: not specified - Applicable versions: MiniMax H3 base / reference prompt guides - Official base prompt guide and complete examples: https://huggingface.co/MiniMaxAI/MiniMax-H3/blob/main/docs/VIDEO_PROMPT_WRITING_GUIDE_base_en.md - Reference-mode prompt guide: https://huggingface.co/MiniMaxAI/MiniMax-H3/blob/main/docs/VIDEO_PROMPT_WRITING_GUIDE_ref_en.md - Watch the prompting chapter: https://www.youtube.com/watch?v=G3YHSvXZP_g&t=1380 - Original source: https://huggingface.co/MiniMaxAI/MiniMax-H3/blob/main/docs/VIDEO_PROMPT_WRITING_GUIDE_base_en.md - Start here: 1. Choose by input: use the base guide for T2VA and boundary frames, and the reference guide for Ref2VA. Do not mechanically mix the structures. 2. Open a complete example and identify integrated_multimodal_description, overall_soundscape and non_diegetic_music. 3. Check subject action, camera and cut timing in shot order. Each cut should introduce a clear new view and actions must fit the clip. 4. Use the official speaker and language format for dialogue. Keep ambience and score in their own sections and check for unintended sound sources. 5. Save the complete original example as a reference and edit only what you need. Review action, dialogue and sound after generation, then address one issue at a time. - Expected result: Choose the generation mode, understand an official prompt example, and check the alignment of shots, dialogue and sound. - Troubleshooting: - Invented reference assets: Audit every Picture, Video and Audio label and keep only supplied inputs. Do not ask an assistant to guess unseen assets. - Dialogue does not match the shot: Recheck speaker tags, language and shot timing against the official example, and shorten dialogue that does not fit. ### Character references and dialogue: assign image, video and audio roles - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/video-pov-camera-angles/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/video-pov-camera-angles/ - Track: create - Depth: deep - Status: active - Category: prompt - Best for: Creators with a working single-clip H3 setup who want reference media to guide identity and dialogue. - Goal: Use Ref2VA to assign identity and sound references, then review dialogue and identity retention before trying camera edits. - Hardware: ComfyUI already running H3, with separate Ref2VA weights. More complex inputs increase compute requirements. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: intermediate - Estimated time: not specified - Applicable versions: ComfyUI 0.30+ · native H3 templates - Official R2V workflow JSON: https://github.com/Comfy-Org/workflow_templates/blob/main/templates/video_minimax_h3_r2v.json - Complete reference prompts and input examples: https://huggingface.co/MiniMaxAI/MiniMax-H3/blob/main/docs/VIDEO_PROMPT_WRITING_GUIDE_ref_en.md - Ref2VA model files: https://huggingface.co/Comfy-Org/MiniMax-H3 - Original source: https://docs.comfy.org/tutorials/video/minimax/minimax-h3-native#minimax-h3-reference-to-video-r2v - Start here: 1. Open the R2V template and select Ref2VA instead of the FL2VA weights used for T2V/I2V. 2. Connect image, video and audio references as shown in the template and record their input order. Start with only the assets the task requires. 3. Use the reference guide to assign identity, action, background or sound roles and specify what should be retained or changed. 4. Place one spoken line in a short scene, with the official speaker and language format. Check that every reference corresponds to an uploaded input. 5. Inspect identity, motion, dialogue and sound separately. Reduce conflicting references for unstable identity and shorten incomplete dialogue. 6. Once the baseline is satisfactory, try a camera or action change while specifying what stays the same. Do not replace all references at once. - Expected result: Use Ref2VA to assign identity and sound references, then review dialogue and identity retention before trying camera edits. - Troubleshooting: - Identity drift: Reduce conflicting inputs and separate identity from action references. Compare within the same short scene. - Truncated dialogue or unexpected sound: Shorten the line and check language, speaker tags and whether audio is referenced or reused. ### Turn storyboard frames into a consistent trailer - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/storyboard-to-trailer/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/storyboard-to-trailer/ - Track: create - Depth: guide - Status: active - Category: prompt - Best for: Film and advertising creators with storyboards or final-film frames. - Goal: Generate shot by shot from final-film frames and shot descriptions, then assemble a trailer. - Hardware: An H3 image-reference workflow. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/magnific/status/2090508187875356957 - Start here: 1. Extract one reference frame for every intended shot. 2. Generate each shot with its frame and description while keeping style constraints fixed. 3. Select takes, edit to rhythm, and finish sound and color consistently. ### Build a one-minute trailer on RTX 3060 with Turbo LoRA - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/3060-turbo-trailer/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/3060-turbo-trailer/ - Track: run - Depth: guide - Status: active - Category: acceleration - Best for: Creators with 12GB VRAM and an existing concept-art or storyboard set. - Goal: Animate an existing image set into short shots and edit them into a one-minute trailer. - Hardware: RTX 3060 12GB and 24GB system memory, as reported by the source. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/PixelAigc/status/2086958485741441240 - Start here: 1. Order the images and action notes by shot. 2. Generate short clips with Turbo LoRA instead of chasing a one-minute single pass. 3. Select takes and finish pacing and sound in an editor. ### Maestro six-step Turbo: trade detail for iteration speed - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/maestro-six-step-turbo/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/maestro-six-step-turbo/ - Track: run - Depth: guide - Status: active - Category: acceleration - Best for: Local Maestro users who want shorter iteration cycles. - Goal: Use a six-step distilled LoRA in Maestro for fast H3 previews. - Hardware: Depends on Maestro and the selected H3 weights. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/blizaine/status/2085554573494657328 - Start here: 1. Save a native-mode baseline first. 2. Switch to six-step Turbo without changing other variables. 3. Use Turbo for shot selection and compare higher steps for important finals. ### Low-VRAM Maestro: pruned 20B plus Turbo - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/maestro-pruned-20b/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/maestro-pruned-20b/ - Track: run - Depth: guide - Status: active - Category: acceleration - Best for: Maestro users who cannot comfortably run the full model. - Goal: Reduce VRAM pressure with the pruned 20B model, six-step Turbo, and optional First Block Cache. - Hardware: A lower-VRAM NVIDIA setup; use current Maestro documentation for the actual minimum. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/cocktailpeanut/status/2086119385757041048 - Start here: 1. Select the pruned 20B model and six-step Turbo. 2. Run a fixed-input baseline and record VRAM. 3. Enable First Block Cache only if still needed, then inspect quality again. ### Before-and-after Turbo LoRA benchmark on RTX 3060 - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/3060-turbo-benchmark/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/3060-turbo-benchmark/ - Track: run - Depth: guide - Status: active - Category: acceleration - Best for: 12GB users who want a measured view of Turbo gains. - Goal: Compare native and Turbo runs at fixed resolution and duration on the same RTX 3060. - Hardware: RTX 3060 12GB, 64GB RAM, and Windows 11, as reported by the source. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/AIPixLab/status/2088797656118390866 - Start here: 1. Run a native baseline and record its time. 2. Add only the specified Turbo LoRA while keeping input and output settings fixed. 3. Compare time, image quality, audio, and motion stability. ### Run H3 Turbo on Mac Studio with Phosphene - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/mac-phosphene-turbo/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/mac-phosphene-turbo/ - Track: run - Depth: guide - Status: active - Category: acceleration - Best for: Mac users who want a graphical H3 Turbo path. - Goal: Use fewer steps on Apple Silicon to reduce a five-second run from about 20 minutes to about eight in the reported setup. - Hardware: Mac Studio M4 with 64GB memory, as reported by the source. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: not rated - Estimated time: not specified - Original source: https://x.com/cocktailpeanut/status/2085765919079350355 - Start here: 1. Generate a baseline with Turbo disabled. 2. Enable Turbo while keeping prompt and media unchanged. 3. Use the faster result for iteration and return to quality settings for important shots. ### H3 in the cloud: your first video without local setup - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/rent-gpu-comfyui/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/rent-gpu-comfyui/ - Track: run - Depth: deep - Status: active - Category: getting-started - Best for: Users with limited local VRAM who want to validate results first. - Goal: Open a cloud template, replace its prompt or first frame, then generate and download an MP4 with audio. - Hardware: A browser that can access Comfy Cloud and a stable connection; no local NVIDIA GPU is required. - Source checked: 2026-09-06 - Site generation test: not performed - Difficulty: intermediate - Estimated time: not specified - Applicable versions: Comfy Cloud · native MiniMax H3 templates - Open the T2V template in Comfy Cloud: https://cloud.comfy.org/?template=video_minimax_h3_t2v - Comfy Cloud onboarding: https://docs.comfy.org/get_started/cloud - Cloud image-to-video template: https://cloud.comfy.org/?template=video_minimax_h3_i2v - Original source: https://docs.comfy.org/get_started/cloud - Start here: 1. Open the official cloud template and sign in. Check the account plan, credits and generation controls. 2. Start with MiniMax H3 T2V. For I2V, open its template and upload your first frame through Load Image. 3. Keep the template models and preview size. Replace the scene, action and sound description; check the first-frame input for I2V. 4. Check duration, aspect ratio and credit information, then run once. Do not resubmit the same request while it is pending. 5. Play the output and check picture, sound and duration. Download the MP4 from the output and save the workflow for later changes. - Expected result: Open a cloud template, replace its prompt or first frame, then generate and download an MP4 with audio. - Troubleshooting: - Account or credit restriction: Resolve the plan or credit issue in the cloud account page; local driver changes cannot fix cloud billing. - The input image has no effect: Confirm that the I2V template is open and the image is uploaded to its input. ### Dual-clock sampling: separate video and audio step counts - English page: https://awesome-minimax-h3-cases.zzskysilent.com/en/tutorials/dual-clock-audio/ - Chinese page: https://awesome-minimax-h3-cases.zzskysilent.com/tutorials/dual-clock-audio/ - Track: create - Depth: guide - Status: active - Category: audio - Best for: Advanced users balancing sound quality, sync, and generation speed. - Goal: Control video and audio sampling separately in ComfyUI and compare it carefully with an acceleration LoRA. - Hardware: An NVIDIA environment capable of running H3 in ComfyUI. - Source checked: 2026-08-23 - Site generation test: not performed - Difficulty: advanced - Estimated time: 75 minutes - Applicable versions: MiniMax H3 Audio T8 1.44.0 · ComfyUI native H3 - Original source: https://x.com/0xmomonifty/status/2085377094461333550 - Start here: 1. Confirm the official H3 ComfyUI baseline outputs an MP4 with audio, then save its seed, prompt, canvas, frame count, and 20-step result. 2. Find MiniMax H3 Audio T8 in ComfyUI Manager or install it with the comfy CLI, then fully restart ComfyUI. 3. Open examples/workflows/01-basic-generation and replace the models and media. Start with 22 frames, a small canvas, and the stock sampler. 4. Wire MiniMaxH3AudioConditioningT8, MiniMaxH3DualClockSamplerT8, MiniMaxH3AVDecodeT8, and MiniMaxH3PreflightT8 first. Run preflight and fix size, tag, or VRAM errors. 5. Hold video steps constant while changing the audio clock, then reverse the test. Record total time, speech clarity, event sync, and output stream metadata each time. 6. Add Turbo LoRA only after the stable path passes. Test experimental nodes, SageAttention, and long-video graphs separately rather than stacking them in the first run. - Commands: - comfy node install minimax-h3-audio-t8 - cd ComfyUI/custom_nodes && git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8.git minimax-h3-audio-T8 - Expected result: Produce an MP4 comparison that changes only the video or audio clock, with a Preflight report documenting models, frames, dimensions, and VRAM risk. - Troubleshooting: - prompt media tag validation failed: Match ,