Showmaker needs a few one-off configurations before it is fully usable. This section covers them, both for the system administrator and for the Showmaker user.
Info: Documentation is continually updated, see the latest version at the Vizrt Documentation Center.
System Administrator Only
Follow the standard setup described in section Configuration Tool, together with the Showmaker-specific instructions, then return to this page.
Setting up Showmaker for Daily Use
Prerequisites
Viz Mosart 5.14.3 or later.
Manus Administrator running.
The Viz Mosart client UI running and able to display a rundown.
Info: Individual Showmaker features depend on the Viz Mosart server supporting them, so for the version required by your Mosart Web Apps release, see the Mosart Web Apps Release Notes at the Vizrt Documentation Center.
Installation and Configuration
You can open a standalone, pre-production rundown in Showmaker with no additional configuration. To work with Viz Mosart templates, or to test the rundown against Viz Mosart, complete the one-off steps below.
To manage Viz Mosart templates
To work with Viz Mosart template sets in Showmaker, the bundled NRCS Plugin must be correctly configured, because Showmaker embeds it to read those template sets.
Follow the Showmaker instructions under App Configuration.
To connect to Viz Mosart
Ensure your Viz Mosart system is operating under normal working conditions. As a minimum, Manus Administrator must be running, and the Viz Mosart UI must be running and displaying a rundown.
In the Configuration Tool, open App Configuration and confirm the required setup is complete, including the MOS communication settings that let Showmaker act as a newsroom system towards Viz Mosart.
Consider the scenarios under Optional Server Setups below.
Continue with Getting Started.
Studios
A Studio groups the MOS devices that make up one production environment, typically a main Viz Mosart server with an optional backup, or one gallery on a multi-studio site. Showmaker uses studios to decide which Viz Mosart server a rundown is sent to, and operators can override the studio on an individual rundown.
Studios are created in the MOS communication settings, and a site running several Viz Mosart back ends from one Mosart Web Apps host defines them on the Studios page. See Studios.
Roles and Access
Showmaker has two roles, which are only enforced when authentication is enabled. With authentication off, everyone has full control.
Role name | Permissions |
|---|---|
showmaker-viewer | View only. |
showmaker-admin | Full control. |
Roles are assigned in your authentication provider, not in the Configuration Tool, and are read from the roles claim. See Roles.
Info: A user who signs in with neither role is shown a screen explaining that they do not have access, rather than an empty show list. If that appears unexpectedly, the user is authenticated but has not been granted a Showmaker role in your identity provider. If instead the screen reports that their access could not be checked, the check itself failed and it offers a retry.
Comments and mentions
The @mention picker is populated from the people who have signed in to Mosart Web Apps. With authentication switched off there are no identities to harvest, so the picker stays empty and mentions cannot be used. If your teams rely on mentions, enable authentication.
Video Clips
Showmaker's clip picker searches the media service on the Viz Mosart server, so:
Media Administrator must be running on the Viz Mosart server. It performs the search.
Current Viz Mosart servers answer clip searches over the Mosart server's own real-time connection, needing no separate key. Older versions fall back to the REST media search, which requires the Authorization Key to be set. See Mosart API Access.
How clips are labelled in the lists is controlled by the Video Clips setting. See Video Clips.
TriCaster
Two Showmaker features use a TriCaster, and both need its address and credentials entered once under TRICASTER FOR LIVE PREVIEW. See TriCaster Live Previews.
Uploading a clip from Showmaker to the TriCaster clip server.
Clip thumbnails from a TriCaster, which the Mosart web server fetches on the browser's behalf so that operators need no direct access to the device and thumbnails work over HTTPS. If TriCaster clip thumbnails are blank, check the address, username and password.
To work with the Story Recorder feature
Story Recorder lets operators mark stories for recording in Viz Mosart, optionally publish the resulting clips to online platforms (TriCaster only), or replace the original story script with the recorded version. To make these controls available in Showmaker:
Configure Story Recorder in Viz Mosart first. See the Vizrt Documentation Center, under Viz Mosart Administrator Guide > Operational Examples > Story Recorder Setup.
In the Configuration Tool, open Showmaker > Feature settings and turn on Enable Story Recorder controls.
Once enabled, every story in Showmaker gains Record and Publish actions and a Use recording toggle. For how operators use these controls, see Recording a Story.
Background on Story Recorder itself is in the Vizrt Documentation Center, under Viz Mosart User Guide > Operation > Story Recorder.
Graphics Integrations
Showmaker can host graphics panels alongside the Viz Mosart templates. Both are optional and both are registered once in the Configuration Tool, under the Showmaker asset integration settings:
Viz Pilot Edge, for editing Pilot Edge graphic templates in place.
Viz Flowics, for cloud-based interactive HTML5 graphics. This needs an integration token issued by Flowics support, which is stored encrypted.
See Asset integrations settings. Both panels are embedded in the browser and exchange MOS messages with Showmaker directly, so beyond the URL and MOS plugin ID there is no further server-side setup.
Optional Server Setups
These settings are usually performed by a system administrator.
Support for main and backup connection
If you have a backup server for redundancy, define the environment in Server Configuration.
Support for HTTPS
If you are using HTTPS, define the environment in Server Configuration.
Troubleshooting
See section Troubleshooting.