Research updates
Every update is dated and condition-bound
Provider claims, project reports, community reports, and pool measurements are kept distinct. This pool has no measured run yet.
Latest
22 September 2026 · Dreamverse FastH3 profile check
Dreamverse gives FastH3 a four-GPU chain. It does not give it a live-capacity result.
FastVideo documents 124-frame 768×1344 Preview v1 segments, last-frame carry, a four-GPU default, and a cold readiness wait that can take tens of minutes. It is a continuity mechanism to inspect, not a stream benchmark.
21 September 2026 · FastH3 V2 native-canvas check
FastH3 V2 has a speed boundary before it has a speed claim.
One detailed Radeon 8060S community report puts a 768×1344, 243-frame V2 run at 33 minutes 9 seconds. The author says the sparse path does not help below a stated token threshold; this is local rendering, not live video.
20 September 2026 · FastH3 V2 scope recheck
The FastH3 V2 transition claim is still a source conflict.
FastVideo’s model card says first/last-frame conditioning was not distilled. ComfyUI’s current template says it accepts those frames. Do not call it a continuity route before a pinned render proves the anchors hold.
19 September 2026 · RTX 5090 FastH3 timing check
A 5090 FastH3 run is a faster review loop, not live video.
A platform-published FastH3 Preview v1 test returned 15.08 seconds of image-to-video in 55 seconds at 480×640 and 126 seconds at 768×1024. Its hot timing excludes queue and model loading.
18 September 2026 · FastH3 Comfy scope check
FastH3 reached ComfyUI. Its first/last-frame claim is already disputed.
FastVideo documents a fixed eight-forward V2 recipe as T2AV-only; a current official ComfyUI template says it also accepts first and last frames. Do not promise a transition before a pinned run settles it.
17 September 2026 · Remote H3 serving reality check
An OpenAI video endpoint does not make H3 a live-video server.
vLLM-Omni documents a separate H3 service that ComfyUI can call. Its stated full-H3 four-B300 row returns about 8.7 seconds of output in about 87 seconds.
16 September 2026 · Collective control-loop check
YoLive has a real-time claim. The useful question is who gets to choose the next scene.
Yoroll says group proposals and votes guide the next scene, with 10 seconds of 768p, 24 fps video generated in four seconds on eight B200 GPUs. The missing measurement is vote-to-screen time.
15 September 2026 · Consumer-channel reality check
A 5090 can reportedly keep FastH3 on air. That is not the same as a live 24-fps show.
A community source reports 22.1 fps at 448×448 on one RTX 5090. Its continuous channel relies on retimed playback, prequeued work, and distinct scenes.
14 September 2026 · Capacity correction
Four B200s do not clear FastH3’s documented 15-second deadline
Reactor gives separate four- and eight-B200 timings. The latter is faster than the cited clip duration; neither is an independent live-service result.
13 September 2026 · Autoplay boundary
FastH3 can autoplay. Its default queue does not.
Reactor documents optional hands-free playout, but a completed clip otherwise clears to black. The queue policy is part of the product.
How to read a record
- Provider says proves a published capability, price, or product term.
- Project says records a project’s stated setup or measurement.
- Community report records a user’s stated experience and is a lead for replication.
- Measured here will appear only with a pool test, method, inputs, and result.