Settings here are needed when you use the NRCS Plugin or Showmaker for the first time, or have installed the Mosart Web Apps bundle on a separate server to the Viz Mosart server.
Note: Showmaker always requires the NRCS Plugin to be correctly configured.
NRCS Plugin
To configure the NRCS Plugin
First perform the Getting Started (Installation) procedure.
Select App Configuration and click NRCS Plugin.
From the NRCS type drop-down menu, select your newsroom system type.
(If iNEWS is the selected NRCS type, ignore this step)
Enter Mos ID. This is a mandatory field if you select NRCS type ENPS, Octopus or Other.
Tip: To find your Mos ID, in the Manus Administrator console, type settings. For more details, see the Viz Mosart Administrator Guide, section Manus Administrator > Settings Editor MOS > NRCS Configuration.
Back in the Web Apps Configuration Tool App Configuration page for the NRCS Plugin, in section ACCESS MOSART TEMPLATES, specify the location of your Viz Mosart templates. This can be either
Local: By default, this is a local folder C:\channeltemplates. The tool will automatically scan for three files: channeltemplates.xml, avconfig.xml and newsroomsettings.xml. If successfully identified, a green validation message is displayed.
A network folder: When your template folder is on a network drive, click Choose folder and navigate to the target folder, and ensure the network folder has adequate permissions.
Database: If template details are stored in a database, enter host access and authentication details.
Click Save.
Template type filter buttons
The NRCS Plugin shows a row of filter buttons so journalists can narrow the template list to one type. You control which types appear, and in which order, from the NRCS Plugin page in App Configuration.
The available types are Camera, Clips, Voice over, Live, Graphics, DVE, Jingle, Telephone, Adlib, Break, Video wall, Sound and Accessories. Put the types your journalists use most first, and leave out the ones your production never uses, so the plugin only offers what is relevant.
Info: To complete the NRCS Plugin one-time setup, you will also need to visit the Server Configuration page.
Showmaker
Prerequisites
A running Viz Mosart 5.14.3 or later.
Manus Administrator is running.
The Viz Mosart client UI is running and can display a rundown.
If either Manus Administrator or Viz Mosart is down, start them now. You only need to do this once after a server reboot.
Info: Users can run Showmaker standalone without a connected Viz Mosart. This user scenario would be for early versions of a rundown (running order) where structure is being drafted, rather than operations verified.
MOS communication settings
Showmaker uses standard MOS protocol. These configurable properties define the communication.
A fresh installation has one MOS device pointing to your Mosart server: a single row in the MOS DEVICES table. While the table has exactly one device, the row also carries the control for handing the matching settings over to Manus Administrator, described below.
To establish communication between a single MOS device and Showmaker
There are two alternative setups, depending on your network structure.
Showmaker is installed on the same server as Viz Mosart
If you are running Showmaker on the same server as the Viz Mosart server, the Configuration Tool can write the matching MOS configuration into Viz Mosart for you.
From the App Configuration page, select Showmaker.
Review the values in MOS COMMUNICATION SETTINGS. If necessary, adjust the defaults by referring to the table below.
On the MOS device row, open the Manus Administrator settings control. With a local Viz Mosart server detected, it lets you inspect the changes and push the settings to Manus Administrator.
A warning reminds you that Manus Administrator must not be running at this point. Ensure Manus Administrator is closed before continuing.
To complete the action, click Confirm.
Info: Before anything is written, a backup of the current Manus Administrator settings is created at C:\ProgramData\Mosart Medialab\ConfigurationFiles, so the previous configuration can be restored.
Showmaker is installed on a separate server from Viz Mosart
If you are running Showmaker on another server than the Viz Mosart server, Viz Mosart must be set up manually for connecting to Showmaker:
Review the values in MOS COMMUNICATION SETTINGS and, if necessary, adjust the defaults as presented in the table below.
On the MOS device row, open the Manus Administrator settings control. With no local Viz Mosart server detected, it opens the Settings for Manus Administrator dialog, showing the values to enter on the Viz Mosart server.
On the Viz Mosart server, in the Viz Mosart Manus Administrator console, type settings.
From the Settings menu that appears, navigate to the section MOS.
Configure the MOS settings as presented in the Settings for Manus Administrator dialog in the Web Apps Configuration Tool.
Click Save.
(optional) If changes do not appear immediately, restart the Windows service Vizrt.Mosart.WebApps.Server.
Default values and multiple MOS devices (main/backup or multiple studios)
Table Property | Description |
|---|---|
NRCS ID | This is the Newsroom System ID for Showmaker. Set this ID on any MOS-enabled NRCS device to establish communication with Showmaker. For Viz Mosart, this value must be set in Viz Mosart Manus Admin. Default: SHOWMAKER.MOS. |
Add MOS Device | For defining multiple MOS devices. Click Add MOS Device and follow the guidelines in this table. |
MOS Device ID | This is the ID of a MOS device configured to communicate with Showmaker. For Viz Mosart, copy this value from Manus Admin console > Type settings > MOS section. Default: MOSART.MOS.SHOWMAKER. |
MOS Device URL | The URL for connecting to a MOS device. For a Viz Mosart server, the URL is ws://mosart-server-host:10540/mos/mosartsocket. The port in the URL (10540) is the MOS lower port configured in the Settings menu of Manus Admin, under the MOS section. Default: ws://localhost:10540/mos/mosartsocket. |
Studio | The Studio label that this device belongs to. Type a new name to create a Studio. A Studio is a label that groups one or more MOS devices, representing one production environment: typically a main Viz Mosart server with an optional backup, or a single gallery in a multi-studio site. The Studio exists as long as at least one MOS device references it, and disappears when no device uses the name anymore. Once Studios are configured, each show (and optionally each rundown) can be assigned to a Studio, and that assignment governs which Mosart server or servers the rundown is sent to. Failover without downtime: main and backup Mosart servers under one Studio means a failover keeps the same Showmaker rundowns on air. Per-rundown overrides: a show defaults to one Studio, but individual rundowns can be reassigned, shown with an orange badge in the UI, which is useful for rehearsals or last-minute changes. |
Examples | Typical configurations: One studio with main + backup: two rows with the same Studio label and the same MOS ID, and different URLs ( |
Feature settings
Story Recorder
Story Recorder lets operators mark stories for recording in Viz Mosart, optionally publish the resulting clips to online platforms (only available with TriCaster) 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, under App Configuration, select Showmaker, scroll down to Feature settings and turn on Enable Story Recorder controls.
Once enabled, every story in Showmaker contains Record / Publish actions and a Use recording toggle. For how operators use these controls, see Working with Showmaker.
Asset integrations settings
If you use either Viz Pilot or Viz Flowics to provide assets for your show, you need to configure some one-time settings. The integrations are displayed in the Showmaker integrations sidebar together with the Mosart web app, NRCS Plugin.
Info: These integrations appear in the Showmaker integrations sidebar as selectable, embedded MOS plugins (iFrames). They communicate directly with Showmaker in the browser using MOS messages, so no additional server-side configuration is required beyond specifying the URL and MOS Plugin ID.
Viz Pilot: to enable Viz Pilot graphics in the Assets panel
If you will run Showmaker with assets from Viz Pilot, select the checkbox for VIZ PILOT GRAPHICS AND ELEMENTS.
By following the on-screen information icon, provide values for
Application URL: Where Viz Pilot Edge is running. Default: http://localhost:8177/app/pilotedge/pilotedge.html?mosid=pilot. Enter the host of your Viz Pilot Edge installation, if not on the same machine.
MOS Plugin ID: The MOS ID that Viz Pilot Edge announces. Default: PILOT. This value must match what your NRCS / Mosart side anticipates.
Click Save.
Viz Flowics: to enable Viz Flowics graphics
Select the checkbox for VIZ FLOWICS GRAPHICS and ensure you have your Viz Flowics (cloud application) credentials to hand.
By following the on-screen information icon, provide values for
Integration token: A token issued by Flowics support. It is stored encrypted and displays as
************after saving.Application URL: Where Viz Flowics is running.
MOS Plugin ID: Default: flowics.com.mos. Change only if your NRCS / Mosart side anticipates a different id.
Click Save. Viz Flowics now appears as a tab in the Showmaker Assets panel.
Info: To complete the Showmaker one-time setup, you will also need to visit the Server Configuration page.
Named Overlays Editor
The Named Overlays Editor has its own page in App Configuration, where you register the graphics plugin it offers in its provider panel. Configure the Viz Pilot Edge plugin here with a display name, the MOS ID to stamp on overlays created from it, and the plugin URL.
The plugin panel is optional. With none configured, the editor still works for creating custom overlays by hand and for XML import and export. For everything else about the app, see Setup and administration NOE.
Template Editor (Early Access)
Please refer to the section Setup and Administration of Template Editor.