Most settings here are needed when you install the Mosart Web Apps bundle on a separate server to the Viz Mosart server, move the Web Apps to a different server, or need to define the Viz Mosart backup server. For securing the connections, see HTTPS and Certificates and Authentication.
Server addresses
Under the automatic proxy setup, all default settings are pre-filled and no further action should be necessary. If you need to change any values:
MOSART MAIN SERVER, Address: By default, this field contains the address of the Mosart Web Applications. Enter the hostname, IP address, or FQDN of the main Viz Mosart server if located on another machine.
MOSART BACK-UP SERVER: When running Viz Mosart with a backup for redundancy, select the checkbox and enter the hostname, IP address, or FQDN of the backup Viz Mosart server.
PROXY WEB SERVER, Address: Hostname or IP address of the machine where the Mosart Web Applications are installed. The system attempts an auto-detect. If the FQDN is required (for example, by a certificate), provide this instead.
Click Save after changes.
Mosart API Access
The Authorization Key is the Viz Mosart server's REST API key, configured on the Mosart server under Remote Controller Service > Security. When the Mosart server runs in API-key mode, the web proxy attaches this key to the calls that need it, so the browser never sees the key itself. It is used for:
The Named Overlays Editor: reading and writing named overlays, including the Sync to backup server function.
Clip search against older Viz Mosart servers (before 5.16). From Viz Mosart 5.16, clip search uses the server's live connection and does not need the key.
Availability checks the Configuration Tool itself runs, for example whether the Mosart server's settings editor is reachable.
Note: The same key is sent to every Viz Mosart server the Web Apps talk to: main, backup, and every studio's servers in a multi-studio installation. All of them must therefore be configured with the same REST API key.
Info: With OIDC authentication enabled on the Mosart servers, the REST API key is not accepted there and this field is not used: the apps send the signed-in user's token instead. See the Authentication page.
Media Sequencer
Smart Panel can drive a Media Sequencer directly, for button actions that take an MSE graphic and for Asset List widgets that read their content from a Media Sequencer playlist or show.
Under MEDIA SEQUENCER, enter the Address of the Media Sequencer and its REST API Port. The default port is 8580.
Viz Arc
Smart Panel buttons can execute Viz Arc actions. To make them available, enter the Address and Port of the Viz Arc REST web service under VIZ ARC. The default port is 9004. The Configuration Tool probes the host as you type and reports whether the service answers.
Note: The Viz Arc REST web service must be running on that host, and it requires its own licence. The Web Apps server calls Viz Arc on behalf of the browser, so only the Web Apps host needs network access to it.
Video Clips
Video clips (PACKAGE templates) can be presented with various details. This setting controls how clips are labelled in the web apps that list them, such as Smart Panel. Select what to display from the dropdown menu.
TriCaster Live Previews
If your studio uses a TriCaster, Smart Panel can show its video inputs and outputs as Live previews. The Mosart web server proxies the streams on behalf of the browser, so it needs the TriCaster address and a user account.
In the Configuration Tool, open Server Configuration and scroll down to TRICASTER FOR LIVE PREVIEW.
Enter the TriCaster Address and the Username / Password of an account with access to the TriCaster web browser URL.
After this, TriCaster sources become selectable as preview sources in the relevant Web App.
Info: NDI sources need no configuration here. Mosart Web Apps discovers NDI sources on the network itself, so a Smart Panel live video element can list and preview them directly. The Web Apps host needs the NDI Runtime installed.