# TAG Video Systems MCS

> How a TAG Video Systems MCS connection routes inputs to layout PIPs and layouts to outputs, and how many PIPs each layout offers.

A TAG Video Systems MCS connection lets Buttons route the MCS multiviewer: which input each PIP of a layout shows, and which layout each output shows. Buttons reads the inputs, layouts and outputs from the MCS, so operators can change a multiviewer from a Router Section the same way they take any other route.

<callout color="gray" title="Note">
  Needs **Buttons 1.8.13** or later and **TAG Video Systems MCS module 1.1 or 1.2**. Buttons 1.9.2 and earlier 1.9 releases don't include this integration.
</callout>

## Before you begin

- A TAG Video Systems MCS connection already added and connected, running module version 1.1 or 1.2. See [Update a connection's module safely](/docs/buttons/v1.8/connections/module-compatibility) if you need to check or change the installed module version.
- **Enable Layout Variables** turned on in the module's settings, so Buttons can show which input each PIP shows.
- Access to **Connect → Connection** to check configuration, and to **Routing** to take and verify routes.

## How the MCS maps to routing

The MCS has two separate kinds of routes, and Buttons keeps them apart:

| Source | Destination | What a route does on the MCS |
| --- | --- | --- |
| An input | A PIP of a layout, named after the layout, for example **Quad PIP 2** | Puts the input in that tile of the layout (the module's **Modify Layout** action) |
| A layout | An output | Puts the layout on the output (the module's **Apply Layout** action) |

Each kind is its own routing domain: an input routes only to PIPs, and a layout routes only to outputs. Buttons never offers a layout for a PIP or an input for an output.

Every port is video only. The MCS sets an output's audio apart from its layout, and Buttons doesn't route audio on this connection.

Routing an input to a PIP changes the layout on the MCS, but doesn't put the layout on an output. To show the layout, route it to an output.

## Set how many PIPs each layout offers

Module versions 1.1 and 1.2 report how many tiles a layout has only once that layout has been on an output since the connection started. Until then, Buttons offers a fixed number of PIPs for the layout:

1. Open **Connect → Connection** and select the MCS connection.
2. On the **Config** tab, set **PIPs per Layout** to the number of tiles your layouts usually have. The default is 16, and the range is 1 to 64.
3. Save.

Once the MCS reports a layout's tile count, Buttons offers exactly that many PIPs for the layout and updates the ports. A layout the MCS reports as empty offers no PIPs.

These module versions don't report tile numbers either, so Buttons numbers a layout's PIPs from 1 in the order the MCS lists its tiles.

## Routes taken elsewhere

Buttons reads back which input each PIP shows and which layout each output shows, so changes made on the MCS or from another controller also appear in Buttons. A PIP with an empty tile, or an output without a layout, shows no source.

If PIPs never show their current input, check that **Enable Layout Variables** is on in the module's settings.

## Locking and None source

The TAG Video Systems MCS integration doesn't support destination locking, so no lock or unlock controls appear on its destinations. It also has no None source for clearing a PIP or an output.

## If you get stuck

| What you see | What to try |
| --- | --- |
| A layout offers more or fewer PIPs than it has. | The MCS hasn't reported the layout's tile count yet. Put the layout on an output once, or set **PIPs per Layout** to match your layouts. |
| PIPs don't show which input they're showing. | Turn on **Enable Layout Variables** in the module's settings. |
| An input doesn't appear as a source for an output. | Expected: inputs route only to PIPs. Route the input to a PIP, then route that layout to the output. |
| One route in a take fails. | Buttons sends the routes one at a time, and a failed route only fails its own destination. Check the message in the [routing report](/docs/buttons/v1.8/routing/troubleshoot-a-route), then check the layout or output on the MCS. |
| No lock control appears on a destination. | Expected: this integration doesn't support locking. |

## Where to go next

- [Check what a router integration supports](/docs/buttons/v1.8/connections/router-integrations), for how this compares with other router modules.
- [Build a Router Section](/docs/buttons/v1.8/positions/router-sections).
- [Take a physical route](/docs/buttons/v1.8/routing/take-a-route).
- [Understand route status](/docs/buttons/v1.8/routing/understand-route-status).
