Audio I/O routing within AERO units is very flexible. The flexibility may make the routing appear complex at first glance, but it is not difficult to master. The AERO.20, 200 and 2400 support AES67/SMPTE2110-30/31 I/O and have routing options that the AERO.10, 100 and 2000 units do not.
AERO.10, 100, 2000 System Setup
Do this before I/O Configuration
The first step in configuring I/O for these processors is to select the Clock reference.
NfRemote navigation: System > I/O Setup > Hardware I/O Setup
Click the Clock Reference dropdown
Select the reference clock
If SDI I/O is going to be used the selection should always be SDI
This ensures that de-embedding and re-embedding of audio is properly timed to the SDI signal itself.
Note that there are also some hardware selections here for troubleshooting these AERO units.
The Main page is where the audio clock sources are configured, along with Master Bypass and Motherboard Bypass controls, which are useful for troubleshooting purposes.
With the exception of the AERO.8000, the AERO units support several baseband audio reference clock options, including:
SDI Input #1
Analog VRef
AES3 Input #1
AES3 Input #4
AES3 Reference Input
Internal 48 kHz oscillator
The selected clock option sets the timing for the baseband signal path and the audio processing instance(s).
The AERO.20, AERO.200, and AERO.2400 support primary and secondary baseband clock sources. They automatically use the internal oscillator if neither primary nor secondary clock sources are available.
To configure clock and bypass controls for these processors:
Choose System > Baseband I/O > Main.
Figure 1: Baseband Audio Reference Clock configuration
Set the primary and secondary baseband audio reference clock sources using the respective drop-down menus.
(Optional) Click (highlight) the Master Bypass or Motherboard Bypass to bypass the respective controls (for example, when testing routing).
Master Bypass is a hardware relay bypass, so that the physical inputs directly connect to the physical outputs. This automatically happens when power is removed or it can be controlled via NfRemote or ASCII commands to the control port(s).
Motherboard Bypass disables all audio processing while keeping the I/O functionality the same. It is used for troubleshooting purposes.
If SDI I/O is used, the second step is selecting which audio channels will be re-embedded in the SDI output. The audio pairs re-embedded may be from the Instance’s processed outputs, AES-3 baseband sources or from the SDI source audio pairs..
NfRemote navigation: System > I/O Setup > SDI Embedding
SDI embedding is enabled by clicking SDI Embed button. An indicator will light yellow to confirm the selection
Clicking on any of the 8 dropdown menus allows a source selection for that embedded audio pair.
Also found here in the System > I/O Setup > menus are:
SRC Bypass. Click a source if it is desired that the source NOT be sample rate converted to match the selected reference clock. For instance a bit rate reduced (Dolby, MPEG, APT etc.) encoded source would not go through an SRC.
SDI Video Delay is set here: System > I/O Setup > SDI Video Delay
Note: Livewire+/AES67/SMPTE2110-30/31 are NOT supported in AERO.10, 100 and 2000 and these menus should not be used.
AERO.10, 100 and 2000 units have Livewire+ AES67 configuration submenus found in several locations. For example:
System > System > Livewire. Outputs > Livewire Stereo Output >. Instance > Output > Livewire.
AERO.10, 100, 2000 Input
NfRemote navigation: Instance 1 > Input > Source
Inputs selects the baseband source that is applied to the Instance’s DRCs.
All I/O are physical (baseband)
1 x SDI with 8 embedded audio pairs (16 channels)
4 x AES-3 unbalanced
AERO.2000 has an additional 4 x AES-3 I/O unbalanced I/O on a DB25 connector.
Each Instance input has a drop down menu.
Clicking an Input’s drop down displays all of the audio sources, for that AERO unit, which can be assigned to that Input.
Click on an audio source and the dropdown menu closes and the Input shows the chosen source.
The same source may be assigned to multiple inputs if desired.
Example of an AERO.10, 100 2000, AMX input selection: Input 7/8: SDI 7/8 or Input 9/10: AES 1/2
AERO.10, 100, 2000 Output
NfRemote navigation: Outputs > AES/SDI Outputs > AES Outputs (or SDI Outputs)
Each physical AES-3 and SDI output has a dropdown menu
Clicking an Output’s dropdown displays all of the Instance’s audio outputs, for that AERO unit, which can be assigned to each physical output
Click on an Instance’s output and the drop down closes and the Output shows the chosen output source.
An example of an AERO.10, 100 2000, AMX output selection: AES Out 1/2: Instance 1 Processed 1/2 or SDI Out 1/2: Instance 1 DD+ Out
Special Configuration Options
There are special configurations available for Instance outputs 7/8 and 9/10. These options provide support for SAP, automatic SAP replacement, DVS (descriptive Video Service), local emergency audio, and local program/commercial/interstitial program insert.
NfRemote navigation: Instance > Output > Output 7/8
Select 7/8 Mode = Normal to pass the 7/8 processed source to the 7/8 out
Select 7/8 Mode = Main Downmix to send a processed downmix (or stereo 1/2) out of 7/8 all the time.
Select 7/8 Mode = Auto Downmix to replace the 7/8 source with the Main downmix when the 7/8 source is not present.
Auto Downmix is used to maintain audio on the SAP channel when SAP programming is not present.
AERO.20, 200, 2400 Input
Connecting baseband (physical) sources to processing Core inputs.
NfRemote navigation: System > Baseband I/O > Core Input Source
This is where Baseband inputs (physical inputs from SDI de-embedding and AES-3 sources) are assigned to Core inputs.
Core inputs are the sources for the internal audio routing to processing and/or audio passthrough to outputs
There are a total of 18 baseband stereo Core Inputs.
Clicking a Core Input dropdown displays all of the baseband sources, for that AERO unit, which can be assigned to the Core Input
Click on an audio source and the dropdown menu closes and the Core In shows the chosen source.
The same baseband source may be assigned to multiple Core inputs if desired.
Examples of an AERO.20, 200 2400, AMX Core input selections: Core Input 1/2: SDI #1 1/2 or Core Input 17/18: Mute.
see Figure 2. Core Input Source, below.
Figure 2. Core Input Source
After assigning the Core Input sources the Instance Source selections can be made.
Connecting Core inputs to Instance inputs as sources
NfRemote navigation: System > Baseband I/O > Instance
Click Instance 1 or Instance 2 on the left
Click an Instance’s input or return pair (1/2 to 9/10 and Return A, B and C) dropdown to see all of the Core inputs that can be chosen an audio source for that Instance input.
The same Core source may be assigned to multiple Instance inputs if desired.
See Figure 3. Instance Source Selection, below.
Figure 3. Instance Source Selection
AERO.20, 200, 2400 Outputs
The main category, Outputs, in these processors is only for selecting what audio is heard in headphones, a stereo AoIP stream and/or a 5.1 AoIP stream used strictly for monitoring purposes. Monitoring points can be chosen from inputs, between processing sections, before Dolby encoding and after a Dolby decoder, in the Output subcategories. Selection of what baseband sources, and Core outputs, are sent to SDI 1, SDI 2, and AES-3 are made by navigating to the appropriate Baseband I/O selection in NfRemote.
The first step in selecting the sources that will be embedded in SDI #1, SDI $2 and AES-3 outputs is to select what sources are connected to the Core (processing and routing Core) outputs.
Selecting a Source for Each Core Out
NfRemote navigation: System > Baseband I/O > Core Outputs Source
The AERO.20, 200, 2400 processing Core has 17 pairs of outputs.
Clicking an Core Out dropdown displays all of the Instance output sources, for that AERO unit, which can be assigned to each Core Out.
Click on an output source pair and the drop down closes and the Core Out shows the chosen output source.
An example of a Core Output Source selection is Core Out 1/2: Instance 1 Processed 1/2
After assigning Core Out pairs to all of the needed output sources selection Core Outs can be assigned to SDI #1, SDI #2 and AES-3 Baseband (physical) outputs.
Selecting What Core Outs are embedded in SDI #1 and/or SDI #2, or sent to an AES-3 output.
NfRemote navigation: System > Baseband I/O > SDI #1 (or SDI #2 or AES3 Outputs)
Each SDI output has 8 output pairs.
There are 4 x AES3 main outputs and 4 x AES3 Aux Outputs. AUX outputs are available on the 2400 only.
Click SDI #1
Click on Audio in the bottom configuration window to see the SDI #1 audio pairs
Click the SD #1 Embed button to enable SDI #1 to embed Core outputs into the SDI signal.
Clicking any Core Out dropdown displays all of the audio output sources, for that AERO unit, which can be assigned to the SDI or AES-3 Output
Select a Core output pair and the drop down closes and the Output shows the chosen output source.
An example of an AERO.20, 200 2400, AMX output selection: Out 1/2: Core 1/2 or Out 15/16: Mute
Output Routing AERO.20, 200, 2400
Similar to the input routing, the output routing is handled in two stages:
Routing from an AMX processing instance output to the core audio output channels
Routing from the core audio output channels to the physical baseband audio outputs
There are some additional considerations regarding the output routing:
Audio Core Outputs 1-16 are dedicated to SDI #1 Output.
Audio Core Outputs 17-32 can be routed to SDI #2 Output.
Audio Core Outputs 19-34 can be routed to AES3 Outputs.
Notice that there is overlap between the SDI #2 and AES3 Outputs. This must be considered when planning the unit configuration and routing.
To configure output routing:
Choose System > Baseband I/O > Core Output Source to navigate to the Core Output Source routing page. This is where you route an AMX instance output to the audio Core Out channels
Route an AMX instance output to the core audio output channels using the Core Output drop-down menus.
Navigate to the output page for the desired physical output and then configure the routing using the drop-down menus.
For SDI #1 outputs, choose System > Baseband I/O > SD #1.
For SDI #2 outputs, choose System > Baseband I/O > SD #2.
For AES3 outputs, choose System > Baseband I/O > AES3 Outputs.
See Figure 4. Core Outputs, below.
Figure 4. Core Outputs
I/O Capabilities of Different AERO Processors
AERO.10 I/O
1 x 1.5G SDI I/O with 8 audio pair
4 x AES-3 unbalanced I/O on BNCs
1 x analog stereo, input only, DB9 F
AERO.100 I/O
1 x 1.5G SDI I/O with 8 audio pair
4 x AES-3 unblanced I/O on BNCs
1 x analog stereo, input only, DB9 F
AERO.2000 I/O
1 x 1.5G SDI I/O with 8 audio pair
4 x AES-3 unbalanced I/O on BNCs
4 x unbalanced AES-3 I/O on DB25
AERO.20 I/O
2 x 1.5G/3G SDI I/O with 8 audio pair for each SDI I/O
4 x AES-3 unbalanced I/O on BNCs
up to 8 x AES67/SMPTE 2110-30/31 Profile A streams I/O
an AES67/SMPTE stream is also called a flow
AERO.20 receive and send streams may contain 2, 6 or 8 audio channels.
2 channel streams can be connected to any AMX instance 2 channel input
A 6 channel source stream may be connected to an AMX5.1 or AMX2.0, 5.1 channel input
An 8 channel source stream may be connected to an AMX5.1 or AMX2.0, 5.1 channel input and/or a 2.0 channel input.
5.1 channel sources must be received in a single stream of 6 or 8 audio channels.
5.1 channel sources must be connected to an AMX5.1 or AMX2.0 input in consecutive order.
pairs 1, 2, 3 for a 6 channel source
AERO.200 I/O
2 x 1.5G/3G SDI I/O with 8 audio pair for each I/O
4 x AES-3 unbalanced inputs on BNCs
up to 8 x AES67/SMPTE 2110-30/31 Profile A streams in and out
an AES67/SMPTE stream is also called a flow
AERO.200 may receive and send 2, 6 or 8 audio channels in a stream.
A 2 channel stream can be connected to any AMX 2 channel input
A 6 channel stream may be connected to an AMX5.1, 5.1 channel input
An 8 channel stream may be connected to an AMX5.1, 5.1 channel input and a 2.0 channel input.
5.1 channel sources must be received in a single stream
5.1 channel sources must be connected to an AMX5.1 input in consecutive order.
pairs 1, 2, 3 for a 6 channel source
pairs 1, 2, 3 or 2, 3, 4 for an 8 channel source
AERO.2400 I/O
2 x 1.5G/3G SDI with 8 audio pair I/O for each SDI I/O
4 x AES-3 unbalanced I/O on BNC
4 x AES-3 unbalanced I/O on a DB25
up to 8 x AES67/SMPTE 2110-30/31 Profile A streams
an AES67/SMPTE stream is also called a flow
AERO.2400 can receive and send 2, 6 or 8 audio channels.
A 2 channel stream can be connected to any AMX 2 channel input
A 6 channel stream may be connected to an AMX5.1 or AMX2.0 5.1 channel input
An 8 channel stream may be connected to an AMX5.1 or AMX2.0 5.1 channel input and a 2.0 channel input.
A 5.1 channel sources must be received in a single stream (6 or 8 channel stream)
5.1 channel sources must be connected to an AMX5.1 input in consecutive order.
pairs 1, 2, 3 for a 6 channel source
pairs 1, 2, 3 or 2, 3, 4 for an 8 channel source
Note: When using both SDI input connections, they must be synchronous with each other, meaning that they must use the ame video timing reference.
Loading and Saving I/O Presets
To make configuration and setup of your AERO easier, sample baseband I/O routing presets are included to use as a starting point. Alternatively, you can change I/O settings and then save them as a preset.
To load an I/O preset:
Choose System > Baseband I/O > Load Presets.
Navigate to the desired preset and select it. (See I/O Preset Considerations.)
To save an I/O preset:
After adjusting settings, choose System > Baseband I/O > Save Presets.
Use the Save Presets page controls to name and save the new preset.
I/O Preset Considerations
There may be presets that are not applicable to your use case (such as presets that support two AMX instances if you only have one enabled). Check out the default presets to find one that is close to what you need to start with.
The I/O presets are divided into single AMX instance presets and dual AMX instance presets. Each AMX instance is routed to its own SDI I/O path in these presets. While this may not fit the need for everyone’s workflows, it provides a good starting point for configuration.
AERO.10,, 100, 2000
Single SDI / Single AMX instance presets:
SDI with 1x stereo (AMX5.1)
SDI with 2x stereo (AMX5.1)
SDI with 3x stereo (AMX2.0)
SDI with 3x stereo + Dolby (AMX2.0)
SDI with 5.1+2 & AES3 Local 9-10 In (AMX5.1)
SDI with 5.1+2+2 (AMX5.1)
SDI with 5.1+2+2 + Dolby (AMX5.1)
SDI with 5.1+2+2 Input (AMX2.0)
SDI with 5x stereo (AMX5x2)
AERO.20, 200, 2400
Dual SDI / Dual AMX instance presets:
2x SDI with 2x 5.1+2+2 (2x AMX5.1)
2x SDI with 2x 5.1+2+2 w AES3 Local 9-10 In (2x AMX5.1)
2x SDI with 2x 5.1+2+2 w AES3 Local(9-10) In (2x AMX5.1)
2x SDI with 5.1+2+2 and 3x 2.0 (AMX5.1 + AMX2.0)
2x SDI with 5.1+2+2 and 3x 2.0 w AES3 Local 9-10 Inputs (AMX5.1 + AMX2.0)
2x SDI with 5.1+2+2 and 3x 2.0 w AES3 Local(9-10) Inputs (AMX5.1 + AMX2.0)
2x SDI with 5.1+2+2 and 5x Stereo (AMX5.1 + AMX5x2)
All adjustable parameters that fall under the Baseband I/O menu are stored in these presets (from the settings in the Main page through the settings in the AES3 page). This includes video delay settings for the SDI Outputs, which are used ensure that video and audio remain in sync through the unit. All compensating video and audio delays are set at zero (no delay) when units are shipped from the factory.
Input Status
The Input Status page (System > Baseband I/O > Input Status) provides the status for each physical baseband input, along with the status of both power supplies.
Instance Overview
AERO.20, 200, 2400 example
The Instance Overview page (System > Baseband I/O > Instance Overview) provides a status display of all the I/O routes, both input and output, made for each AEROMAX engine instance (such as Inst 1 and Inst 2 onscreen). This includes both baseband I/O and AoIP I/O. See figure 5, below.
Figure 5: Instance Overview page
SRC (Sample Rate Converters)
AERO.20, 200, 2400 example
There are 36 channels of hardware Sample Rate Conversion (SRC) built into the AERO.20, AERO.200, and AERO.2400 (System > Baseband I/O > SRC). Twenty channels of SRC are permanently fixed in the audio Core Input path. 16 channels are switchable to be either in the audio Core Input path or in the audio Core Out (output) path for SDI #1 (Out 1-16).
Figure 6: Sample Rate Conversion with 16 of 32 channels in the audio Core Input path
Figure 7: Sample Rate Conversion with 16 of 32 channels in the audio Core Out path for SDI #1
Important! While PCM audio passes through an SRC unharmed, encoded audio does not. Encoded audio, such as Dolby Digital, Dolby Digital Plus, MPEG-1 Layer II, AAC, and all other encoded audio formats, is destroyed when passing through an SRC. Properly managing clock synchronization is required when using coded audio.
Using coded audio with mixed reference clock domains makes managing clock domains more challenging.Instance Source
SDI #1 and #2 Status
AERO.20, 200, 2400 example
Each SDI output page (System > Baseband I/O > SDI #1 and SDI #2, respectively) provides tabs for revealing SDI output status information, configuring audio routing, and compensating for video delay to maintain audio/video sync.
Status
The SDI’s Status subpage reports the input video format, along with the status of each audio pair contained in the SDI output.
Figure 8: SDI output status information
Audio
The SDI’s Audio subpage is where the output audio is configured.
The Embed control enables or disables embedding audio from the AMX processing engine or Core Audio, along with pair shuffling.
When the Embed control is disabled, the audio from the SDI input passes through directly to the SDI output, which completely defeats the purpose of having an audio processor inline.
SDI #1 supports:
Embedding from audio Core Output 1-16
Embedding from SDI #1 In 1-16
Mute (no audio)
SDI #2 supports:
Embedding from audio Core Output 17-32
Embedding from SDI #2 In 1-16
Mute (no audio)
Figure 12: SDI Audio routing tab
Video
The SDI Video page is where the video compensating delays are configured. The video delays allow for audio/video sync to be maintained on the output of the unit.
Figure 13: SDI Video subtab and delay setting
Important! These are manual controls and must be adjusted during setup.
The AERO is shipped with no video delay added, so it must be set on each SDI output for audio and video to be synchronous.
If it is desired to buffer the AEROMAX processed outputs to an integer number of video frames or other value, use the audio delay controls for the AMX instance, located in the Output Delay page (Instance 1 or Instance 2 > Output > Output Delay)
Note: The factory default value of the video delays is 0 ms. The video delays must be adjusted for the desired amount of delay, whether to match the latency of the AEROMAX Engine, or set it to an integer number of video frames.
Video delay settings are part of the Baseband I/O presets. Baseband presets should be saved after all configuration parameters are set to their desired values.
AERO.20, 200, 2400 AES3 Outputs
This page (System > Baseband I/O > AES3 Outputs) provides status information and controls for routing AES3 outputs.
To see an overview of routing for the AES3 outputs:
Choose System > Baseband I/O > AES3 Outputs > Overview.
Figure 14: AES3 outputs and Overview subpage
To configure routing for AES3 outputs:
Choose System > Baseband > AES3 Outputs > Assign.
Use the AES3 drop-down menus to assign AES3 outputs. The available output source options for the AES3 outputs are audio output core 19-34.
Figure 15: Configuring AES3 output routing (AES3 Outputs, Assign subpage)
Note: AES3 outputs are always clocked based upon the current audio reference clock. Sample Rate Conversion is not available for the AES3 outputs.
Note: AES3 Aux Outputs (pairs 5, 6, 7 and 8) are only available on the AERO.2000 and AERO.2400.
TCP Link Status
This page (System > Baseband I/O > TCP Link Status) displays the status of the link between the AERO unit and the host computer running NfRemote. It is found in all AERO processors.
Display Settings
Display Settings allows configuration of metering and information displays. These are always seen at the top of the NfRemote window. The Display Settings selection appears in several menus for easy access wherever these settings are needed. It is found in all AERO processors.
Clock Status Indicator
The NfRemote main window includes a built-in reference clock indicator. This indicator is the double-L Linear Acoustic logo, located in the top left corner of the window. The indicator uses color to denote the status of the reference clock, and communication status of communication between the baseband I/O card and the main system processor.
Solid gray: The unit is operating normally and is using the primary reference clock.
Figure 16: Primary baseband reference clock is in use
Blinking yellow: The unit is operating normally, but the primary reference clock source has been lost, and the unit is using the secondary reference clock.
Figure 17: Secondary baseband audio reference clock is in use
Blinking red: One of three conditions has occurred: The unit has lost both the primary and secondary reference clock (and is now using the internal 48 kHz clock), or there is a failure communicating with the baseband I/O card, or there is a failure with the baseband I/O card itself.
Figure 18: Baseband audio reference clocks are missing, internal oscillator in use
Clock Status Indicator is found in all AERO processors.
AoIP I/O Routing Overview
AERO.20, 200, 2400
AoIP (Audio over IP) routing and clocking are handled differently than baseband I/O. For more information, see Configuring Audio Over IP.
AoIP routing is handled in the AMX instance itself.
For clocking, the AoIP section operates on a separate reference clock; either a PTP clock (IEEE-1588) or a Livewire clock. PTP is the industry standard clock when using AES67 or SMPTE ST 2110 workflows. Livewire clock is a clock option when using workflows based on Telos Alliance Livewire. A Livewire system can also use a PTP clock, instead of a Livewire clock.
AoIP reference clock status is not reflected in the double-L clock status indicator located in the top left corner of the NfRemote window. Instead, it is found on one of the AoIP status pages (such as System > System > AoIP > AoIP 1), or in the AoIP reference clock section (System > System > AoIP > Clock).
Figure 19: PTP / Livewire clock page
Sample Rate Conversion
Since the AoIP section uses a separate, and different, reference clock than the audio processing engine and baseband I/O, clock management is essential. To aid in this, sample rate converters (SRCs) are included in between the AoIP section and the audio processing engine.
One general rule with SRCs is that PCM audio passes through them unharmed. However, encoded audio, such as Dolby Digital, Dolby Digital Plus, MPEG-1 Layer II, AAC, and all the other coded audio formats do not pass through SRCs without being destroyed.
Using coded audio with mixed reference clock domains makes managing clock domains more challenging.
Important! Coded audio, such as Dolby Digital (AC-3) and other formats can never be passed through Sample Rate Converters without being destroyed. Properly managing clock domains is required when using coded audio.
SRC would be used when, for instance, an AES67 or AES-3 source is routed to an SDI output to match the source audio rate to the SDI audio rate.