Creating a WebRTC Monitor in Axia Altus

Updated by Bryan Jones


This document applies only to the Axia Altus virtualized console and specifically shows you how to set up a WebRTC monitor.


With the Altus virtualized console, you are often not "local" to the console, which can present a challenge to hear the monitor speakers that we would otherwise hear if we were sitting in a more traditional studio. In this example, we're not "contributing" to the show, simply running the console. If you are a contributor and have your own source on a fader, you won't require a WebRTC monitor, as your return audio is provided as a normal backfeed.

In our example, we will set up a CR Monitor feed.

Creating the WebRTC feed

  1. In the Web Page of your Altus console, click on Outputs located under the Configuration section of the left side menu.

In our example, you see that output # 8 is already the CR Monitor feed but set up for multicast. We're going to leave that and create a second output using one of the other outputs.

  1. Change one of the unused outputs to CR Monitor. We'll use Talk to CR since it's not needed in this configuration.
  2. Click the Apply button at the bottom of the page. Note that the options on the Output 11 line will change when you do this. The Name Override is automatically populated with a WebRTC room name. You can change it; however, keep in mind that room names must be unique on whatever server you use for WebRTC.
  3. Change the Payload Type from Disabled to one of the choices from the list. We'll use 128k Stereo.
  4. Click apply at the bottom of the page.
  5. You now have a Monitor link on the right side. Click this link.
You might be tempted to right-click and try to "copy link." That doesn't work here. You need to click the link to open the player. You can copy the link from there.
Before you click CONNECT on the player, click the gear icon and choose your sound card. It will use the system default, but you need to make your choice before you connect.

Let us know how we can help

If you have further questions on this topic or have ideas about improving this document, please contact us.

How did we do?