# Riedel MediorNet

> How a Riedel MediorNet connection exposes its video, audio, data, multi-channel audio and GPIO matrices and the NONE source in Buttons.

A Riedel MediorNet connection lets Buttons route the MediorNet system's matrices. Each source and destination is a single port, so there's nothing to configure in Buttons beyond the connection itself.

| Matrix | Routed as | Port names |
| --- | --- | --- |
| Video | Video | **In** and **Out** with the port number, for example **In 1101** |
| Audio | Audio | **Audio In** and **Audio Out** with the port number, for example **Audio In 4001** |
| Data | Data | **Data In** and **Data Out** with the port number |
| Multi Channel Audio | Audio | **Multi Channel Audio In** and **Multi Channel Audio Out** with the port number |
| GPIO | Data | **GPIO In** with the port number, only on units that have GPIO targets |

The number is the port's number on the MediorNet system. Each matrix uses its own number range, so the ports don't start at 1. For example, audio ports can start at 4001 while video destinations start at 2001.

Each matrix is its own routing domain: a source routes only to destinations in the same matrix. Buttons offers a matrix only when the MediorNet system reports targets for it.

<callout color="gray" title="Note">
  The Audio, Data, Multi Channel Audio and GPIO matrices need Buttons 1.8.11 or later. Earlier 1.8 releases route only the Video matrix.
</callout>

## Before you begin

- A Riedel MediorNet connection already added and connected, running module version 1.3 or 1.4. 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.
- Access to **Connect → Connection** to check configuration, and to **Routing** to take and verify routes.

## Sources, destinations and names

Buttons reads the inputs and outputs of each matrix from the module, with the names set on the MediorNet system shown next to them. Video ports keep the names they had before the other matrices were added, so existing routes and routing Presets still work.

Buttons reads the current route of every output back from the system, so routes taken elsewhere also appear in Buttons.

## Clear a route with NONE

Each matrix's source list includes its own **NONE**. The Video matrix's is named **NONE**; the others carry the matrix name, for example **Audio NONE**. Routing **NONE** to a destination clears its route on the MediorNet system, and releasing a route uses the **NONE** of that destination's matrix.

Two more entries, **INTERRUPTED** and **FOREIGN**, can show up as a destination's current source when the MediorNet system reports that state. Outside the Video matrix they also carry the matrix name, for example **Audio INTERRUPTED**. They aren't sources you can route yourself.

## Locking

The Riedel MediorNet integration doesn't support destination locking, so no lock or unlock controls appear on its destinations.

## If you get stuck

| What you see | What to try |
| --- | --- |
| A destination shows **INTERRUPTED** or **FOREIGN**. | That's the state the MediorNet system reports for the route. Check the route on the MediorNet system itself. |
| 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.
- [Take a physical route](/docs/buttons/v1.8/routing/take-a-route).
- [Understand route status](/docs/buttons/v1.8/routing/understand-route-status).
