---
title: "Creating a Fader for a Remote Console's Program Audio with Talkback"
slug: "creating-a-fader-for-a-remote-consoles-program-audio-with-talkback"
updated: 2024-12-13T10:46:43Z
published: 2024-12-13T10:46:43Z
canonical: "docs.telosalliance.com/creating-a-fader-for-a-remote-consoles-program-audio-with-talkback"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a Fader for a Remote Console's Program Audio with Talkback

## Scope

This article applies to the Fusion and Element console systems using the Studio Engine or Powerstation platforms running version 3 or higher.

## Description

Sometimes we need on-air contribution from a console in another control room. The easiest way to do that is to create a source profile in the air console for the remote console's program bus. Then load that profile to a fader on the air console. But what if we want to use that channel's Talkback button to communicate with the remote studio? This is where some custom configuration is needed.

If you have Pathfinder Core Pro, you can [try the procedure here](/v1/docs/using-pathfinder-to-trigger-talkback-in-a-fusion-or-element-console-remotely).

If not, it'll require an available VMix and will use up one of the External Monitor inputs on the remote console. Here, we'll be explaining how to create a backfeed for the fader on the air console that can be loaded onto the remote console as a monitor source.

## Create a Source Profile on Air Console:

1. Create a source profile on the air console that will receive the main program buss from the remote console.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/74a88bc1-eb36-4506-a37a-0b2a45e83e2d.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A54%3A40Z&se=2026-11-07T18%3A54%3A40Z&sr=c&sp=r&sig=XmgtvwecXtF2XVYv0YddwO3BAKYU9dBpxpwM5grLDEs%3D)

> [!WARNING]
> **Notice:** In our example, the remote console's program 1 buss is on channel **10101**

1. Next, set **Feed to Source** to **Custom**.

You'll see a box full of options show up to customize the backfeed:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/c3dabe6f-243f-4821-90c5-8d971b60eb41.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A54%3A40Z&se=2026-11-07T18%3A54%3A40Z&sr=c&sp=r&sig=XmgtvwecXtF2XVYv0YddwO3BAKYU9dBpxpwM5grLDEs%3D)

You can select **Program 1** under the parameters you want for the local channel, or you can enter your main pre-delay air feed or main air program buss channel number into the **External Feed Src** field and select **External** for each of the conditions for the fader channel instead of **Program 1**. It really depends upon what you want the remote console to monitor.

Make sure to check the check boxes under each to enable **talk insertion** and **Dim Gain**.

1. **Apply** changes.

## Create a VMix

to convert the backfeed we just configured to a regular source the remote console can use for monitor.

1. Go to the **V-Mixer** page in your engine and choose an available channel

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/fcbf2ec8-e2bf-4566-a5f6-efd5ff3b64d6.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A54%3A40Z&se=2026-11-07T18%3A54%3A40Z&sr=c&sp=r&sig=XmgtvwecXtF2XVYv0YddwO3BAKYU9dBpxpwM5grLDEs%3D)
2. Set the **Input Selector** to **EXTERNAL**
3. Enter the channel number for the source we just created (10101) into the **Channel** Field
4. Set **In Stream Type** to [**To Source**](/v1/docs/to-source-vs-from-source) (that's 10101's backfeed)
5. Set **Enable** to **On**
6. Give the output source a sensible name using the **Out Name** field
7. Enter an available Livewire channel number in the **Channel** field
8. Finally, set the **Out Stream Type** to **Live Stereo**
9. **Apply** your changes to the V-Mixer. (make sure you click the correct **Apply** button)

## Create a Source Profile on the Remote Console

1. On the remote console, create a **Line** source profile using the new Livewire channel we just created in the VMixer:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/7d026cd4-4ea1-4b39-9307-dde4f42a87a4.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A54%3A40Z&se=2026-11-07T18%3A54%3A40Z&sr=c&sp=r&sig=XmgtvwecXtF2XVYv0YddwO3BAKYU9dBpxpwM5grLDEs%3D)
2. Be sure that this new source is available for **CR Monitor**:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/3018e5a6-39df-4bf2-85d7-ad3733e7085f.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A54%3A40Z&se=2026-11-07T18%3A54%3A40Z&sr=c&sp=r&sig=XmgtvwecXtF2XVYv0YddwO3BAKYU9dBpxpwM5grLDEs%3D)

It might even be wise to disable all but **CR Monitor** so that it can't be pulled up on a fader.
3. **Apply** changes

## Set the New Source as an External Monitor Input

1. Go to the remote console's **Shows** page and select the appropriate show profile
2. Go to the Show's **Monitor Section**
3. Under **Sources for External 1 & 2**, select the new source profile under one of the **EXTERNAL Input**s:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/60dd65b0-5ffd-4871-a5ff-9c218768031e.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A54%3A40Z&se=2026-11-07T18%3A54%3A40Z&sr=c&sp=r&sig=XmgtvwecXtF2XVYv0YddwO3BAKYU9dBpxpwM5grLDEs%3D)
4. Save changes
5. Load the show on the remote console.

Now that this is set up, the remote console will need to be monitoring EXT 2 in order to receive talkback from the air console.

## Let us know how we can help

If you have further questions on this topic or have ideas about how we can improve this document, please [contact us](https://www.telosalliance.com/support-request).