MiniMax H3 day-one test finds better identity retention with max ref image size
jozbgm · reddit · 2026-08-04
After one day with MiniMax H3, the author says they’ve basically spent the entire day testing it and building from a real benchmark clip.
What they tested
- Recreated a short clip from an earlier Seedance video using H3.
- Kept the same character and beats, stitched from 6-second clips into a 42-second sequence.
- Used ComfyUI, an RTX 5090, 96GB RAM, and the minimaxh3ref2vaprunedint8convrot workflow.
What seems to help
- refimagesize: max works better than matching size when faces or textures must persist.
- resmultistep + beta scheduler seems better for reference-heavy prompts.
- Describe sound as physical events in time—impact, tear, breath—instead of mood words.
- Re-anchor the character explicitly in every clip rather than assuming continuity.
Open questions
- How much motion can fit in one clip.
- How well identity survives across long chains of generations.
- Whether some cuts should be generated in one shot instead of stitched later.
The author says they’re only at hour one of the optimization curve and invites others to share settings and prompt habits.
Related event: MiniMax H3 Tests: Multimodal Workflow and Open Weights(12 posts)→
More from Infra
- Databricks reaches a $4B revenue run-rate and nearly $21.8B raised, says Infra Play — thedealdirector · 2026-08-04
- AI index steepens 5x after late 2024 as compute shifts from pretraining to inference — ProfBuehlerMIT · 2026-08-04
- Local Benchmarking of DeepSeek V4 Flash Quantizations: Q3 vs Q8 — Spicy_mch4ggis · 2026-08-04
- Bittensor’s Root Reborn revives validators and removes automatic sell pressure — const_reborn · 2026-08-04
- ARPL makes llama.cpp adapt to ARM ISA and core topology at runtime — OpeningTough145 · 2026-08-04
- DeepSeek V4 Flash 0731 hits a ctx_other error in llama.cpp speculative decoding — Ambitious_Fold_2874 · 2026-08-04