50 seats total·128 fps median measured over 16 min · Helio 0.1.115 · free invite-only beta.→
Lab · Performance

Over 120 fps observed, without claiming locked 144

A 16:04 direct session shows what this Lume chain sustained—and the eight interruptions that prevent a universal claim.

16:04analyzed direct-session duration
128.4 fpsobserved median frame rate
140 fpsP95—not a locked rate
8 freezes2.597 seconds combined
Results

The median exceeds 120 fps; perfect stability does not

128.4frames per second median
140frames per second P95
6.59 Mbpsmeasured median bitrate

The same session recorded eight freeze events totaling 2.597 seconds. A “144 fps” headline would hide that essential context.

Protocol

One identified session, not a universal benchmark

The analyzed direct session lasted 16 minutes and 4 seconds. It represents one hardware, software, network and routing context. It does not include a photodiode or high-speed-camera input-to-display measurement.

Interpretation

Why median and P95 do not mean “locked”

A median splits samples in half. P95 describes a percentile bound. Neither proves a constant frame rate. A locked-144 claim would require a tight frametime distribution and no meaningful interruptions.

Incidents

Eight freezes matter more than an isolated peak

The summary alone cannot assign a cause to each event. Network, encode queue, decoder or scheduling may contribute. Publishing them alongside positive results makes later regressions comparable.

Conclusion

The precise claim this test supports

Lume sustained a median above 120 fps for a 16:04 direct session on the tested setup. It does not promise locked 144 fps everywhere or establish perceived latency.

Lume © 2026