Why MiniMax H3 videos run long: the frames % 17 == 5 grid, explained
bennash · x · 2026-09-07
bennash explains why MiniMax H3 (Hailuo) returns slightly longer clips than requested: the model runs at 24 fps but only allows frame counts where frames % 17 == 5 (5, 22, … 124, 243, 362). Exact-second counts (120/240/360 frames) are illegal, so the pipeline snaps up: 5s→5.167s, 10s→10.125s, 15s→15.083s. The API only takes an integer duration 5–15 with no frame-count parameter; the same snapping occurs on fal, Hailuo, and local weights, so for exactly 5.000s you must trim after download.
More from Multimodal
- Sheet Music to MIDI Pipeline Offers a More Structured Space for Music Models Than Audio — felpix_ · 2026-09-07
- Seen2Scene open-sourced: flow matching trained on real partial scans for 3D scene completion, ECCV 2026 — angelaqdai · 2026-09-07
- TAIKEN: a 4-minute AI action film made with MiniMax H3 and ChatGPT — bennash · 2026-09-07
- Midjourney watercolour-style generations showcased — davidhoang · 2026-09-07
- Wuxia "Netherworld Divine Palm" AI video made with open-source MiniMax H3, prompt shared — Low_Loquat_4035 · 2026-09-07
- ComfyUI-Easy-Use adds Pass or None node for conditional value routing in workflows — altoiddealer · 2026-09-07