What people were actually discussing on October 18–19
MiniMax H3 is not this week's release: open weights landed on August 3, 2026, a few days after the model appeared on July 31. The new material is a set of r/StableDiffusion and r/comfyui threads from October 18 and 19 where people post failures and workarounds, not demos.
Three themes run through them. Faces: tattoos and paint vanish within a second. Length: a 35-second take costs hours of sampling, and on a consumer card people buy extra length with custom nodes and system memory. Acting: in an argument scene the model delivered an emotion its author did not expect.
Everything below is user opinion, sourced and dated. Keeping it apart from the spec sheet matters for AI video production, because half of these problems only appear on your own files.
What the official spec sheet says
Specs come from the open-weights announcement (https://www.minimax.io/news/minimax-h3-open-source) dated August 3, 2026.
Two caveats. The 2K module is not part of the open release — resolution comes from H3-Regenerate-2K, currently API-only. An audio reference in Ref2VA cannot stand alone: it needs an image or video input. The full list of models with duration, resolution and limits sits in the guide to AI video models 2026.
| Spec | Value |
|---|---|
| Duration | 4–15 seconds |
| Frame rate | 24 FPS |
| Audio | 32 kHz stereo |
| Resolution | 768 px on the short side by default; 2K through H3-Regenerate-2K |
| Modes | FL2VA (zero, one or two images) and Ref2VA |
| References in Ref2VA | up to 9 images, up to 3 videos, up to 3 audio clips, 12 files total |
| Dialogue languages | 11, Russian among them |
Faces: tattoos and paint get "washed"
The freshest observation is a thread from October 19, 06:34 UTC: Minimax H3 tends to "wash" faces (https://www.reddit.com/r/StableDiffusion/comments/1x9pio1/minimax_h3_tends_to_wash_faces/). The poster attaches head elements to a character using a clean image plus references for each item. Head accessories hold, but anything on the face — tattoos, face paint — disappears within a second.
The reply at 06:38 UTC suggests face close-ups on the reference sheet and naming key features in the retention analysis section of the prompt. Later replies add two more tips: use fewer references, and paint the tattoo or face paint onto the clean character image first, or run a second masked pass over the face only. One commenter also notes that H3 is weaker on faces in wide shots, which can only be partly mitigated.
For a client the takeaway is blunt: the face is its own line in acceptance. If a tattoo, scar or makeup carries the meaning of the shot, it vanishes first.
A 35-second take: hours of sampling
The most detailed thread is from October 18, 17:19 UTC: H3 test render, 35-second tracking shot (https://www.reddit.com/r/StableDiffusion/comments/1x98r2r/h3_test_render_35_second_trackingwalking_shot/). One continuous take: a technician walks a corridor, pauses to press a button, walks on. References were two five-panel sheets — five face angles, five of the body.
The render ran on a rented RTX Pro 6000 with 96 GB, then an upscale pass in DaVinci Resolve. Timings from the comments: 1.0 MP (1376×768) took a little over an hour of sampling, about ninety minutes including model load and save; 1.6 MP (1728×960) took more than two and a half hours of sampling plus roughly ten minutes to load and save.
Another user (October 19, 01:22 UTC) explains the decay: on long continuous segments the image degrades, and by the fifth segment the drop is obvious. Carrying latents and injecting the previous end frame help partly — three or four segments is the usable limit.
One publishing detail from the same thread. Render metadata confuses YouTube: gamma tagged sRGB gets converted to Rec.709, contrast climbs and shadows crush. Export tagged for Rec.709 and it stops.
This is where the work splits: handcrafted videos get checked shot by shot, while mass vertical videos are built from short scenes where that decay never gets going.
20 seconds on 16 GB: selflift-Fish and the trade-off
Thread from October 19, 09:40 UTC in r/comfyui: selflift-Fish: Longer H3 videos & higher resolutions on a 16GB GPU — 20s clips / 1920×1088 tested (https://www.reddit.com/r/comfyui/comments/1x9sgr1/selfliftfish_longer_h3_videos_higher_resolutions/). The author published a version of the SelfLift node for H3 in ComfyUI: it fixes the background swelling and shifting of the original spatial tiling scheme, and promises longer clips with less pressure on VRAM.
The numbers in the thread: an RTX 5070 Ti with 16 GB plus 128 GB of system RAM. For ten-second runs at 1920×1088, full workflow time fell from 27:50 to 12:55. The author flags these were different runs rather than a fixed-seed benchmark.
The caveat that is easy to miss: 16 GB is the GPU capacity, not the total memory requirement. The results rely on offloading into system RAM, and the same trick will not reproduce on a machine without that headroom. Comments ask for examples and a workflow, and one asks what the trade-off is.
Acting in an argument scene, and the hunt for endless talk
Thread from October 19, 11:09 UTC in r/comfyui: MiniMax H3's acting in this argument scene surprised me (https://www.reddit.com/r/comfyui/comments/1x9tze1/minimax_h3s_acting_in_this_argument_scene/). The author had been experimenting with refmods and motion context and noticed that in some scenes the acting and emotional delivery come out unexpectedly alive. The post asks which tasks H3 is genuinely good at.
A different thread, October 19, 10:16 UTC in r/StableDiffusion: is there anything for H3 like infinite-talk for Wan 2.1 (https://www.reddit.com/r/StableDiffusion/comments/1x9t1ug/is_there_any_workflow_or_node_for_h3_for/). What the author wants is the overlapping sampler — the last 9–15 frames — that let Wan 2.1 run an endless talking head.
The answers say nothing is ready. At 10:39 UTC one user notes the scene moves fast and someone is probably already tinkering in Discord. At 11:21 UTC another describes their own endless-speech experiments: native Comfy loop nodes plus a dummy "talking nonsense" prompt. In their view a proper solution needs sentence splitting, length calculation and varied end frames, otherwise the same frame repeats.
Resolution: why a closed model's 480p can look cleaner
Thread from October 18, 19:10 UTC: Why does 480p Grok Imagine look cleaner than open-source 1080p Wan/H3? (https://www.reddit.com/r/StableDiffusion/comments/1x9bjjk/why_does_480p_grok_imagine_videos_look_cleaner/). The poster sees "mushy" fine detail on faces from open models — skin, eyes, lips, hairline — at a higher nominal resolution.
Explanations converge on three. H3's official ceiling is 768 px on the short side, and anything above goes through a separate module rather than native generation. Quantized builds and turbo LoRAs cost quality: int8 sits close to bf16, int4 differs noticeably. A closed service runs on a GPU farm that can afford a full unoptimized pass.
What this means when you order a video
Three conclusions land in a quote. A long take is hours of sampling plus post, and past the fourth segment you either regenerate or cut. A face carrying a tattoo, paint or scar needs its own acceptance step. Endless dialogue is not a button yet: it comes from a chain of generation, line splitting and mixing.
That shapes the budget: piecework where every scene and face matters, throughput on short shots and repeatable templates. In our own pricing, handcrafted videos start at $394 for up to 90 seconds with about a week of turnaround, and a series is priced per episode on the same basis. Mass formats run from $2.47 CPM (per 1,000 views).
