Remote settings and actions

Everything an installer can set on a screen can also be set from Venue → Devices. Open a screen and choose Change settings…, or tick several screens and press Apply settings… to change them together, then press Send to the screen. Only what you change is sent; everything else stays as each screen has it.

• How is this screen mounted? — the turn this screen gives the picture. As the stage says follows the stage or its wall panel. See Mounting and rotation.
• Sound — volume, mute and, on the apps, which output.
• Playback — render quality (Automatic, Full or Lite for a weak box), the startup animation (Cinematic, Simple or Off), how much the screen may store, and whether it starts again by itself after a crash.
• Camera — whether this screen may use its camera for people in front of the screen (When the stage asks for it or Never on this screen), and its load — Low for old boxes, Normal or High — how often it looks and how much of the processor it may use.
• Screen off — the days and times the display sleeps, in the venue’s time.
• Upkeep — the daily restart time, the log level, and how the screen keeps in step with a wall.
• For the installer — a name shown on the screen, and notes.

Add up to seven windows, each with its days and the times the screen goes off and comes back on. A window may run past midnight — Mon–Fri, off 23:00, on 06:30. On Android TV the TV goes to standby over HDMI-CEC where it can; otherwise the picture goes black and dim. The desktop app and the Raspberry Pi put the display to sleep. The player keeps running, so the screen is ready the moment it wakes.

Every screen restarts its player once a day, at 04:00 venue time unless you choose another time or Never. It starts each day fresh and takes new player versions then. A wall never restarts in the middle of switching to new content.

If the player crashes, it starts again by itself — within seconds on the desktop app and the Raspberry Pi, within about half a minute on Android. When it keeps crashing it waits longer between tries: a minute after four crashes in ten minutes, ten minutes after eight in half an hour, so a broken screen never keeps a box busy, and it comes back as soon as the cause is gone. Restart after a crash (on by default) switches this off, for a TV or computer that is also used for other things: then a crashed player stays closed until someone opens it. A Raspberry Pi starts it again at its next boot.

A change reaches a switched-on screen within seconds and is applied without a reload. Until the screen confirms it, it reads Pending; then Applied. Failed names what the screen could not do and why — a browser cannot switch the TV’s sound output, for example. Some changes, such as render quality, take effect after the next restart; the screen says so.

An installer can change settings on the screen itself — the Android TV settings overlay, the desktop app’s Settings, the arrow keys on a Pi. Devices lists those as Changed on the device at 10:42.

The latest change wins, key by key: yours from the office, or the installer’s on the screen. When the installer chose Keep my changes on this screen, their value shows with a lock and stays, whatever you set later. Keep the installer’s values here too makes their values yours.

• Take a screenshot — the screen sends a picture of what it really shows, video included, and it appears in the drawer.
• Upload logs — the last day of the screen’s log, as a link in the drawer, for support.
• Restart the app — the app closes and starts again.
• Reboot — the whole box. On Android TV only where IT set the box up as a managed device; otherwise the app restarts.
• Update the app — installs a new version of the Android TV app, when your Wunderframe offers one. The TV asks before it installs, unless it is a managed device.
• Move to another stage… — the screen plays another stage or wall panel, keeps its identity and frees its old place.
• Unpair — the screen stops playing and shows its pairing code again.

Screenshots, logs, reboot, move, unpair and app updates need a Wunderframe app; a browser tab can only reload, resync, clear its cache and identify itself. The drawer offers only what the screen can do.

Operators can identify a screen, take a screenshot and Watch live, for the venues they run. Settings and the other actions need an editor or the owner. Every change is kept with who made it and when, under History in the drawer and in the Live board’s log.