A multi-studio site runs one central Mosart Web Apps host against several Viz Mosart back ends. The Studios page in the navigation sidebar is where you define them.

Note: Multi-studio support is being delivered in stages. The applications differ in how far they support it today, so check Studio support per application below when planning a multi-studio installation.

Defining studios

The page is headed Studios with a count of how many are defined, and describes itself as mapping each studio to a Viz Mosart server backend and an NRCS, so that studios become routable targets across the Web Apps. The table columns are a row number, STUDIO, HOST, PORT, NRCS DEVICE and BACKUP.

Each studio entry takes:

  • Studio name: the label used throughout the Web Apps to identify this production environment.

  • The Viz Mosart server hostname or IP for that studio, and its port.

  • An optional Backup server, added with Add backup in the BACKUP column, which opens a Backup server sub-row beneath the studio with its own host and port. A plain shield icon marks a studio that has a backup, and a shield with a check marks the backup row itself.

  • An NRCS device, selected from the devices you have configured.

Use Add Studio to create further entries. A new row arrives pre-named studio-<n>, pre-filled with the current default Mosart port and the first available NRCS device.

Studio names become URL slugs

On save, a studio's name is normalised to a URL-safe form: lower-cased, with every run of other characters turned into a single hyphen. Studio 1 is stored and displayed as studio-1.

That slug is the studio's identity everywhere. The proxy routes it as /mosart/<studio>/…, the Home page launches studio-scoped apps with ?studioId=<studio>, and it is the label on the Home page's studio strip. Two names that normalise to the same slug are rejected while you type, with Name must be unique (collides with another studio). So choose names that read well in lower case with hyphens, and expect the tool to rewrite what you typed.

What the page validates

Entries are validated as you type, and the messages appear on the row itself:

  • Between studios: two studios may not point at the same Viz Mosart backend, meaning the same host and port together. Two studios on the same host with different ports are allowed. The check resolves host names, so a short name, its FQDN, localhost and the machine's IP all count as the same machine.

  • Within one studio: the rule is stricter. The backup must be on a different host from the main server, since a pair on one machine is no redundancy at all.

  • A host must be a hostname or IP address with no scheme, port or spaces, and a port must be a number from 1 to 65535.

Save is blocked while the conflict check is still running, so a clash cannot slip through by saving quickly.

With more than one studio defined, the Home page gains a studio selector: studio-scoped applications launch against the selected studio and connect to that studio's Viz Mosart server, while applications that work across studios are listed under Cross-studio. A single-studio installation keeps the flat layout.

Info: The Configuration Tool retargets the Mosart port on every studio row when you change certificate mode: 55168 when you supply your own certificate, 55167 otherwise, because the Viz Mosart servers serve HTTPS only with a custom certificate. It only moves a port that still holds one of those two defaults, so a port you typed yourself is left alone and has to be updated by hand. This applies to each backup port as well. See the HTTPS and Certificates page.

Studio support per application

Application

How it uses studios

Rundown Viewer

Launches per studio, and can switch studio from a picker in the timers bar.

Smart Panel

Launches per studio from the Home page. Panel layouts are shared by the installation.

Prompter

Launches per studio from the Home page.

Named Overlays Editor

Has its own studio selector in the header toolbar, and works against the selected studio's Mosart server.

Showmaker

Assigns each show, and optionally each rundown, to a studio, which decides where the rundown is sent. Its studio list comes from the Showmaker MOS devices in App Configuration; the NRCS device field on this page links a studio to that device.

Showmaker is grouped under Cross-studio on the Home page because it works across studios, but launching it from Home still carries the selected studio: the tool follows that studio's NRCS device to the MOS device's Studio label and passes it, so Showmaker opens filtered to that studio's shows. A studio with no NRCS device set launches Showmaker unscoped, which is why the NRCS DEVICE column matters even on a single-studio installation.

NRCS Plugin, Template Editor

Work across studios, against the installation's template source.

Editing a studio's Mosart server settings

Mosart Server settings under Help & Resources opens the settings of the installation's main Viz Mosart server only. A studio's own server, and any backup server, are not reachable from there.

To edit the settings of any other Mosart server, open the settings on that machine from a Viz Mosart desktop application: in Manus Administrator, type settings in the console, or in AV Automation use Devices > Settings. This is also the way to edit settings when OIDC authentication is enabled on the Mosart servers, because the browser-based editor has no sign-in of its own. See Configuration Tool.

Note: Settings that must match across a studio's pair, HTTPS and authentication in particular, have to be applied on the main and the backup server separately, and the Mosart Remote Control Service restarted on each. A configuration that works until a failover is usually a backup server that was never updated.