Local Video Starts With H3, Then the Hardware Argues Back

A model people run themselves becomes a workshop. One commenter says they are "already lost in this sea of 4-step loras for H3," and another calls turbo loras "absolutely the biggest variable" in a workflow. The sign that people are building on a model is that their arguments are about settings.

People are reaching past clips toward scenes. Someone made a horror music video to see whether H3 could "hold together across a full music video" rather than a single clip, generating the shots separately and editing them to the music, and someone else recreated the ending of WarGames from four stills and a voice sample, as a test of a custom node built for H3. In both cases the model is one stage in a longer pipeline, with editing or a custom node around it. A workflow builder says theirs can generate from an input video, into the start of one, or between two, joining them.

The limits people name are limits of continuity. One commenter says MiniMax video extend methods seem to produce "a flash of light or some other flaw," and another says MiniMax H3 reference to video "works pretty well but you have to give it the reference image each time." In both, what the model is fed is where the trouble starts: the previous video in one, the reference image in the other.

When output goes wrong, the advice points at the user's setup, not at the model. A commenter tells people who offer loras or say H3 is bad at character transfer that correct prompting gets "nearly perfect character transfer," and another tells someone using several tools at once that bouncing between them lets "little differences pile up" and kill consistency, and that the fix is to lock in a style with only ComfyUI and MiniMax first. That is how people talk about a model they have decided to trust: a failure is a question about what the user did.

The price of that regard is paid in hardware. Even a happy user says "I'm very impressed with h3. Only issue for me is that local generations take a while." For some people the wait is a wall. A commenter with a 7900XTX card and 24 gigabytes of video memory says they cannot seriously run any video model, and that LTX, which was supposed to be easier to run, was slow too, while someone with a 5070ti and 16 gigabytes calls video possible and tinkerable but "hardly worth the hassle kind of."

For people the hardware leaves behind, LTX is the other name that comes up. Someone running an rx6700xt says they tried everything to make H3 work and failed, while "LTX just works with occasionally OOM," and someone else says LTX is much easier to train, because its runs do not need the babying that MiniMax runs do. Both describe LTX by how little it asks of them next to H3.

H3 is the yardstick for what comes next. A commenter delighted that someone has given them references and edit capability says it is "potentially awesome if it can come close to how H3-Minimax was managing it," and another expects attention to stay put, saying that only a better, fully open-weights model that runs on modest hardware could pull it away, and that "doesn't seem likely anytime soon." Against the week before, more people on Reddit wrote about MiniMax.

MiniMax the company turns up at the edges of the conversation, in license terms and subscription plans. A commenter says the model's output can be monetized but that serving the model itself takes a contract with MiniMax, and a Chinese-language forum post relays an announcement that an M Plan will take over the Token Plan's subscriptions, with some tiers able to use H3 and the Token Plan closing to new purchases. For people making video at home the lab can stay out of sight; it comes into view when someone wants to serve the model to others, or to buy their way in through a plan.