Research update 003 · 12 September 2026
An “infinite” FastH3 broadcast can still hard-cut every scene
Reactor’s current project can keep a chat-driven RTMP feed moving. Its own model notes say the generated clips do not carry a subject, frame, or voice into the next clip.
Two things can be true
Project says: Reactor’s infinite-livestream turns Twitch or YouTube chat prompts into scene groups, builds FastH3 clips, and sends a paced RTMP broadcast. That is a real implementation of a never-ending broadcast.
Project says: its FastH3 model notes describe a different boundary: every clip is generated independently. They call the boundaries hard cuts and say subject, framing, and voice do not continue, even with identical prompts. The model’s tracks go black when there is no next clip to play.
The useful distinction is simple: a delivery connection can stay alive while the story resets every clip.
How the client keeps the broadcast moving
Project says: the streaming client keeps a generation queue and a playout queue. It automatically chains a ready playout front, then uses a 24 fps pacer to bridge bursty clip output with repeated frames and silence. Its architecture labels the model output “black between” clips.
That may keep the RTMP clock and an overlay alive. It does not create continuity that the model did not generate. A viewer can still see a frozen or black fallback, a cut, or a new scene with a different voice.
What “1× real time” buys—and does not buy
Project says: on its stated four-B200 profile, a warm FastH3 build took 14.4 seconds for a 14.375-second clip. The same source reports roughly 0.22–0.25 seconds from play to first frame after that clip is ready, and about 3.5 minutes from load to serving.
That is a high-end capacity result for a prepared queue. It is not a claim that a viewer’s idea stays in the same scene, that a queue never empties, or that a smaller machine can do the same job. This pool has not run the project.
Choose the promise before the stack
| If the product needs… | Current route to inspect | Boundary to test |
|---|---|---|
| A viewer’s new direction inside one continuing scene | H3 Max Director | Provider session limit, direction delay, bill, and handoff. |
| A chat-shaped feed of short, independently generated scenes | FastH3 queue and paced playout | Ready seconds, visible fallback, scene cuts, backlog, and moderation. |
| A local experiment or prebuilt footage | Local H3 or FastH3 | Wall time, hardware, quality mode, retries, and what enters the queue. |
The next honest demo
Do not ask only whether a feed stayed online. Show the next clip boundary. Show what happens after an empty queue. Show whether a prompt changes the current world or merely schedules a new scene. Those three moments tell a builder and a viewer far more than “infinite.”