Setting up the Rundown Viewer

Prerequisites

• A running Viz Mosart system, with Manus Administrator running and the Viz Mosart client UI running and displaying a rundown.

Installation and Configuration

The Rundown Viewer needs almost no configuration of its own. It reads the shared Mosart server settings that the other Mosart Web Apps use. Its one setting of its own is whether its session may time out, described under Session Timeout below.

1. Ensure your Viz Mosart system is operating under normal working conditions, as above.

2. From the Mosart Web Apps Configuration Tool, select Home and then the Rundown Viewer card.

Access

The Rundown Viewer has no roles of its own. Where authentication is enabled for Mosart Web Apps, users sign in as they do for the other apps, but there is no separate viewer or author permission to grant for this app: anyone who can reach the URL can read the rundown. It is a display, so it sends no commands to Viz Mosart.

Multiple Studios

On a site that runs several Viz Mosart back ends from one Mosart Web Apps host, the Rundown Viewer shows the rundown of one studio at a time.

• Define the studios once in the Configuration Tool. See Studios.

• Launch the Rundown Viewer for a studio from the Home page, or open it with ?studioId=<studio>.

• Only studios whose back end is a Viz Mosart server are offered, since those are the ones with a rundown to show.

• An operator can also switch studio from inside the Rundown Viewer, using the picker in the top bar. It appears whenever any studio is configured, not only on a multi-studio site, and choosing a studio reloads the page with that studio's ?studioId=. An unattended display therefore stays on the studio it was pointed at across reloads.

Setting up an unattended display

The Rundown Viewer is often put on a gallery or studio-floor screen with nobody driving it. Because each view is just a URL, that needs no special deployment:

1. Decide what the screen should show, and add the matching parameter to the URL. The options are listed under Choosing what to display: the rundown, the rundown with the story script, the script alone, the timeline alone, or the keyboard shortcut panel alone.

2. Point a browser at that URL in kiosk or full-screen mode.

3. Set the display options once on that screen. They are stored in that browser, so each display keeps its own settings and you can tune one screen without affecting the others.

Optional Server Setups

Support for main and backup connection

• If you have a backup server for redundancy, define the environment on the Studios page, where each studio carries its own main server and optional backup. The Rundown Viewer then shows an indicator for each of the two servers.

Support for HTTPS

• If you are using HTTPS, define the environment in HTTPS and Certificates.

Session Timeout

Where authentication is enabled, the Configuration Tool's Server Configuration page carries an Allow session timeout group inside Authentication (OIDC), with one switch per web app.

• The Rundown Viewer switch is off by default, reading Stays signed in while open. The viewer renews its own session for as long as the page is open, so an unattended display never drops to a login screen mid-show.

• Turning the switch on makes it read Renews while in use; can time out when idle, which is the right choice on a shared machine where an abandoned session should not stay signed in.

• Session timeout, beside the switches, sets how long an unused session survives, in minutes, from 5 to 10080, defaulting to 30. It applies only to the apps whose switch is on. A value outside the range is clamped, and one that is not a whole number falls back to 30; both are logged at startup.

Troubleshooting

See section Troubleshooting.