KanexPro Support Assistant

Describe your setup, the part number, and what you are seeing.

Before we start

So the team can follow up if this needs a person.

Used only to follow up on this request. See our Privacy Policy.

General enquiry

Tell us what you need and the right person will come back to you.

Used only to answer you. See our Privacy Policy.

Support Knowledge base Flex Matrix Pro

White Paper: Dante/AES67-Native AV Matrix — Part 1: Eliminating the AV/IT Audio Divide

White Paper — Part 1 of 2

Dante/AES67-Native AV Matrix Infrastructure

Eliminating the AV/IT Audio Divide with Flex Matrix Pro

Executive Summary

In most enterprise AV installations, audio is a second-class citizen. Video routing is handled by the matrix switcher. Audio routing is handled by a separate DSP, separate audio matrix, or analog cables no one fully documents. The result is two routing planes, two control interfaces, two firmware cycles, and two failure modes — all to distribute a single AV signal.

The KanexPro Flex Matrix Pro eliminates this division. Every I/O card — HDMI, DisplayPort, HDBaseT, Fiber, and 12G-SDI — ships with native Dante/AES67 audio networking built in at the card level. This white paper explains why that matters and how to design a Flex Matrix Pro installation that fully leverages it.

1. The Problem: Parallel AV Infrastructure

Traditional enterprise AV separates video and audio at the architectural level, creating four persistent operational problems:

  • Routing sync failures: Video routes to Display B while audio still points to Display A — one of the most common AV support calls in corporate environments.
  • Dante bridging cost: Adding Dante to a non-native matrix requires external AVIO hardware at every audio I/O point.
  • Control fragmentation: The video matrix, DSP, and audio matrix each have separate control APIs.
  • Double maintenance scope: Two independent systems to monitor, update, and troubleshoot.

Dante/AES67-native matrix switching addresses all four problems at the architectural level — not through workarounds, but by eliminating the separation between video and audio routing infrastructure.

2. Card-Level Dante: Why It Matters

In the Flex Matrix Pro, Dante/AES67 is implemented at the I/O card level — not chassis level. A chassis-level implementation provides a fixed number of Dante channels that don’t scale with I/O expansion. A card-level implementation scales Dante channel count directly with installed cards. Each card provides a dedicated Dante/AES67 network port, appears as an independent Dante device in Dante Controller, supports AES67, and is DDM compatible. A FLEX-PRO32X32 at full population appears as 16 independent Dante devices on the network.

3. Five Signal Formats with Native Dante

FormatCardsDante Note
HDMI 2.0FLEX-PROHDMI-IN / OUTHDMI embedded audio extracted at card — no breakout hardware
DisplayPort 1.2FLEX-PRODP-IN / OUTCritical for UC endpoints where DP dominates workstation connections
HDBaseT/CATFLEX-PROCAT-IN / OUT330ft over CAT6A. PoC on output powers TX units. Dante independent at card.
Fiber OpticFLEX-PROFIB-IN / OUTSM to 2km / MM to 300m. Dante extracted regardless of transmission distance.
12G-SDIFLEX-PROSDI-IN / OUTSDI embedded audio extracted at card — eliminates SDI de-embedder hardware

4. Chassis Sizing

ChassisMax I/OMax CardsMax Dante Devices
FLEX-PRO16X1616×1688
FLEX-PRO32X3232×321616
FLEX-PRO64X6464×643232
FLEX-PRO128X128128×1286464

5. AES67 Interoperability

Flex Matrix Pro’s AES67 compliance enables direct audio exchange with Shure, Sennheiser, and Audio-Technica wireless systems; QSC, Biamp, and BSS DSPs; Yamaha and Allen & Heath consoles; and any AES67-compliant device — without analog or AES3 bridging hardware.

Continued in Part 2: System Design, Control Integration & Deployment Scenarios