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. The options are Showmaker, iNews, ENPS, Octopus, OpenMedia and Other. Showmaker is in the list because Showmaker itself can be the newsroom system.
Enter Mos ID. The field is shown for every NRCS type except iNews, so it applies to Showmaker, ENPS, Octopus, OpenMedia and Other. Its help text says the field is required when the newsroom system uses the MOS protocol. The tool does not block a save when it is left empty, so the value has to be right by inspection.
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. Location offers two options:
Local: a folder on this machine or on a network path. The default is
C:\channeltemplates. Use Choose folder to point it at a network drive, and make sure that folder has adequate permissions. The tool scans for three files,channeltemplates.xml,avconfig.xmlandnewsroomsettings.xml, and reports the folder as valid or invalid as you type.Database: if template details are stored in a database, enter host access and authentication details.
A save is refused while the folder is invalid, which is the one validation this tab enforces.
Underneath the fields, CONFIGURE NRCS PLUGIN shows a Preview URL with a copy button beside it. That is the URL to hand to the newsroom system: the Web Apps address plus
/plugin, withnrcs=<type>appended for every type except Other, andmosid=<value>for every type except iNews. Click the link to open it in your default browser and confirm the plugin loads before you configure the newsroom system.Click Save.
Template type filter order
The NRCS Plugin shows a row of filter buttons so journalists can narrow the template list to one type. The control that governs them is Template type filter order, under UI SETTINGS on the NRCS Plugin tab.
It lists all thirteen types, namely Camera, Clips, Voice over, Live, Graphics, DVE, Jingle, Telephone, Adlib, Break, Video wall, Sound and Accessories, and you reorder them by dragging a row or using the up and down arrows. Put the types your journalists use most at the top.
When the templates come from a local folder and its newsroomsettings.xml names an alias for a type, that row is labelled with your newsroom's own name instead of the name above. Types the file does not name keep the names above, as do installations that store the templates in a database, where there is no file to read.
Note: This sets the order only. There is no way to hide a template type: any type missing from the saved order is appended in default order, so every type always reaches the plugin. The order applies to everyone using the plugin, and the ALL filter always stays first.
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.
Connection settings
Showmaker uses standard MOS protocol. The Connection settings heading on the Showmaker tab covers two blocks, MOS COMMUNICATION SETTINGS and MOS DEVICES.
A fresh installation has one MOS device pointing to your Mosart server: a single row in the MOS DEVICES table, whose columns are ID, URL and Studio. While the table has exactly one device, the row also carries the control for handing the matching settings over to Manus Administrator, described below.
The add and edit dialog labels the same three fields ID *, URL and Studio *. A new device pre-fills Studio with Default, and the URL is pre-filled with the local Mosart address only for the very first device.
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.
Click the icon button in the last column of the MOS device row. It appears only while the table holds exactly one device. With a local Viz Mosart server detected and changes to make, it opens Inspect changes and push settings to Manus Administrator, showing current and new values side by side.
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.
Click the icon button in the last column of the MOS device row. With no local Viz Mosart settings found, it opens the Settings for Manus Administrator dialog, which simply lists the values to type on the remote server, with OK to close.
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 Mosart Web Applications (service name MosartWebApplications).
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. |
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. |
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 a rundown gains a record control; stories in a rundown template do not. The publish action and the Use recording toggle appear on a story only once that story has a recording. With authentication enabled, only a user with the showmaker-admin role can operate these controls: a viewer sees the record state and the Use recording toggle but cannot change them, and the publish action is not shown. For how operators use these controls, see Working with Showmaker.
Assets 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.
Prompter integration settings
Below the asset integrations, Prompter integration settings carries a LEGACY MOS 2 PROMPTER (SOCKET) checkbox. Enable it and four fields appear: Prompter host / IP, Lower port, Upper port and Prompter MOS ID. Showmaker then dials out to a prompter that speaks MOS 2 over TCP and pushes the running order and script to it.
Field | Default |
|---|---|
Prompter host / IP |
|
Lower port |
|
Upper port |
|
Prompter MOS ID |
|
Note: On the prompter's own MOS settings, set its remote NCS ID to the NRCS ID configured above, and use the same Prompter MOS ID. Only rundowns activated for a MOS device are sent.
Info: To complete the Showmaker one-time setup you will need two other pages: Studios, for the Viz Mosart server and optional backup that Showmaker's rundowns are sent to, and Server Configuration, for how browsers reach the Web Apps. The Mosart main and backup server fields are no longer on Server Configuration; they live on Studios.
Named Overlays Editor
The Named Overlays Editor has its own tab in App Configuration, with a single block, Assets integrations settings. It carries a VIZ PILOT GRAPHICS AND ELEMENTS checkbox and two fields, Application URL and MOS Plugin ID. There is no display name to set: the plugin is always registered as Pilot Edge.
The first time you open this tab, the tool registers a Pilot Edge entry for you. It copies the Showmaker tab's Pilot Edge settings if one is configured there, and otherwise uses the defaults http://localhost:8177/app/pilotedge/pilotedge.html?mosid=pilot&sendbutton with MOS Plugin ID PILOT.
Clearing the checkbox is what leaves the editor without a provider panel. It then 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)
The Template Editor tab is where the app is switched on. The Template Editor ships switched off, and ENABLE TEMPLATE EDITOR at the bottom of the tab is what turns it on. Above the switch, the tab states the three things to know first:
Explore and test: this is an early-access build, and it is not supported for production use.
Backup: it shares the NRCS Plugin's template storage and supports file-store templates only, so back up your channel templates XML before you start.
Control access: as a web app it is reachable by everyone on the network unless authentication is configured.
For the full procedure, including what happens on save and how to open the app, see Setup and Administration of TE.
Smart Panel
The Smart Panel tab is the last of the five, and it governs how Smart Panel writes its two clock values, Time of Day and Next Break Time. Smart Panel reads these settings once, when it starts, so reload any panel that is already open after you save.
Time format
The TIME FORMAT block decides how those two values are written. Use browser default is selected out of the box: the clocks then follow the language settings of the browser on each Smart Panel machine, always with a two-digit hour. A Preview beside the checkbox shows the current time written the way the panels will write it, so you can check a choice before saving.
Clear Use browser default to set the format explicitly. This is what you need when the operator's Windows regional format differs from the browser's language, because a browser cannot read the Windows Regional format setting. Four controls appear:
Regional format: a searchable list of the regional formats Windows offers on the machine running the Configuration Tool. The choice decides the separators and the AM and PM text.
24-hour or 12-hour. The default is 24-hour.
Leading zero: on by default, so the hour is always written with two digits.
Use this PC's settings: fills the three controls above from the Windows regional format of the PC running the Configuration Tool, which saves finding it in the list.
Time zone
The TIME ZONE block decides which clock the two values follow:
Local (browser), the time zone of each Smart Panel machine. This is the default, and it is what you want when studios or control rooms sit in a different time zone from the Viz Mosart server, so a presenter's clock reads the time where they are.
Mosart server, the time zone of the Viz Mosart server. Choose this when everyone should read the same clock as the automation system, wherever the panel is opened.
Note: These settings need a matching Viz Mosart server version. Against an older server the clocks keep their previous behaviour, showing the Mosart server's wall clock in that machine's own 12 or 24 hour format.
For what an operator sees, see the Timer section of Working with Smart Panel.