A broadcast rail that tells the truth: LIVE vs REPLAY in Rive by Jessy MariauA broadcast rail that tells the truth: LIVE vs REPLAY in Rive by Jessy Mariau
A broadcast rail that tells the truth: LIVE vs REPLAY in Rive
The instrument rail from my FLAGFALL broadcast package: a status strip that distinguishes a live feed from a replay honestly, beats a dot when a real frame lands, and degrades through a designed failure ladder when the feed stalls, instead of freezing and pretending.
The signal chain rail
Roughly 245 bound properties are written into the file per frame from the runtime. The bare .riv is deliberately static, because the motion IS the data: adapter stamp, feed-beat dot, connection states and the failure ladder are all driven by JavaScript through Rive data binding.
The panel running live
Ticker running on live feed data
This is the unglamorous half of broadcast graphics, and the half that decides whether viewers trust the screen.
A broadcast status strip that distinguishes a live feed from a replay honestly, beats a dot when a real frame lands, and degrades through a designed failure ladder when the feed stalls instead of freezing.