H3 Max Live generates video faster than it can be watched, and that changes the game for live video
Fal post-trained MiniMax's H3 model and optimized inference to cross the infinite video barrier: every frame is born in real time, directed by chat.

The AINews newsletter from Latent Space called the launch of H3 Max Live, from Fal, a "break in the infinite video barrier." The phrase sounds like hype, but the data behind it is concrete and has a direct consequence for anyone designing products: for the first time, a generative video model produces frames faster than a person can watch them. This removes the premise that has structured all generative media so far, that generating video is a batch operation you wait to finish.
The problem that always existed: latency greater than consumption
Until now, every AI video pipeline was designed around one inconvenience: generating image and video takes time. Even with consistency models bringing a 30-second generation down to 1 second, the practical result was, at best, 1 FPS, far below what the human eye accepts as fluid. The pattern that levels.io himself described was spending 2 to 5 minutes to produce 15 seconds of video.
This imbalance (generation time far greater than consumption time) forced every video application to be asynchronous: the user requests, waits, receives. Live streaming, interactivity and infinite loops were simply out of reach, because the rendering queue would never catch up to the clock.
How Fal crossed the line
According to the source, Fal did not train a model from scratch. It took MiniMax's H3, released the previous month, and did two things:
- Post-trained the model to improve cost and quality, generating the variant named Max;
- Optimized inference on the company's own engine, reaching 35x the speed of the official endpoint (the community itself cited up to 50x in some tests).
The result is what Fal's account announced as "video generation is now faster than real time." It was Ethan Mollick who noticed it first, in experiments using only the web interface:
A line in AI video has been crossed. In my experiments with the web interface, H3 Max now creates reasonably good quality video in less time than it takes you to watch it. This is real-time from the moment I hit "generate" (and it includes prompt enhancement).
>
-- Ethan Mollick
The architecture behind the live product is H3 Max Director, described by Fal as an autoregressive and continuous version of H3 Max, with up to two minutes of context. Autoregressive here is the key piece: instead of rendering a closed clip, the model generates the next frame conditioned on what has already been produced and on what the chat sends. This is what turns "generating a video" into "streaming a video that never ends."
What became a product
Fal employees packaged the model into an infinite broadcast, a kind of "interdimensional cable" where anyone types !prompt in chat and it appears on screen within seconds. Rehan Sheikh's demo, tied to a Twitch live stream, hit 5.75 million views. levels.io launched Infinite Slop, an interactive stream in which chat text becomes the next scene and the model tries to stitch continuity with what came before.
An operational detail that matters to anyone who wants to build something similar: Twitch and YouTube took the streams down almost immediately. Fal's response was to build its own live video service (fal.live), in the spirit of "twitch plays pokemon," with LLM-generated prompts that the audience can vote on. In parallel, the company launched Reference-to-Video for MiniMax H3 Max, reporting a real-time factor of 1 at 768p in initial preview.
Why this matters for those building in Brazil
Be honest about the quality: the source itself acknowledges that, watching for a few seconds, you can tell it's slop, a jumble of RL content with no plot and low-quality imagery. Nobody is going to binge this. But AINews's central argument is about trajectory, not the current state: this is the worst the technology will ever be. There is now a proof of concept that good-enough video, faster than real time, is possible.
For Brazilian developers, what changes is the category of product that becomes viable:
- Interactive and live streaming: generative channels where the audience directs the scene in real time, without a rendering queue.
- Metaverse and simulated worlds: aligns with Solaris, from Runway, cited in the same newsletter as an "interface world model" that generates interactive interfaces frame by frame, with no code. The idea that "the frame is the interface" and serves as a training environment for agents stops being an abstraction.
- NPCs and game environments generated on the fly, instead of pre-produced assets.
The architectural point developers need to internalize: video models are migrating from the batch paradigm (request, wait, receive file) to the stream paradigm (continuous flow, autoregressive, conditioned on live input). These are two different engineering worlds, both in inference infrastructure and in application design.
Where it still isn't worth it
It's important not to confuse the demo with serious production. Some concrete limits:
| Aspect | Current state (according to the source) | |---|---| | Quality | "Slop": low fidelity, no narrative coherence | | Resolution | ~768p in preview | | Context | Up to 2 minutes in H3 Max Director | | Distribution | Mainstream platforms (Twitch/YouTube) blocked it | | Model | Depends on Fal's proprietary endpoint, no open weights |
If the project requires fine control over script, character consistency over minutes, or production quality, the traditional batch video pipeline still delivers superior results. Faster-than-realtime doesn't replace a controlled video pipeline; it opens up a new class of application (live and interactive) that didn't exist before.
There's also the dependency: for now, everything runs through Fal's optimized inference, which means cost per video token, rate limits, and no self-host path. For those who want to quickly prototype a live experience, the natural path is Fal's API; for those who need cost predictability and sovereignty over the stack, this is still a moment to watch. What you can't do is treat this as a passing curiosity: the barrier that structured the entire sector has just fallen, and those who build for the future that's arriving, not for the current state of slop, read the metagame better.
Translated from the Brazilian Portuguese original · Read the original
Convex Agent Component: how native memory and RAG work for AI agents
Convex's official component bundles threads, persistent memory, and hybrid vector/text search for those building AI agents, without setting up a parallel vector DB stack.
