Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The three icons in the bottom (I) (see screenshot at Routing) manage the routing presets. There are three options:
The presets are related to their respective collection as explained in the next section on Routing Collections.
Note - As mentioned earlier in the introduction, both AIXpressor and flexAIserver employ flexAI as their underlying software platform.
Certain menus, most notably (but not exclusively) in the Interfaces section, are unique to one product or another, while many others will be similar if not identical regardless of the hardware.
Wherever possible, we have made an effort to point out which information applies to which products, but bear in mind there may be differences between the figures and illustrations in this documentation and your particular product.
The type of audio processing and the number of processors available is determined in part by which features have been licensed at the time of purchase. Additional processing solutions and features can always be activated by purchasing the respective license.
The available capacity of the SoM (System on Module) x86 processor installed in an AIXpressor is another determining factor. This limitation can be overcome by daisy-chaining an AIXpressor with a COTS (Commercial Off the Shelf) server equipped with a Jünger PCIe card that runs flexAI and connecting it with the proprietary Jünger tieLight low-latency fiber interface.
Audio processing is based on the Jünger flexAI engine (flexible audio infrastructure) which renders the audio processors and conects to the various audio I/Os and the system OS settings.
The processing itself is "program-oriented" in that the number of audio channels determines what types of processing blocks are involved (Mono, Stereo, 5.1 etc.). Each block appears in the Routing matix by its name where "x" represents the progarm number. For example, a stereo processor will appear as Program x: L and Program x: R while a multi-channel surround processor will appear as Program x: L ... Program x: Rs. A surround processor with voice-over channels would add two more inputs labeled Voice A and Voice B.
Select Audio Processing in the Main menu (A), then click the +ADD button (B) to open the "Add new Program" window. Use the Program Type dropdown menu (C) to open the list of available processing options, enter a "friendly" name into the Program name field (D) if desired, then click the OK button (E) to save.
Note - If you choose not to enter a custom name in the Program name field, the program type will be used as the name.
The GUI for the selected processor will be displayed:
To change the name of a processor once it has been added, click the EDIT NAME button (B), type the new name in the Name field (C), tick the check box, then click the Close button (A) to save and exit.
Important! As noted in red on the GUI, remember that changing the processor name here also affects the Ember+ processing name and any remote control connections. As well as the appearience in the Routing matrix.
To delete a processor, click the DELETE button (B), click the checkbox of the processor(s) you wish to delete (E), then click the Delete Selected button (D). Clicking the checkbox a second time de-selects the processor. Clicking the Clear Selection button (C) de-selects all processors. Click the Close button (A) to save and exit.
Clicking on the name of an audio processor from the Main menu will open a window to reveal its individual processing stages and parameters.
Clicking on any of the processing stage buttons (A) will cause the window to scroll to the relevant displays and controls section (C) which, like the selected button, will be highlighted in blue. By default, all of the sections are visible but can be individually collapsed by clicking the collapse/expand arrow (B). Depending upon the size of your browser window, it may be necessary to use the scroll bar (E) to view the entire section. Clicking on the Collapse button (D) collapses all sections and changes the button name to Expand.
For detailed descriptions of Jünger audio processing parameters, please visit https://www.jungeraudio.com/uploads/preset/57f636396a612d241b030000/Junger_LevelMagic-Leveler-Dynamics_Parameters_210310.pdf.
For a list of recommended settings forthe Level Magic processor, please visit https://www.jungeraudio.com/uploads/preset/57f634ec6a612d241b010000/201512_EngineeringBulletin_LevelMagic_RecommendedSettings.pdf.
Changes made to each processing section can be saved as user presets.
Click on the Save Preset icon (F) to open the Save Preset window. Use the Save Preset As dropdown (A) to choose whether the changes will be saved as a new preset or will overwrite an existing preset. Type a name into the Preset Name field (B) and a description, if desired, in the Preset Description field (C). Click the OK button (D) to save your changes and exit, or the Cancel button (E) to exit without saving.
Once presets have been saved, they can be recalled by clicking on the Open button (A). Clicking on the Preset Operation button (B) provides a convenient means to open, save, and delete presets.
Presets can also be used for entire processing strips. The Open (A), Save (B), and Preset Operation (C) buttons work here exactly as they do for individual processing sections.
The routing matrix consists of three primary sections: A list of sources (A) in the left column, a list of destinations (C) in the right column, and a cross-point matrix (B) used for connecting sources to destinations in the middle column.
A Source can be any of the following:
A physical input from the main PCB, such as AES3, analog, MADI, tieLight, and AoIP
A physical input from interface slots 1-4, such as SDI, AES-3, analog, MADI, and Dante/AES67
The output of one of the DSP processing blocks, such as Level Magic Channel Strip - Stereo or Program + Spectral Processing Strip - 5.1
A Destination can be any of the following:
A physical output from the main PCB, such as AES3, analog, MADI, tieLight, and AoIP
A physical output from interface slots 1-4, such as SDI, AES-3, analog, MADI, and Dante/AES67
The input to one of the DSP processing blocks, such as Level Magic Stereo or SpectralSignature Level Magic 5.1
Getting a signal from one of the physical inputs to a DSP processing block and then ultimately to a physical output is a two-step process.
First, one of the physical inputs must be connected to the input of a DSP processing block.
This is accomplished by selecting audio channels of a physical input from the source side of the matrix (A) and then selecting audio channles of DSP processing blocks from the destination side of the matrix (B). Pressing the Link (New) button (C) will create the connection.
In Figure 2 below, channels AES 1 and AES 2 of the AES3 input are being routed to the Level Magic Channel Strip - Stereo processing block L and R for loudness control:
Second, the output of a DSP processing block must be connected to one of the physical outputs.
This is done by selecting the DSP processing block from the source side of the matrix and selecting the physical output from the destination side of the matrix.
In Figure 3 below, the processed output of the Level Magic Channel Strip - Stereo L and R is being routed to EMB1 and EMB 2 of the Slot 2: SDI embedded SDI output. Pressing the Link (New) button (C) will create the connection.
Note - You may select multiple sequential sources by holding down the "Shift" key and then selecting the first and last sources. To select multiple non-sequential sources, hold down the "Control" key (Windows) or "Command" key (Mac), then select the desired sources. Note that each source can be simultaneously routed to multiple destinations, but not vice versa.
The Routing pane provides tools needed to make connections. They span from organizing the source and destination columns to several methods of creating connections (crosspoints).
If you have marked audio channels of a specific source (C), you can move them to the matrix by pressing the bluish arrow (D). This will prepare them to be assigned to their destinations.
FM radio broadcast is not only about audio. Instead the signal consists of different services that share the ‘space’ available on the FM carrier. A typical stereo radio signal spectrum may look like this
Mono audio signal (M=L+R) - 30 Hz to 15 kHz base band
Stereo pilot tone at 19 kHz - approximately 9 % of 75 kHz deviation
Stereo audio signal (S=L-R) - 30 Hz to 15 kHz base band
DSB-SC carrier - Double-sideband suppressed carrier
RDS signal - Radio Data Signal at 1 187,5 Bit/s
DARC signal - Data Radio Channel at about 16 000 Bit/s
SCA signal - 14 kHz (narrow) or 26 kHz (wide) bandwidth for auxiliary audio services
To calculate the overall MPX Power the power spectrum of all consisting signals needs to be considered.
Please note that within the FM Conditioner Web UI, only RDS and SCA Deviation can be set as additional services. As SCA and DARC normally cannot be used simultaneously due to their overlapping frequency bands, the SCA Deviation parameter can also be used for DARC. To calculate the overall deviation, all of the services in use must be taken into account to ensure that they do not exceed the modulation limits defined by the ITU (as shown below). After setup, this process happens internally and is not a concern for the FM Conditioner user.
When dealing with processing for FM broadcast, four main parameters come into focus:
Deviation Δf of the transmission frequency (carrier) fc
MPX Power of the modulating signal (modulator)
Pre-Emphasis to enhance the signal-to-noise ratio of FM transmission
Baseband bandwidth of all involved services (audio signals and auxiliary data)
ITU-R BS.412 has standardized the maximum values for these parameters. Broadcasters must comply with these limits to not exceed the planned coverage or interfere with adjacent programs. They are:
Maximum peak deviation of +75 kHz
Maximum MPX Power of 0 dBr
A typical audio baseband cutoff at 15 kHz to ensure undisturbed transmission of the 19 kHz stereo pilot tone
For mono operation a typical audio baseband bandwidth of 17.5 kHz is utilized (no pilot tone is necessary)
MPX Power is measured at random intervals of 60 seconds. An MPX Power level of 0 dBr should be equivalent to the modulation power of a stationary sine signal that induces a deviation of +19 kHz. A stimulus frequency of 500 Hz is recommended.
The tasks required to comply with this rule may sound 'simple' on the surface: take your pocket power measurement instrument, connect it to your readily accessible reference antenna, tune it to your transmitter, and take measurements. Then, adjust the relevant audio parameters if necessary. However, as this approach is not applicable for studio equipment, we must calculate MPX Power before modulation and then translate it to the studio output. To ensure precise calculations, all technical equipment must be gain-matched and calibrated.
The crucial step in calibration is setting the Operating Level. A stationary sine signal at this level should induce a 40 kHz deviation in the FM carrier. If the input level (at the FM HPA or uplink line) for this reference modulation is known, simply configure the Operating Level in the FM Conditioner accordingly. This is applicable in most installations.
In many stations, the reference level for a 500 Hz tone is +6 dBu (analog) or -9 dBFS (digital). It may be designated as the operating level and defined at 0 dB relative (as displayed on a peak level meter). However, please exercise caution with this type of reference level scale, as this analog operating level of 0 dBr is not the same as 0 dBr MPX Power.
If the reference modulation is unknown, you need to apply a sine test tone and measure the frequency deviation of the FM carrier over the air. Start with a generator level of -9 dBFS and adjust this value until you achieve a 40 kHz deviation. It's important to note that any processing in the signal chain between the generator and FM HPA must be bypassed during calibration. The calibration process should be carried out without considering any processing, additional services, or pilot signals.
If the Reference Level of your setup differs from -9 dBFS, you can use the Setup Gain of the FM Conditioner for level matching.
The second step of calibration involves configuring the values for the Pilot Tone, RDS, and SCA (DARC) Deviation. The required values depend on the settings of the respective encoders. Please refer to their manuals.
After completing the calibration process, the FM Conditioner will display the available audio headroom.
Here is an example with an assumed deviation of ~ 12 % of 75 kHz for the extra services:
20*log (75 kHz – 8.8 kHz) / 40 kHz = 4,4 dB
Or -4.6 dBFS
All calculation is performed internally and updates automatically whenever any of the involved parameters change. The resulting value is referred to as the 'Ceiling.' It's essential to understand that the Ceiling is calculated with the Pre-Emphasis filtering of the FM transmitter included. Therefore, the wideband true peak level of the audio signal before Pre-Emphasis must be lower. To better grasp this concept, you can refer to the level relation diagram:
Pre-Emphasis is a filtering system in which higher frequencies are boosted by a shelving filter at the transmission stage and conversely reduced at the receiver end. The Pre-Emphasis filter employs a time constant of 50 µs (or 75 µs in the USA), resulting in a 10 dB gain at 10 kHz. This process significantly improves the signal-to-noise ratio. However, as the increased high-frequency energy contributes to the MPX Power, it must be taken into account within the FM Conditioner.
There are two mechanisms to manage Pre-Emphasis. First, a Pre-Emphasis Headroom parameter reduces the maximum wideband level by lowering the true peak limiter threshold. This results in lower overall audio levels but enhanced high-frequency transparency. Second, a process called Pre-Emphasis Limiter dynamically reduces the high-frequency component of the audio signal, creating 'space' for the additional Pre-Emphasis shelving. The Pre-Emphasis Limiter is always active and prevents high-frequency overmodulation. To lessen its impact, the Pre-Emphasis Headroom should be increased. The Pre-Emphasis Limiter is based on sophisticated dynamic filter algorithms, well-known from the state-of-the-art Jünger Audio De-Esser.
It's important to note that very short transients may not be fully mitigated by the Pre-Emphasis Limiter. Nevertheless, this is a fundamental aspect and has no practical significance for FM transmission.
The Maximum True Peak value cannot be manually set by the user since it is automatically calculated and set to the Ceiling Level minus the Pre-Emphasis Headroom. When there's no Pre-Emphasis Headroom, the Maximum True Peak equals the Ceiling.
The most crucial component of the FM Conditioner processor is undoubtedly the MPX Limiter. Since MPX Power is a value calculated over one minute of integration time, limiting can be a highly intricate task. In theory, a 60-second look-ahead time may seem appropriate, but it's not practically feasible for a real-time processor. Therefore, the Jünger Audio MPX Limiter employs a complex prediction algorithm that adapts to the incoming signal structure. Nevertheless, the limiter reference level remains an absolute brickwall threshold and is considered inviolable. In the event of an 'emergency,' the MPX Limiter will drastically reduce the signal level to prevent any threshold violation. The MPX Limiter in the FM Conditioner can be considered the most effective MPX brickwall limiter available today.
Please be aware that the MPX Limiter Reference can, of course, be exceeded when incoming levels are high and the MPX Limiter has just been activated. According to the measurement principle, it may take up to one minute for the MPX Limiter to stabilize
The MPX Limiter Profile impacts the speed and extent of the process and, consequently, its neutrality toward incoming sound quality. When using softer settings, the system requires a buffer zone between the MPX Limiter reference and the measured MPX of the audio signal. Although this buffer zone is always very small, with harder settings, it becomes even smaller, allowing for higher MPX Power transmission. The optimal setting depends on the type and style of the program being broadcast.
MPX Power 60 s (dBr) - Currently measured MPX Power
Duration - Past time since reset
MPX 60 s Max (dBr) - Maximum MPX value since last reset
MPX True Peak Max - Maximum True Peak value since last reset
Gain Reduction Max - Maximum MPX Limiter Gain Reduction since last reset
Reset Max - Resets Current Measurements and stores last values in Recent Measurement
Duration - Past time for last measurement period
MPX 60 s Max (dBr) - Maximum MPX value for last measurement period
MPX True Peak Max - Maximum True Peak value for last measurement period
Gain Reduction Max - Maximum MPX Limiter Gain Reduction for last measurement period
FM Conditioner Enable - [ON / OFF]
Setup Gain - [-4.0 … 10.0] dB
Can be used to adapt loudness processed signals to MPX criteria or level matching
Pre-Emphasis Headroom - [0.0 … 15.0] dB
True Peak Limiter Profile - [0 ... 9]
True Peak Limiter Threshold - No user parameter
Pre-Emphasis - [OFF / 50 µs / 75 µs]
Operating Level - [-16 ... -6] dBFS
Peak Deviation Target - [35 ... 80] kHz
Pilot Deviation - [0 ... 15] kHz
RDS Deviation - [0 ... 4] kHz
SCA Deviation - [0 ... 15] kHz
Resulting Ceiling - No user parameter
MPX Power Limiter Enable - [ON / OFF]
Reference - [-4 ... 4] dBr
MPX Limiter Profile - [Soft / Mid / Hard]
Low-Pass Filter 15 kHz - [ON / OFF]
AIXpressor can optionally be equipped with a Dolby® E decoder and encoder. Please see for instructions on installing a new processor.
Dolby E was introduced in 1999 as a professional audio coding system that allows the distribution of multichannel digital audio within two-channel infrastructures. Up to eight channels of broadcast-quality audio, plus metadata, can be distributed via a single AES3 pair.
The decoder will decode all standard Dolby E programs.
Important - Unlike legacy Dolby E implementations in which the second program of a 4x2 configuration appeared on outputs 7/8, AIXpressor always shows the audio outputs in ascending order regardless of which program configuration is being decoded.
Click on the Dolby E Decoder button (A), then on the In button (B) to display a running total of the number of frames received (C).
Click on the Dec button (A) to display a list of all parameters (B), including (but not limited to) the following:
Library Version - The version of the installed Dolby library.
Input Signal - Green indicates a Dolby E signal; yellow indicates PCM audio; red indicates mute.
CRC Errors - Displays the number of CRC errors in the incoming Dolby E stream. The counter can be reset with the Execute button at the bottom of the metadata display.
Frame Rate - Indicates the frame rate of the incoming Dolby E signal.
Frame Offset - Shows the offset between the incoming Dolby E signal and the system frame reference.
Bit Depth - Indicates the bit depth of the incoming Dolby E signal.
Program Configuration - Displays the Program Configuration metadata parameter, which determines how the audio channels are grouped within the Dolby E bitstream.
Program Description - Shows the Program Description metadata, typically the name of the program or a description of the program source.
Channel Mode - The Channel Mode (also known as the Audio coding mode) indicates the active channels within the encoded bitstream. In the decoder, this ensures the proper routing of the audio channels to downstream devices.
LFE Channel - Indicates whether or not there is an LFE Channel present in the incoming bitstream.
Bitstream Mode - Displays the audio service contained within the incoming Dolby E bitstream.
Dialog Normalization - Also referred to as Dialog Level or dialnorm, this indicates the average level of dialog in the presentation and determines the proper level shift in the decoder to ensure proper normalization within and between program sources.
Click on the Mtr button (A) to view the decoder meter page. The Peak Level meters (D) show sample-accurate peaks for all eight incoming audio channels with a hold function. Peak Accuracy (B) is currently fixed at sample-accurate resolution. The Peak Hold control (C) allows for Automatic or Manual control of the hold feature. Clicking the Reset Measurement Execute button (E) resets the peak hold indicators.
Click on the Out button (A) to show the number of clients (B) currently connected to the unit and a running total of the number of frames emitted (C) from the decoder.
Important - Any preset saved and stored in the Dolby E decoder will also be available in the Dolby E encoder, providing an easy way to use the same settings and metadata values. Note that you may receive an error message if the metadata in one of the received programs does not match the program type - for instance, if LFE is activated for a 2/0 Channel Mode of a 5.1+2 Program Configuration. The encoder will automatically correct this, and you may dismiss the message.
Click on the Dolby E Encoder button (A), then on the In button (B) to display a running total of the number of frames received (C).
Click on the Mtr button (A) to view the encoder meter page. The Peak Level meters (D) show sample-accurate peaks for all eight encoded audio channels with a hold function. Peak Accuracy (B) is currently fixed at sample-accurate resolution. The Peak Hold control (C) allows for Automatic or Manual control of the hold feature. Clicking the Reset Measurement Execute button (E) resets the peak hold indicators.
Click on the Enc button (A) to display a list of all parameters (B), including (but not limited to) the following:
Library Version - The version of the installed Dolby library.
Encoder Status - Green indicates the encoder is active; red indicates it has stopped.
Video Sync Frame Rate Status - Green indicates proper sync; red indicates a mismatch.
Video Sync Frame Rate - The actual measured reference frame rate extracted from the sync signal.
DSP 1/2 - DSP 7/8 - A label of the encoder inputs based on the signal type to ensure proper encoding for the chosen Program Configuration.
Frame Rate - The Frame Rate of the Dolby E-encoded bitstream.
Video Sync Shift Offset - Sets the guard band relative to the video switching point (see SMPTE RP 168) to ensure proper Dolby E alignment. Shift steps are measured in audio samples using a 48kHz sample rate.
Program Configuration - Sets the Program Configuration metadata parameter, which determines how the audio channels are grouped within the Dolby E bitstream.
Program Description - Sets the Program Description metadata, typically the name of the program or a description of the program source.
Channel Mode - The Channel Mode (also known as the Audio coding mode) sets the active channels within the encoded bitstream.
LFE Channel - Informs the downstream decoder as to whether or not an LFE channel is present.
Bitstream Mode - Sets the audio service contained within the incoming Dolby E bitstream.
Dialog Normalization - Also referred to as Dialog Level or dialnorm, this sets the average level of dialog in the presentation and determines the proper level shift in the downstream decoder to ensure proper normalization within and between program sources.
Line Mode Profile - Sets the dynamic range metadata profile for line outputs of the downstream decoder.
RF Mode Profile - Sets the dynamic range metadata profile for the RF outputs of the downstream decoder.
DC Filter - Determines whether or not a DC-blocking 3Hz highpass filter is applied prior to encoding to remove DC offsets in the program audio.
Lowpass Filter - Determines whether or not a lowpass filter is applied to the main input prior to encoding to remove high frequencies that would not be encoded, thereby preventing aliasing upon decoding.
LFE Filter - Determines whether or not a 120Hz eighth-order lowpass filter is applied to the LFE channel prior to encoding, thereby removing frequencies that would cause aliasing when decoded.
Click on the Out button (A) to show the number of clients (B) currently connected to the unit and a running total of the number of frames emitted (C) from the encoder.
Note - Dolby, Dolby Audio, and the double-D symbol are trademarks of Dolby Laboratories Licensing Corporation. The Dolby E encoder and decoder in AIXpressor are manufactured under license from Dolby Laboratories.
On top of the Source column (A) you will find the symbols to expand and collapse the view of the audio channels that belong to sources. The symbol toggles the view of enabled sources (sources that have connected audio channels). The symbol toggles the view of the sources column. A Search field (B) will show only sources that include only the specified search criteria. The Destination column operates in the same manner.
The greenish center bar (F) indicates successful connections. Unrouted entries have no marks, while unsuccessful routes will be marked red. The icon (G) is a powerful tool used when highlighting one or multiple entries of the matrix and offers several options to manage the connections. You may Delete connection(s), Clear the source(s) and/or the destination(s) of existing connections, and Move sources or destinations up and down to other connections. The icon above the Destination column (K) toggles the view between unused and all destinations.
Grabbling the icon (H) on the left side of a highlighted connection allows you to move such connection up or down to organize the list to your taste.
Note - The Decode page displays considerable additional information A detailed explanation of all metadata parameters is available in the
Note - A detailed explanation of all metadata parameters is available in the
Selecting Interfaces from the Main Menu adds a column next to the Main Navigation menu which shows all available I/O interfaces and, depending on the particular interface, sub-menus for settings and status.
Each interface is explained in detail in the dedicated sub-sections below.
Note - Not all interfaces are available on all products. For example, flexAIserver has no hardware I/O except for the optional PCIe card for MADI and tieLight connections. Accordingly, there may be differences between your system and the sample images shown in this document since most screen shots are bound to the AIXpressor.
Applicable to AIXpressor and flexAIserver
The AoIP implementation supports Livewire (including Livewire Clock and Livewire Routing Protocol), SMPTE ST 2110-30 / -31 Level A, and AES67. It is capable of generating multicast streams with between 1 - 8 audio channels per stream. Support for up to 64 audio channels per stream is planned for a future release.
Note - This chapter assumes familiarity with AoIP technology, including RTP transport, PTP synchronization, QoS (DSCP settings), applicable standards (including SMPTE ST 2110, SMPTE 2022-7, N-MOS, IEEE1588), and general terminology (such as multicast, unicast, VLAN, IMGP, etc.).
Important - The current UI shows some parameters that are not currently supported by the hardware, and are noted accordingly in the documentation below. They are greyed out and can't be set (at least for now).
When setting up a large number of receivers and senders, entering the information once in the New Stream Defaults section pre-populates the most common fields and eliminates the need to repeatedly enter the information with each new addition.
Selects the type of AoIP stream. Choices include Livewire, AES67, and ST2110.
Some values may ybe pre-selected based on the protocol, while others are initially blank to allow for a customized value. When you anble the settings they will appear in the Receivers and Senders stream setups in the following chapters. To ease the assignmment of multicast addresses for receiving streams you can set a Start Destination Address Prefix.
If Seamless Protection Switching is used you can set this address for streams for Media Interface 2 as well.
Seamless Protection Switching - ON/OFF
Codec - Select the type of codec for 2110 / AES67 streams
Auto RTP Payload Type - the paylaod type will b eautomatically set depending on the selected protocol
Start Destination Address Prefix
Note - The fields displayed in the Receiver and Sender sections will vary depending upon which protocol is selected; SMPTE 2110 is shown in Figure 1. It is important to mention again that setting these paramters requires a deep knowlege about AoIP, so pls. consult therespective IETF, AES, SMPTE, AMWA knowlege base if you have questions. At Telos we have the AoIP "Bible" that digs deeper into details:
<Link>
Expand the AoIP portion of the Interfaces menu, then select Setup.
Important: The screenshots here show the available controls with Show Expert Settings (H) enabled, and require a solid understanding of AoIP to avoid situations that may cause issues that are not immediately apparent.
Enable - Enables or disables the AoIP interface.
Sync Source (B) - Displays the sync source and indicates if the clock is locked (green dot) and shows the name of the interface where PTP is received.
Leader ID (C) - shows the MAC address of the current PTP leader
All three interfaces work identically.
Interface - Selects the respective LAN interface by its system name.
Link State - Indicates the status of the selected LAN interface (green = Up).
IP Address - Displays the IP4 address of the selected LAN interface.
LWRP (Livewire Routing Protocol) Password Status - Indicates whether or not a Livewire password has been set or not set.
LWRP Password - The field in which a password may be entered. Toggling the "eye" symbol to the right of the text field allows the password to be visible. Click <APPLY> to save the password. If done the Apply button changes to <CLEAR PASSWORD>.
256 Ch Extension License (I) The flexAI core license limits the number of audio channels to 256 for the receivers and the transmitters. If you must use more that this number you must acquire another such license. The field Claimed Extensions below shows the respective number.
Packet Processing With the introduction of the new High-Efficiency Audio-over-IP (XDP), the user can optimize the system's performance. In general, once the XDP mode is enabled (J), the system load reduces significantly, and packet sizes of 0,125 ms, 0,25 ms and 0,5 ms are unlocked on the transmitter end. However, as the load on an AIXpressor can still be high due to the high packet density, we have introduced a switch <Interval> that allows the user to balance the system between speed and CPU load. The decision is influenced by whether the short packet sizes are needed to optimize latency or if it's solely about transmitting a high number of channels per stream.
If the goal is a high number of channels, it may be sufficient to transmit packets every 1 ms (several packets in burst mode), significantly relieving the system. On the other hand, if low latency is crucial, the packets must be sent at the same interval as the set packet size, but this simultaneously increases the system load. Rule of thumb for Packet Sizes below 1 ms:
Small Packet Size + Small Packet Processing Interval = Low Latency + Higher System Load
Small Packet Size + Large Packet Processing Interval = Slightly Higher Latency (corresponding to interval setting) + Lower System Load. For Packet Sizes equal or above 1 ms the interval setting has no relevance.
This colume is meant to set the NMOS IS-04 Discovery Mode. I.e. how the device finds a NMOS registry in the network.
Connection - Connected (green dot) / Unconnected (red dot)
Host - IP address of the NMOS registry host
Port - of the IP connection to the host
Version - of the registry implementation
Discovery Mode - - Multicast DNS-SD (mDNS) flexAI is looking for a NMOS Registry Server by using mDNS. - Unicast DNS-SD flexAI is looking for a NMOS Registry Server by using Unicast DNS within the selected Domain - Manual You may set the host IP4 address and the port number of the Registry Server to query
Domain Domain name of the network for manually connecting to a NMOS regestry
Host IP address of the NMOS regestry for manually connecting
Port Port number of teh NMOS regetry for manually connecting
Query Registry ON / OFF
A NMOS Registry Server in turn will query the current flexAI device by using the IP4 address on port 3212 of the management interface
Remaining Licensed Channels
Remaining Licensed Streams
Will be used by the receiver when Auto Link Offset is turned on, to automaticaally deal with the network latency. Should be set in relation to the duration, in microseconds, of the latency present in the network. See AES67-2018 (page 20) that illustrates the link offset definition. Generally speaking, setting a value of three times the packet time selected in the Sender will provide more robust timing though with a small increase in overall latency. Separate fields are provided for each of the supported packet time options.
One may use the name from the sender stream or set an own stream name
Discovery Protocol Filter - The Discovery Protocol Filter can be set to either look for Livewire, SAP/AES67/ST2110, or NMOS/AES67/ST2110 when searching for streams in the network.
Default Name Filter field is provided to assign the filter a unique name to be used in the stream setup process.
Remaining Licensed Channels
Remaining Streams
Allows for selecting the appropriate QoS - Differentiated Services Code Point for each of the supported packet time options.
The Routing matrix can be subdivided into collections of cross points, each having its own preset. This allows you to create groups of connections.
The names of the Collections appear in the top of the cross-point matrix (A).
Connections are managed by the little icons in the upper right-hand corner (B). The Edit icon opens a menu where you can + ADD, Name / Rename, and Delete collections from a list. The eye symbol toggles between the view of one or all connections, selectable by highlighting and underlining their names when selected (A).
Expand the Receivers (RX) (A) portion of the AoIP menu, revealing the ADD/DEL buttons (B). Clicking ADD generates a new stream with the default settings and name. Clicking DEL deletes the selected individual stream. Each Receiver (C) has its own configuration and status page.
Selects the type of AoIP stream. Choices include Livewire, AES67, and ST2110.
Session Status - Displays the status of the current session.
RTP Status - Displays the status of the Real-time Transport Protocol.
Provisional Stream Status - Displays live status information for the stream.
Interface 1 and Interface 2 - Displays the RTP status of the individual interfaces.
Note - The fields displayed will vary depending upon which protocol is selected. For example, AES67 and ST2110 will show SDP information, which is not applicable to Livewire. AES67 is shown in Figure 1.
Enable - Enables or disables the stream.
Stream Name - Allows for a unique name for the stream.
Channel Count - Displays the number of enabled audio channels present in the stream.
Seamless Protection Switching - When enabled, specifies the reconstruction of the original stream in case packets are lost in any path per SMPTE 2022-7.
SDP - Allows the Session Description Protocol information to be entered (AES67 and ST2110 only). SDP information will be gathered and displayed in the Discovery section and may be copied and pasted here.
Note - For senders that do not support NMOS, you may use the Ravenna2SAP tool available at https://solutions.aimsalliance.org/product/rav2sap/.
The parameters below are available when Show Expert Settings is enabled:
Codec - Selects the desired codec (AES67 and ST2110 only).
Auto Link Offset - Enables or disables auto link offset.
Link Offset - When Auto Link Offset is disabled, allows a specific link offset value to be added to the minimum RTP offset to keep the RTP offset value positive.
Ignore RTP Payload Type - When enabled, the RTP payload type will be ignored.
RTP Port - Specifies the RTP port.
Interface 1 and Interface 2 - Enter the multicast destination address of the receiver in the Destination IP Address field. When the Livewire protocol has been selected, an additional field for the Livewire Channel number appears.
The Discovery section shows the senders available via Livewire, AES67, and ST2110. When highlighted, the details of each stream will be displayed. A Filter field provides a means of entering a stream name or keyword to minimize the amount of scrolling required on a large network. Clicking the Apply button will copy the announcement information to the current receiver.
Applicable to AIXpressor
AIXpressor has four AES3 interfaces proving a total of eight I/O audio channels. It may also be configured as four inputs and twelve outputs to support the monitoring of immersive audio formats.
Select AES3 (A) from the Interfaces menu.
Displayed information includes:
Relay Bypass (B) - Enables or disables the hard relay bypass for the AES3 input. When enabled, AES3 I/O routing will default to the configuration set by the jumpers near the I/O connector. See the AES3 I/O Relay Bypass portion of the Technical Data section for details.
AES Status Pair (C) - Indicates the status of the AES3 receiver (OK or Fail).
Signal Status Pair (D) - Shows the signal status for each stereo pair.
SRC Stereo Pair (E) - Enables or disables the sample rate converters for each of the four stereo pairs.
I/O Mode (F) - Selects either the eight input/eight output mode or the four input/twelve output mode.
Output Force Channel Status (G) - Options include Transparent, Auto, Prof PCM, Prof Non-PCM, Cons PCM, and Cons Non-PCM.
Applicable to AIXpressor
AIXpressor has a 6.3mm (1/4") front-panel analog headphone jack.
Select Headphones (A) from the Interfaces menu to adjust the output volume. Set the output volume by clicking and dragging the Headphone Gain slider (B). Enabling High Gain (C) boosts the headphone output to drive high impedance headphones.
Important - Enabling High Gain sets the headphone output to +20dB. Use this setting with caution to protect your ears and your headphones.
The source for the headphone output is selected in the Signal Routing menu.
Headphone volume can also be adjusted on the front panel by touching the Headphone symbol (A) from the home screen, then using the slider.
Expand the Senders (TX) (A) portion of the AoIP menu, revealing the ADD/DEL buttons (B). Clicking ADD generates a new stream with the default settings and name. Clicking DEL deletes the selected individual stream. Each Sender (C) has its own configuration and status page.
Selects the type of AoIP stream. Choices include Livewire, AES67, and ST2110.
Session Status - Displays the status of the current session.
RTP Status - Displays the status of the Real-time Transport Protocol.
SDP - Shows the Session Description Protocol (AES67 and ST2110 only).
Provisional Stream Status - Displays live status information for the stream.
Reset Sender Status - Resets the live status information shown in the Provisional Stream Status window.
Interface 1 and Interface 2 - Displays the RTP status of the individual interfaces.
Note - The fields displayed will vary depending upon which protocol is selected. For example, AES67 and ST2110 will show SDP information, which is not applicable to Livewire. AES67 is shown in Figure 1.
Enable - Enables or disables the stream.
Stream Name - Allows for a unique name for the stream.
Channel Count - Displays the number of enabled audio channels present in the stream.
Packet Time - Selects the packet time; options vary depending upon the selected protocol.
Seamless Protection Switching - When enabled, specifies the reconstruction of the original stream in case packets are lost in any path per SMPTE 2022-7.
Note - If Seamless Protection Switching is enabled, the Destination IP Address field of Interface 2 cannot be left empty.
Codec - Selects the desired codec (AES67 and ST2110 only).
DSCP - Selects the Differential Code Service Point.
Auto RTP Payload Type - When enabled, automatically selects the RTP payload type regardless of what is specified in the RTP Payload Type field.
RTP Payload Type - Allows the RTP payload type to be specified (AES67 and ST2100 only)
RTP Port - Specifies the port used for RTP.
TTL - Sets the Time to Live (packet lifetime) value.
Media Interface 1 / Media Interface 2 - Enter the multicast destination address of the sender in the Destination IP Address field. When the Livewire protocol has been selected, an additional field for the Livewire Channel number appears.
Note - When connected to Dante-enabled devices operating in AES67 mode, be sure to use the default Audinate prefix of 239.69.*.*
Applicable to AIXpressor
The SDI Interface menu contains sub-pages for Status, Setup, the De-Embedder, and the Embedder.
Select Status (A) from the Interfaces > SDI menu.
Displayed information includes:
SDI Status (B) - Shows the status of the internal clock as Locked or Unlocked.
Video Format (C) - Indicates the video format as SD, HD, 3G, or N/A.
Video Standard (D) - Displays the actual decoded standard (e.g., 1080i50), no SDI lock, or TAG last valid.
Overview (E) - Graphically shows the status and potential issues within the SDI signal path. For example, If there is no SDI reference present, the input portion of the graphic will turn red.
Audio De-Embedder Status (F) - Indicates the format of the de-embedded signal as PCM, Dolby E, Dolby Digital, Dolby Digital Plus, MPEG-4 HE AAC, MPEG-4 AAC, or N/A.
VANC Metadata De-Embedder Status (G) - The indicator turns green when the SDID is detected in the stream; the pre-selected stream as established in the de-embedder setup stream is also identified.
Audio Embedder Status (H) - Indicates the status of the embedder as follows:
AUTO Embedding - A new group will be built.
AUTO Replace - The structure of the group from the input is retained and the audio content is simply replaced.
Delete - The group from the input is deleted.
OFF - The embedder for the group is disabled.
VANC Metadata Embedder Status (I) - Shows the status of the embedder as Enabled or Disabled (for details, see the SMPTE ST 2020-2 standard).
ARIB STD-B39 Control Data Status (J) - Indicates the status as Available or Not Available along with the Audio Mode; for more information on the ARIB Japanese standard, see "Structure of Inter-Stationary Control Data Conveyed by Ancilliary Data Packets" at https://www.arib.or.jp/english/std_tr/broadcasting/desc/std-b39
Embedder Metadata Errors (K) - Indicates metadata errors including No Show, Overwrite, Overwrite Block, Overflow, and Audio Sync errors plus the status of the test pattern generator.
Select Setup (A) from the Interfaces > SDI menu.
The SDI Bypass section (B) contains two controls:
The SDI Relay Bypass, when enabled, de-activates the bypass relay which serves to connect SDI-IN directly to SDI-OUT1 in the event of a power failure. It also disconnects the de-embedder from the SDI input.
The SDI Embedder Bypass, when enabled, will pass embedded audio data from the de-embedder directly through to the embedder 1:1, preserving the original Ancillary Data structure.
The Video Delay section (D) sets the video delay in whole frames to compensate for any latency incurred in the audio chain. "0" turns off the delay function.
The Level B Stream Select dropdown in the 3G SDI Mode section (E) allows Stream 1 or Stream 2 to be used for the embedded audio per SMPTE 425M for details should the 3G-SDI signal contain two HD sub-streams.
The Test Pattern Generator section (C) offers a test generator to either check downstream connections during installation or for use when there is an input source failure. It can also be used to move 16 independent audio channels over a single coax cable from point to point.
The Mode menu includes OFF, AUTO (Input Loss), and Always ON.
The Video Format menu sets the generator's desired output format (resolution and frame rate) and whether it displays color bars or a black frame.
Select De-Embedder (A) from the Interfaces > SDI menu.
The HD SDI standard allows for asynchronous audio, which may require the use of an embedded Wordclock, and is critical in applications that synchronize the audio transport from the SDI de-embedder.
The Audio Sync Source section (B) sets the Embedded Wordclock source.
Auto - Asychornous audio is automatically sync'd to the Wordclock of De-Embedded Channel 1.
DEM1 - Asynchronous audio is manually sync'd to the incoming SDI signal.
The VANC Metadata De-Embedder section (C) enables or disables the metadata de-embedder; when enabled, the Stream Select menu chooses the individual stream source for the metadata (SSID 1 - SSID 9).
Select Embedder (A) from the Interfaces > SDI menu.
The Audio Embedder Section (B) contains the following controls:
Delete Existing Data - Choices include ALL, New HANC Structure, and OFF.
Each Group, 1 - 4, has its own Embedding Mode menu. Choices include:
OFF - Disables embedding altogether.
AUTO - Embedding
AUTO - Replace Audio
Delete
The AES Channel Status menu offers a choice of Transparent or Professional.
Important - If you generate a new AES channel status, the Audio Mode will automatically be set to Non-Audio ("Other") for both channels if an adjacent pair (1/2, 3/4, etc.) carries compressed audio (such as a Dolby-encoded stream).
VANC Metadata can be embedded using the following controls in the VANC Metadata Embedder Section (C).
Enable - Enables and disables the metadata embedder.
Delete Existing Metadata - All / OFF.
Stream Select - Determines into which stream the metadata is inserted (SSID 1 - SSID 9).
Vidoe Line - Selects which line number receives the metadata, which varies depending upon the video standard employed and how many lines are available for data insertion.
Each embedded audio signal can be delayed independently in the Embedder Audio Delay section (D). This feature is useful for maintaining lip sync when if a video delay is used. Values are in milliseconds (ms) with a range of 0 - 340.
Important - When using a Dolby-encoded signal, adjacent pairs must be set to the same delay values to maintain proper data structure.
Select Device (A) from the Interfaces > SDI menu.
The Parameter Version (B) and Firmware Version (C) of the SDI interface are displayed.
Applicable to AIXpressor and flexAIserver
AIXpressor has two independent optical interfaces which can be configured for tieLight and/or MADI.
tieLight is a proprietary Jünger interface providing high channel count and low latency - up to 1,024 bi-directional audio channels with a total latency equalling four samples. It is designed to daisy-chain multiple AIXpressor units and/or flexAI servers.
AIXpressor has a built-in tieLight interface, while flexAI servers use an optional PCIe card available from Jünger.
Select Setup (A) under tieLight / MADI from the Interfaces menu. Use the Interface Transmission Mode dropdown (B) to set the mode for both interfaces. Choices include:
MADI independent - Both interfaces use MADI but operate independently from one another.
MADI redundant - Both interfaces use MADI but are configured identically to provide redundancy.
tieLight independent - Both interfaces use tieLight but operate independently from one another.
tieLight redundant - Both interfaces use tieLight but are configured identically to provide redundancy.
IF1 MADI, IF2 tieLight: Interface 1 uses MADI; Interface 2 uses tieLight.
IF1 tieLight, IF2 MADI: Interface 1 uses tieLight; Interface 2 uses MADI.
When using tieLight, PTP sync distribution across multiple devices can be set in the tieLight PTP Role dropdown (A). Choices include Master, Slave, and Passive.
Note - Some options may be grayed out and unavailable depending on how the interfaces are set up in the Interface Transmission Mode menu.
SFP 1 and SFP 2 each have independent but identical status pages (A).
Displayed information includes:
RX Status (B) - Shows the current status of the selected optical input as reported from the SFP module.
Signal Status Stereo Pair (C) - Indicates the presence of a signal for each pair as well as the type of signal (PCM, Dolby E, Dolby Digital, Dolby Digital Plus, MPEG-4 HE-AAC, MPEG-4 AAC, and N/A). This information is gathered and analyzed by the core FPGA router using the signal headers of adjacent odd and even signals (stereo pairs). In addition to simply showing status, the information can be used globally for other functions including event management or muting processor inputs.
Important - MADI connections require the use of SFP modules capable of 125Mbps. tieLight connections require the use of 2.5Gbps modules.
Applicable to AIXpressor
AIXpressor's built-in analog interface provides a total of eight inputs and eight outputs. It may also be configured as four inputs and twelve outputs to support the monitoring of immersive audio formats.
Select Analog (A) from the Interfaces menu.
Displayed information includes:
Headphone Status (B) - Indicates whether or not headphones are connected.
I/O Mode (C) - Selects either the eight input/eight output mode or the four input/twelve output mode.
VALUE | SETTING |
---|---|
Format
Professional
Audio Mode
Audio / Non-Audio
Emphasis
None
Frequency Mode
Locked
Sample Frequency
48kHz
Channel Mode
Not Indicated
User Bits
None
Auxillary Bits
24 Bit
Audio Word Length
Not Indicated
The Sync page
Selecting Sync (A) from the Main Menu allows the sync settings to be viewed and changed. AIXpressor provides three priority tiers: Choice 1, Choice 2, and Fall Back for automatic failover.
The Sync Source Priority section (B) is used to define the sync source for Choice 1, Choice 2, and AES3.
Choice 1 and Choice 2 - Options include Internal, tieLIGHT/MADI 1, tieLIGHT/MADI 2, Sync-In WCLK/BB/Tri-Level, Interface Slot 1, Interface Slot 2, Interface Slot 3, Interface Slot 4, AES Select, and PTP. If none of the pre-selected sources in Choice 1 or Choice 2 are present, sync will fall back to Internal in order to maintain audio transport, even if this causes audible clicks and pops due to asynchronous conditions.
AES3 Select - The drop-down menu is used to pre-select the sync source when Choice 1 or Choice 2 are set to use AES Select as their sync source. Options include Sync-In AES3 (Sync-In BNC) and Inputs AES3 1/2, 3/4, 5/6, 7/8.
The Current Sync Source Status section (C) provides information about the sync source currently in use.
Current Sync Source - Displays the current sync source.
Current Sample Rate - Indicates the current sample rate, which in this firmware version is fixed to 48kHz.
Current Video Rate (fps) - Shows the current video rate (23.98, 24, 25, 29.97, 30, 50, 50.94, and 60).
The System Clock section (D) sets the primary and fallback sample rates and video rates.
Sample Rate (kHz) - Sets the preferred sample rate (currently limited to 48kHz).
Internal / Fallback Sample Rate (kHz) - Sets the internal (fallback) sample rate (currently limited to 48kHz).
Video Rate (fps) - Sets the preferred video rate (Follow Input, 23.98, 24, 25, 29.97, 30, 59.74, 60).
Internal / Fallback Video Rate (fps) - Sets the internal (fallback) video rate (23.98, 24, 25, 29.97, 30, 59.74, 60).
The Sync Source Information table (E) provides an overview of the available sync sources and their values. Information includes Sample Rate and Video Rate (fps) for each source.
Applicable to AIXpressor
The Dante interface provides 32 AoIP streams with a total of 64 audio channels to and from the Brooklyn II module on the Jünger DT-100 board. All settings can be performed via the Dante Controller software available for download from the Audinate website: https://my.audinate.com/support/downloads/dante-controller
Figure 13 below shows an example of the routing matrix of the Dante Controller where transmit and receive channels from various Dante interfaces are connected. The interface is color-coded. Red indicates the module resides in a different subnet. Blue represents non-Dante interfaces discovered on the AoIP network that provide AES67 multicast streams (such as Ravenna). Black represents native Dante interfaces operating in either Dante or AES67 mode. Note that if two Dante modules operating in AES67 mode exchange audio signals, the streams will default to Dante Unicast mode.
We strongly recommend studying the numerous documents available from AIMS and the Internet Engineering Task Force to familiarize yourself with the terms used in AoIP networks from PTP over mDNS to Layer 3 routing. For Dante-specific documents are available on the Audinate website, and imparting such knowledge is beyond the scope of this manual.
Important - Layer 3 routing and SMPTE ST-2110 / 2022-7 require the use of the Dante Domain Manager. A license is available from Audinate.
Important - The Dante Controller plays a central role in a Dante network no matter if the interfaces operate in Dante or AES67 protocol mode, or both. Routing within such a network will be controlled by the Dante Controller only. AIXpressor does not provide any means to route audio channels within a Dante network.
When a Dante interface is installed, it will be automatically named by AIXpressor.
Select Status (A) from the Interfaces > Dante menu. The following information is displayed in the status screen (B):
Device Name - The name of the Dante interface used by the Dante controller software to locate it.
Sync Source - The AoIP network to which the Dante interface is connected.
Sync Status - Indicates whether the interface sync is locked or unlocked.
Preferred Master - Indicates whether this Dante interface is set to be a preferred master for other Dante devices.
Network Audio Sample Rate - Indicates the sample rate for AoIP audio.
Device Latency Setting - Defines the size of the buffer size in milliseconds (ms) required to handle network-related latencies.
AES67 Enabled - Indicates whether or not the interface can connect to both Dante and AES67 networks.
Device Access Lock - Shows whether the interface is unlocked or locked to prevent authorized access to the module.
Select Receiver (A) from the Interfaces > Dante menu. The following information is displayed:
Routing Label (B) - Labels are automatically assigned by AIXpressor in the Dante Routing menu.
Channel Label (C) - These are the labels for the 64 transmit channels; they display as numbers from 01 to 64 by default but can be customized using the Dante Controller.
Connection Status (D) - Shows the connection to each channel as OK, Fail, or N/A.
Signal Status Stereo Pair (E) - The routing FPGA analyses the signal headers of adjacent odd and even signals that may form a stereo pair. This status information can be used globally for event management or to mute processor inputs. The type of signal is also displayed (PCM, Dolby E, Dolby Digital, Dolby Digital Plus, MPEG-4 HE-AAC, MPEG-4 AAC, or N/A).
Connected to (F) - Receiver channels must be routed (connected) to transmit channels within the AoIP network. The Dante Controller must be used for signal routing. The receiver shows the transmission channel label and the device name separated by an "@".
Subscription Status (G) - This indicates whether the receiver is subscribed and if so, to which type of connection. Options include Connected (Unicast), Connected (Multicast), No Subscription, and Subscription Unresolved.
Select Transmitter (A) from the Interfaces > Dante menu. The following information is displayed:
Routing Label (B) - The routing label is automatically assigned by AIXpressor and serves as a reference in the Routing matrix of the Dante Controller.
Channel Label (C) - The channel label must be specified and assigned in the Dante Controller.
The Dante interface has two network connectors that may be configured as redundant or switched.
In redundant mode, the interface can be connected to two independent AoIP networks to provide "Seamless Protection Switching" as defined in SMPTE 2022-7.
In switched mode, both networks ports combine to build an Ethernet switch using the built-in Brooklyn II Ethernet interface.
Important - Do not connect both Ethernet connectors to the same network switch. Doing so will cause "race" conditions if the switch has not been configured to use the Spanning Tree Protocol, which is typical in many off-the-shelf "office" switches.
Select Primary Network (A) from the Interfaces > Dante menu.
The Connection Status (B) section shows the following information:
Network Status - Indicates if the interface is connected to an active network and at what speed (Connected 1G, Connected 100M, Offline, Pending, N/A).
PTPv1 and PTPv2 Status - Shows the status of the PTP clocks (Startup, Initializing, Faulty, Disabled, Listening, Pre Master, Master, Passive, Uncalibrated, Slave, NA).
The Current Network Status (C) contains the following information:
Current Mode - Redundant or Switched.
Current Enable DHCP - On or Off.
Current IP Information - Including IP address, Netmask, DNS Server, Gateway, and MAC Address.
The Change Network Settings(C) section allows the following information to be changed:
Request New Mode - Redundant (the default setting) or Switched.
Config IP Information - Allows changes to DHCP (enabled by default), IP Address, Netmask, DNS Server, and Gateway values.
Settings for the Secondary Network are identical to the Primary Network with one exception in the Request New Mode setup. If the Secondary network port is not connected or the Primary port is set to "Switched," the network status changes to "Offline" and no PTP status is available.
The System menu includes sub-menus for:
Setup - Includes "friendly" fields for the Hostname, system location, and system contact.
Network - Displays and configures settings for the various LAN interfaces.
Certificate - System cetificate for Transport Layer Security by using SSL based communication
Update - Facilitates system updates.
Logging - Displays a variety of system and event logs.
Licensing - Lists the currently installed licenses and facilitates downloading and uploading license files.
Info - Displays a variety of system statuses of hardware, software, system load and GNU licenses
Users - User management, password and SSH key settings
Storage - Display of the usage of the storage devices of the system
Terminal - Systm terminal via the UI
Backup / Restore - Used to create a backup file or restore a unit from an existing backup.
Power - Provides a means of shutting down or power cycling the unit from the remote interface.
If your flexAI system is connected to an open network, secure communication is a must.
In flexAI version 2023-12r1 secure client /server communication via HTTPS has been introduced. This requires a SSL/TLS protocol implementation. I.e. the server (flexAI) must provide a certificate that will be used by the client (web browser or other client software), to encrypt the communication. You may refere to the various sources in the internet if you need more detailed information about the matter.
Click on Certificates (A) to open the page
The certificate (B) you initially find on a flexAI system is a so called self signed certificate. If you have a CA (certificate authority) in our network you can register this certificate by generating a CRS (D) (Certificate Signing Request) file that is used for that process. But you can also import (C) a certificate that includes the IP address and/or the DNS name of the flexAI system. If it is registered with your browser as well, this will avoid error messages when you start a new HTTPS session (if your browser automatically deletes cookies and the history). You are able to dowload this certificate (E) or simply display it (F) FYI.
AIXpressor provides a comprehensive logging system based on information available in the Linux operating system. Logged information from the Kernel, running daemons, I/O operations, and user applications are stored in internal flash memory for future analysis.
Select Logging (A) from the System menu to view the log files.
Although the log files may be viewed by the end-user, the information is primarily meant for troubleshooting with customer support. Additional access to the log information may be included in future versions.
You can sort the logs by Severity and view All or just applications specific logs selected by the App: pull down (B).
The flexAI engine within AIXpressor and all audio processing blocks are license-bound. Stand-alone units will handle licensing through a USB dongle, while larger installations use a WiBU license server.
Select Licensing (A) from the System menu to view the license page.
The Product Name and Product Code are listed in the License section (B). Quantity indicates the number of installed licenses for a given product. Available indicates the number of available licenses not currently in use.
Should you purchase additional licenses in the future, you may be asked to provide a license context file by clicking the Download License Context File (C). New licenses can be uploaded using the Update License Update File button (D).
Since flexAI is a Linux based system, the firmware consists of multiple packages. So one my either update individual packages (meant for experienced users, developers and service) or all relevant packegaes for a complete release.
flexAI firmware can be updated in three ways:
From a firmware image on a USB stick plugged into a USB port
From a local image on a computer that is connected to the same network the flexAI hardware is part of.
From our online server - This is currently not available in the field.
The default view of the Update Page allows for the three steps of an update to a new flexAI release. From here you can select an update source (A) and start the update (B) and finally Reboot (C) the device to restart all processes.
Clicking the Setup icon (C) opens a window with options to:
Automatically update packages when a new release is installed (default = on)
Show advanced package management (meant for experienced users, development and service - default = off)
Only show Junger packages (default = on)
When Show advanced packet management is turned on it shows the installed packages (B) in detail. Use the Display column (A) to select whether All available packages are displayed at once or just the content from a specific section.
To begin an update, click on the Change Update Source button (A). A Choose Package Source window (B) will open. Click on the desired source. When the pop-up window appears, follow the on-screen instructions, which will vary slightly depending on the selected update source.
When pressing the EXECUTE UPDATE buton a "Refreshing Repository" progress window will appear:
After all files are copied to the internal memory of te flexAI device a "CAUTION" message appears:
Press PROCEED and be patient. Once the update is complete and the "Update Successful" window appears, reboot the hardware:
Important - Be sure to remove the processor from the on-air path before updating, as the unit will disconnect from the network, and audio will be interrupted during the update.
The Network menu includes setup and status information for DNS, NTP, PTP, Livewire Clock, SNMP, and each of the available LAN interfaces.
Select Network (A) from the System > Network menu to begin, then choose DNS (B) to open the DNS page. Displayed information (C) includes:
DNS State - Displays the IP address of the actual DNS server(s).
mDNS Node Name - Shows the name used for mDNS (Bonjour, Avahi)
DNS - Field for manually entering the IP address of a DNS server.
Select NTP (A) from the Network menu to open the NTP page. Displayed information (B) includes:
NTP State - Displays the current NTP server.
Enable NTP - Enables and disables NTP.
Use Fallback NTP - When enabled, uses the internet NTP servers at debian.pool.ntp.org if the unit cannot connect to the specified NTP servers.
NTP Server - Fields for entering up to four local NTP server addresses.
Select PTP (A) from the Network menu to open the PTP page. Displayed information (B) includes:
PTP Clock Domain - The field for entering the proper PTP clock domain.
PTP DSCP Class - Options include 0, 8 CS1, 10 AF11, 16 CS2, 18 AF21, 24 CS3, 26 AF31, 32 CS4, 34 AF41, 40 CS5, 46 EF (AES67), 48 CS6 (Ravenna), and 56 CS7. 48 CS6 (Ravenna) is the default setting.
Select Livewire (A) from the Network menu to open the PTP page. Displayed information (B) includes:
Mode - Choose "Follower" or "Disabled," as Livewire cannot act as a Leader.
Network Interface - Selects the network interface used for Livewire.
Locked to Leader - Indicates when Livewire is locked to the Leader clock.
Leader ID - The IP address of the Leader clock.
Offset - Displays the difference (delay) between the local clock and the Leader in microseconds.
Jitter - Displays the variations in delay between the local clock and the Leader in microseconds.
Select SNMP (A) from the Network menu to open the SNMP page. Displayed information (B) includes:
Enable - Enables and disables SNMP.
Community - Identifies the SNMP Community string.
Host Name, System Location, and System Contact - Populated fields from the System Setup menu.
Trap Sink IP Address - The IP Address of the SNMP trap receiver.
Trap Sink Port - The port of the SNMP trap receiver.
A total of four LAN interfaces are available. The LAN 1 CTRL and LAN 2 interfaces operate in a similar fashion to one another, so the information below applies to both.
LAN 3/4 differs from LAN 1 and LAN 2 in that they are internally connected by a switch to the network chip which is in turn connected to the SoM via a PCIe link. Therefore, they share the same IP Address, Gateway, MAC Address, and PTP settings.
Choose the individual Interface (A) for each LAN under the Network menu. In the example below, we've chosen the LAN 1 CTRL interface. Displayed information (B) includes:
Link Up - Indicates the presence of an active, working link (True or False).
Speed - The current link speed and type (100Mb/s, Full Duplex).
RX Bytes - Indicates the number of bytes received since the link was made active.
TX Bytes - Indicates the number of bytes transmitted since the link was made active.
RX Throughput Bps - The actual measured receive throughput.
TX Throughput Bps - The actual measured transmit throughput.
MAC Address - The MAC address of the interface.
Select IP (A) for the selected LAN under the Network menu.
The Current IP Addresses section (C) displays the current dynamic and static IP addresses.
When Use Dynamic Addresses (B) is enabled, the unit will automatically retrieve an IP address from the network's DHCP server. When disabled, the specified static IP address is used instead.
Static IP Addresses are listed in the Static Addresses window section (D). Clicking the Edit button (E) will open a pop-up window where the address type (IPv4 or IPv6) and subnet mask may be defined. Clicking the Delete button (F) removes the selected static IP address.
To add a new static IP address, click on the Add IP Address button (G), which will open a pop-up window where the address type, IP address, and subnet mask information can be entered.
Clicking the Restore Factory Defaults button (H) will set the LAN to DHCP and remove all static IP addresses.
Select Gateway (A) for the selected LAN under the Network menu.
The Current Gateways section (B) lists the current gateways.
The Static Gateways section (C) lists the IP addresses of any manually-added gateways along with any specific actions. To add a new gateway, click on the Add Gateway button (D) which will open a pop-up window to enter the new address.
Select PTP (A) for the selected LAN under the Network menu.
The Status section (B) contains the following information:
Hardware PTP Capable - Indicates when the Ethernet hardware is capable of extracting a PTP sync.
PTP Status - Options include None, Initializing, Faulty, Disabled, Listening, Pre-Leader, Leader, Passive, Uncalibrated, and Follower.
Locked to Leader - Indicates when PTP is synced to a Leader clock on the network.
Leader ID - Displays the MAC address of the PTP Leader.
Distance to Leader - Shows the number of hops between the Leader and flexAI unit.
Offset from Leader (us)
Mean Path Delay (us)
The Configuration section (C) contains the PTP Mode control. Options include Disabled and Follower, as flexAI cannot be used as a PTP Leader device.
When selecting USB DEVICE you must burn the *.iso file as an image to an USB stick. Don't simply copy that file to a stick! You may use the balena Etcher tool: or similar tools for macOS.
This is a display provided by Cockpit to show the storage usage in the system:
This is a graphical emulation of a SSH (Secure Shell) terminal. When you click on Terminal in the navigatin column (A) it opens in your (admin) home directory (B):
The Info menu provides a comprehensive list of various statuses. It is broken into five categories: SYSTEM, HARDWARE, SOFTWARE, SYSTEM LOAD and ABOUT.
Select Info (A) from the System menu to view the SYSTEM STATUS, which displays by default.
The Overall Status indicator (B) provides an overall indication of the system. A green "OK" doesn't necessarily mean that there are no abnormal statuses anywhere in the system, but rather that AIXpressor is functioning well overall.
Use the Type buttons (C) to view or filter specific types of statuses, including All, OK, Warning, Error, Info, and Inactive. Multiple buttons may be enabled simultaneously.
The Component dropdown (D) allows you to select which components are included in the detailed status report. Options include All, Service, System, Hardware, Audio Processing, Routing, Sync, Network, and Interfaces.
Clicking the Edit button (E) allows you to exclude certain groups of components from the system status page.
The HARDWARE STATUS page (A) is primarily meant for diagnostic and service purposes. It lists the current firmware version along with various temperature, fan, and power supply statuses. Example from an AIXpressor.
The SOFTWARE STATUS page (A) provides details about the software versions currently installed on a flexAI system.
The SYSTEM LOAD (A) page provides an aggregated view of the variuous system components that may have influence on the performance. When <Show Expert View> (B) is enabled it will provide a time weighted (integrated) display. In the bottom of the moving sections you see the legend of the various colors.
The flexAI systen is based on a Debian Linux distribution. It contains various software packages which are bound to GNU GPL (Genral Purpose Licenses). This page (A) lists all common and Debian package relevant license information. You may click on one of the <DETAILS> buttons (B) to download and read the respective license information.
Select Backup / Restore (A) from the System menu to view the backup and restore page.
To create a backup file containing all audio processing-related settings, click on the Download a Backup File button (B).
Important - The backup file is intended to restore a particular AIXpressor unit to its current state if unwanted changes are made, or if the unit had to be restored to its factory default settings. It is not possible to clone another AIXpressor using this backup file.
To restore the unit from a previously saved file, click on the Select a Backup File button (C), choose the appropriate file from your computer or network, then click the Restore button (D).
When connecting to a flexAI device by a browser you must now log in to it. A Sign In po-up appears:
Since flexAI version 2023-12r1 some features of the Open Source Project Cockpit:
have been introduced. It provides a comprehensive system to manage the underlaying OS by a graphical user interface. flexAI employs it for user management but also to provide detailed information about the built in storage capacity as well as offering a terminal dricetly from the UI.
When connecting to a flexAI device by a browser you must log in to it. A Sign In po-up appears:
The default credentials are User name: "admin" and Password: "admin".
After signing in, the initial page of the UI appears and the overall status of the system enters the ERROR sate. Clicking on the System Status icon in the upper right corner (A) :
It says that the password for the user admin is not set so you should do it as the very next step!
Cockpit shows all users of the system on this page. For the moment, only user admin (B) is relevant.
Click on the <Users> button (A) in the navigation bar at the left side:
For now only the password for the user admin (B) can be changed via the Users pane:
The other users are simply presented here FYI. They are generic system users meant for service and development applications and will used in a wider security concept by your IT team.
If you have forgotten your admin password you may reset it on the AIXpressor via the front panel menu. For a flexAIserver you must use the server adminstration tool (iDRAC for DELL) or you connect via SSH and start the system-menu as sudo.
Select Setup (A) from the System menu. Setup fields include:
Hostname - The hostname for this particular AIXpressor unit.
System Location - A "friendly" field for identifying the physical location of the unit within the facility.
System Contact - A "friendly" field for listing an administrator's name.