Offline playback and recovery
Edge keeps its state and downloaded content outside the renderer, in its own database and verified content cache. The renderer can restart, and the whole computer can lose power, without losing the screen’s presentation or pairing.
Offline playback
Section titled “Offline playback”After Edge downloads and prepares a presentation, it keeps the files and settings on the computer. If Edge restarts before the server is reachable, it starts from the saved presentation first and reconnects afterward.
While Tilecast Server is unreachable, Edge keeps following the schedules it already has. It can’t receive a new assignment or download files it never received. When the server returns, Edge reconnects with a gradually increasing delay and catches up with the current Tilecast state.
Content changes
Section titled “Content changes”Edge prepares a new presentation completely before it replaces the one that’s playing. If the new content can’t be downloaded, verified, or started, the current presentation keeps playing. An interrupted download continues where it stopped, and a damaged file is downloaded again instead of shown.
Commands and settings
Section titled “Commands and settings”Edge saves each command before it runs it. If Edge stops while a command runs, it reports the interruption after it restarts and doesn’t run the command again.
Player settings are stored with a revision number. An invalid or older settings revision doesn’t replace the last one Edge accepted, and the accepted settings apply at startup before Edge contacts the server.
Renderer failures and safe mode
Section titled “Renderer failures and safe mode”tilecastd restarts the WPE renderer without restarting the whole Player. If playback keeps failing, Edge enters safe mode instead of restarting in a loop, and stays there until someone sends Exit safe mode from Studio.
Updates
Section titled “Updates”An Edge update never leaves the screen without a working release:
- an interrupted download continues where it stopped;
- a downloaded release is installed in its own directory and doesn’t replace the release that’s playing;
- after the switch, the new release is provisional, and the previous release stays installed until the new one confirms;
- a new release that fails, doesn’t confirm, or is running when the computer restarts or loses power goes back to the previous release automatically.
One case needs someone at the computer: if the new release upgraded the local state database before it rolled back, the previous release shows its recovery screen. See Recover after a rollback.