Our radar scanned 240 items yesterday across reddit, Hacker News, GitHub releases, Civitai and a handful of peer YouTube channels. The video generation half of that haul was almost entirely about one model, MiniMax H3, and specifically about getting it to run on cards it was not really built for.

Three projects in a single day, which is a genuinely impressive amount of community effort. Then we went and read the licence, and none of the posts had.

What the community built

An any-length sampler. The author of ComfyUI-HR-Endless-Sampler, posting as /u/rhradec, demonstrated a 600 frame 1080p render on 16 GB of VRAM. The trick is chunking: split the video, hand each chunk the last frames of the previous one as context, free the VRAM between chunks. They call it alpha, and it needs a Gemma 4 12B prompt rewriter loaded alongside it, which on a 16 GB system is a second tenant you have to budget for.

A speedup with no retraining. A node called SPEED replaces the random noise at the start of diffusion with a better starting guess so fewer steps are needed. Conservative settings, 20 percent faster with no quality loss the author could see. Aggressive settings, up to 70 percent faster and, in their own words, basically unusable outputs good only for checking a seed. Those numbers are the author’s, self reported, with nobody having replicated them yet.

Two cards instead of one very big one. A Raylight community fork added dual GPU support with sequence parallelism, sparse attention, block caching and a live preview, tested on a pair of RTX 3090s. No throughput figures in the post, though the existence of a regression suite suggests somebody is being careful.

All three are the good kind of community work. People with hardware constraints solving them in public and shipping the code.

The part nobody mentioned

MiniMax H3 has open weights, which is why everyone treats it as a free model. Open weights and an open licence are not the same thing.

We checked the model card ourselves. H3 ships under a custom MiniMax H3 Community License Agreement, and the repository carries an application form described as being for the USA, EU, UK and South Korea. That is a gate rather than a ban, and it is not the same as the permissive licences most of these tools were built against.

Correction, 8 September: the paragraph below is wrong, and we corrected in the wrong direction when we wrote it. The licence does not restrict commercial use in those four territories, it withholds the grant entirely, so in an excluded region you have no licence at all rather than a limited one. There is a separate authorization you can apply for, which we since did. The full correction and what applying took is here.

We are not lawyers and this is not legal advice. What we can tell you is that if you live in one of those four places and you are planning to put H3 output into anything that makes money, the licence is a document you need to read yourself before you invest a weekend in a workflow. Our earlier reading of it was harsher than the model card now supports, so we are correcting ourselves in public: an application requirement is a real obstacle, but it is not the outright exclusion we described before.

If you want the general version of this check rather than the H3 specific one, we wrote up the two minute licence routine we run before a download finishes.

The reason this is worth a whole section is the mismatch. A person building a sampler so H3 fits in 16 GB is exactly the person most likely to be running a small commercial operation, and exactly the person least likely to have opened a licence PDF.

Where we stand

We will bench H3 in our sandbox, because testing a model is research and research is what this channel does. It will not become our production engine while the licence reads the way it does. Our talking footage and our plates keep running on the stack we have already tuned and can use without asking anyone.

That is a deliberate split and we would rather say it out loud than quietly review a model we cannot actually use.

Update, 5 September: we did it. A full day of tests on one card, with the numbers and the mistakes, is in MiniMax H3 on one gaming card.

The number that is ours, and the one that is not

We have not run H3. No render times, no VRAM figures, nothing measured on our own card, so we are not going to imply otherwise.

For scale, here is what we did measure on the model we did test this month. On our RTX 5090 with LTX-2.5, a five second clip at 1280x704 with audio took roughly 40 to 60 seconds, twelve seconds took about 340, and twenty seconds hit a hard out of memory error every time. Different model, different architecture, so treat it as a sense of the shape of the problem rather than a comparison. Duration scales worse than linearly on these things, which is precisely why chunked samplers like the one above are worth the effort.

If you are working out what your own machine could hold before you go chasing any of this, our calculator is the fastest way to find out.

A daily note from our news radar. The full week gets the DIY AI Brief treatment every Monday.