creating Infinity IFBs that include Axia Console backfeeds

Scope

This document covers the use of Codecs defined on an Axia consoles as part of an IFB on an Infinity intercom.

This document was created using Infinity 3.0 and with Dashboard version 3.0.111.

Description

When using an Infinity intercom system it may be desirable to have a Codec that is used on an Axia console also appear on a Panel so that producers, directors, or others may interact with that codec simultaneously.  

We’re using a Telos Z/IP One for this example. but it can be any codec, Livewire or not.  For example a Tieline Gateway, Comrex Access, or even Microsoft Teams or Zoom using an Axia IP audio driver.

Prerequisites

The sources to and and from your codec must appear in the Infinity Dashboard software as inputs and outputs.  

If they do not appear refer to this This section for more info

Infinity IFB

A bit about IFBs

IFB stands for nterruptible Foldback or Interruptible Feedback which is a communication system that allows a producer or director to talk directly to on-air talent through an earpiece or headphones without being heard by the audience.  This generally “interrupts” the normal feed.

In an Infinity system an IFB has;

• A unique identifying name

• Four user definable “dim” settings from none to full cut (for example a director might fully cut the audio while other users may only dim the audio).

• An input (this is generally the normal backfeed that comes from the console.  This is what the remote hears when no one is talking)

• A Reverse input (this is the audio from the remote so that the Infinity Panels can hear it).

• at least one output (this is the audio that goes back to the remote).

• at least one panel assigned to one of the Levels.

Configuration

1. Click the IFB tab listed under Inputs, Outputs, and GPI on the right side of Dashboard.  Any existing iFBs are displayed.

2. Click the ADD button.

3. Assign a friendly name.

4. Set your desired Dim Levels.

5. Set desired Button and text colors.

6. Click ADD

   

A new, blank IFB with the name ZIPOne is displayed.

in the next section, Inputs and outputs are from the point of view of Infinity. For example, the TO: source mix minus backfeed from Quasar is an INPUT to the Infinity system.

1. On the Inputs tab on Dashboard, Locate the TO: source backfeed from your console (you can type To: in the search) and drag it to the Input box on the IFB.

2. On the Inputs tab on Dashboard, locate the main audio FROM your codec (not the To: source) and drag that to the Reverse box on the IFB.

3. On the Outputs tab on Dashboard, locate the output to your codec and drag it to the Outputs box on the iFB (note a second, blank, output box is added automatically)

4. From the Panels list on the left side of Dashboard, drag at least one panel to one of the levels boxes. (note when you add a panel to a level a new blanks spot is added, allowing you to have more than one panel on each level)

5. Repeat step 4 until all panels that need to interact with this IFB are added.

Add the IFB to your panels and configure it’s options

1. On the left side of Dashboard in the Panels section, locate the first panel.

2. Drag the IFB Icon (in our example the yellow ZIPOne icon) to a key on your panel

3. Double click on the key you just added the IFB to.

4. Recommend setting the Key mode to Talk & Auto Listen (this means while you are talking you are also listening to the remote).

5. Recommend setting Key Latching to Auto Listen but NOT Talk. (this allows short tap up on the key to constatanly monitor.  allowing Talk latch could permanently interrupt the feed to the remote)

The behavior of this configuration is that when you talk, the key will remain in listen mode.  You can short tap up on the key to latch and unlatch the listen function.   To turn off the automatic latching of the listen function, remove the Auto Listen Key Latching option.

Some final important notes

Take care to make sure your system can support the number of IFBs you are creating.  Each Panel can create eight renders. In a system with a single Panel (Hardware or VIP) you would be limited to eight tTOTAL Groups, IFBs, or Party Lines as each requires a renderer.  Even two panels is not sufficient to support more than eight total as one panel will be a primary render and backups will be created on the other.   Please contact us for guidance if you have more than eight.

The TO: source from the console is only created when the source Profile on the console is of the Codec type, and is only created when the codec is loaded on a fader.  To this end, if you have never loaded the codec on a fader the TO: source will not appear in dashboard. Create you codecs first then load them on a console so they can be discovered by dashboard THEN build your IFB.

Each console will create a backfeed.  So it’s possible you might have your codec listed in Dashboard from more than one console.  This is okay.  A backfeed is a backfeed regardless of where it comes from.  It does not matter which consoles TO: source you drag to the input of the IFB.

When you drag your Output to the IFB output, Dashboard will automatically configure that Destination with the right renderer channel for that IFB.  You must leave this and not change it.  If you change it by any means (manually, via Pathfinder or an Automation system) Dashboard will remove the output from the IFB configuration.  You will need to come back to the IFB and re-add it if this happens.