MiniMax, Plugged In

H3 also gets pulled toward work that isn't video. One person has been using it to build character sheets from a single input image, and has heard that a Qwen model does the job nicely. In the comments, someone asks, genuinely curious, whether there is any reason to make single images with H3 when other models can edit and then upscale. The two are circling the same question: whether a video model pressed into image work is the right tool for it.

In the comparisons people draw, H3 comes out ahead, and the grounds are the result. One person would rather use it for a transition because it gives "Far better consistency than image editing model". That is a claim about the output, and it is the same ground another person takes against a faster rival: "Who cares if ltx is faster", they ask, and they say the rival put out a release because "h3 is that much better". Where H3 is praised, the praise is for what it produces, not how it feels to run. That is how people talk about a component, not a companion.

In the week before, the complaints that sounded like a model misbehaving were about voices: people described characters switching voices and the wrong character speaking, and audio full of things the prompt never mentioned. Those complaints came with remedies that live in the prompt and the edit. "Minimax likes gibberish", one reply says, and the fix on offer is to give it more specific directions or shorten the video. Another person is less patient with the same problem, calling it something "Minimax H3 is just bad at", and the workaround they relay is to cut clips so only one person talks at a time. The disagreement is over whether the voice trouble is a prompt problem or a fixed limit, and both sides end up editing around it.

Compared with the week before, this week's trouble reports are about memory. One person says H3 and models of its size run out of memory when both graphics cards are active, though not when only one is passed to it. That is a problem with the machine in front of the person, and the next report is the same kind: someone else says it runs on 32GB of RAM and 8GB of VRAM because the model offloads what it can't fit into regular memory, but that anything longer than five seconds risks running out. The question under both reports is whether the model fits, not whether it is good.

Reassurance about fit comes in hardware terms: "Even an entry-level 3060 12Gb card can run it". The conversation around the tools that wrap H3 has the same preoccupation: an update to the Draw Things app adds support for Sol Attention with H3, and a commenter says its developer "optimizes things heavily so models like MiniMax will run on Mac hardware". In this stretch of the conversation, the work that gets talked about is getting H3 onto smaller machines.

Around that machinery a workshop has formed, and it treats the model's faults the way it treats its hardware limits, as things to patch. Fast action, one person says, needs loras "to stop the hands exploding into dust". A defect becomes an occasion to add something to the pipeline, and the tutorials follow that logic: one is titled "Reuseable character LoRAs without training", and workflow files pass from hand to hand.

One recipe, offered with "Trust me on this", shows where the habit ends up: clean images in ChatGPT, build a reference module, generate video with H3, screenshot the best results, upscale them again, train an H3 LoRA and generate once more with the LoRA and the module. Then comes the last instruction: screenshot again, because "that's your dataset now for other models". By that account H3 is a stage that manufactures training material for whatever comes next, not the place a character settles, which leaves the people building this way as the permanent part of the pipeline and the model as the replaceable one.