The dMix 128 supports AES67 natively, including full PTPv2 synchronization and up to 48 bidirectional network-audio streams. Support for ST 2110-30 (PCM audio) is currently in development and is scheduled for release within the next 4 months.

Supported now

• AES67 compliant audio streaming
• PTPv2 / SMPTE-2059-2 timing
• Up to 48 simultaneous streams, 2–8 channels each → up to 384 channels each way

Coming soon

• ST 2110-30 (Class A) native send/receive

AES67 is native on the main network ports. ST 2110-30 will be native as part of a firmware update (no option card required). ST 2110-31 is not implemented and currently not planned.

Sample rates

• 48 kHz and 96 kHz
• PCM 24-bit
• Packet times: 83 μs, 125 μs, 250 μs, 1 ms

The dMix 128 uses PTPv2 following the AES67 / SMPTE-2059 profile with BMCA master election. It can operate as a PTP follower or as a PTP master when configured accordingly.

Supported clock behaviour

• PTP follower (standard mode)
• PTP master (device can assume master role when set to clock master)

Not supported

• PTP Boundary Clock
• PTP Transparent Clock

PTP settings

• Profile: PTPv2 (AES67 / SMPTE-2059-2 compliant)
• Domain: 0 (AES67 default)
• Priority 1:
  • Default = 128
  • Set to 1 when dMix128 is manually configured as clock master
• Priority 2: Default values

Switch requirements

• IEEE-1588 aware switching strongly recommended
• QoS for PTP, RTP, and SAP
• Multicast IGMPv2 or IGMPv3

Current capabilities

The dMix 128 supports full AES67 interoperability with Dante, Q-SYS, RAVENNA, and 2110-30 equipment that supports AES67 mode. It uses SDP-based stream description and standard multicast subscription control.

Not yet implemented

• NMOS IS-04 / IS-05 (Discovery & Connection Management) → Planned for a future major update
• ST 2022-7 Seamless Protection Switching → Not implemented today

Real-world deployments

The dMix 128 has been tested in mixed AES67 environments with:

• Dante/AES67-enabled broadcast consoles
• Q-SYS systems
• RAVENNA-based networks
• Generic PTP master/slave network clocks

The dMix 128 operates natively at 96 kHz and maintains extremely low end-to-end latency even in complex DSP workflows.

96 kHz operation (native DSP rate)

Analog → AD → Network → DSP → DA → Analog ≈ 0.7 ms total round-trip.

48 kHz operation

Upsampling/downsampling adds conversion stages: ≈ 1.3 ms total (typical).

DSP impact

All channel processing, including EQ, dynamics, filters and routing, occurs at 96 kHz, maintaining extremely low additional latency.

Supported

• Ring topology redundancy when multiple dMix units are linked
• Dual power-supply redundancy (internal)
• Ability to create redundant AES67 links via network switches
• Auto-recovery after reboot or brown-outs
• Real-time fault monitoring & logging

Not currently supported

• ST 2022-7 seamless A/B stream redundancy
• Automatic fallback to alternate multicast stream sources

The system provides a fully documented open API for integration with consoles, controllers and automation systems.

Supported control protocols

• REST API (full parameter depth)
• WebSocket real-time control
• OSC
• MIDI
• Examples and libraries in Python, C++, Go
• Templates for Q-SYS, HiQnet, and generic install-control systems

Controllable parameters

• Preamp gain / phantom power
• Routing & crosspoints
• EQ, filters, dynamics
• Delays
• Bus configuration
• Snapshots & scene recall
• Mutes, solos, groups, channel labels
• And more...

Third-party consoles can control all parameters; control depth is not restricted.

Examples:

• A broadcast console can remote-control analog gain on dMix inputs.
• A monitor desk can adjust EQ & dynamics on network audio returns.
• FOH can run scene changes via OSC or API.

Templates and workflows exist for:

• DiGiCo
• Yamaha
• Q-SYS
• Install controllers (Crestron/AMX/Extron via API)
• Generic OSC-based live consoles

Typical workflow examples

• FOH → Monitors → Broadcast Split: 128 internal channels, 384 network channels, zero need for external stageboxes.
• Recording truck integration: AES67 streams directly from the dMix into recording DAWs or 2110-enabled interfaces.
• Network-based patching: dMix 128 as a central routing core with 20M+ crosspoints.

Yes. The dMix 128 web interface allows multiple units to be displayed and controlled simultaneously from any screen, locally or remotely.

Capabilities include:

• Multiple units displayed simultaneously on any screen
• Remote control locally or from overseas
• Device health & thermal monitoring
• Firmware version management
• Event logging & fault reports
• Network diagnostics
• Cluster-wide configuration
• No special software required — standard web browser only

Routing capacity

• Up to 20,000,000 crosspoints (significantly more than typical competitors)

Integrated architecture

• Mixer + DSP + Matrix + AES67 + MADI + expansion cards
• One unified 96 kHz architecture
• No need for multiple chassis or external DSP units

Scalability

• Fully modular channel count
• Expandable network-audio capacity
• DSP performance does not degrade with routing load

Cost efficiency

• High channel count per dollar
• No per-stream licensing fees
• No DSP card limitations

The dMix 128 follows a matrix-core architecture, but with the flexibility of a modular toolbox.

Integrators can shape the device to match any workflow (broadcast core, live split engine, install matrix, conference DSP, etc.).

This provides:

• A central high-power DSP engine
• Software-defined routing and mixing
• Ability to behave as a console, a matrix, or a hybrid

dMix 128 provides:

• Dual redundant PSU
• Auto-recovery on brown-out or hardware restart
• Event logging and error reporting
• Standard IP network redundancy (ring topology)
• Safe firmware system (A/B bank coming soon)

Typical interoperability examples:

• Dante consoles running AES67 mode → dMix 128
• Lawo/Calrec 2110 routers (AES67 fallback) → dMix 128
• RAVENNA-based systems → dMix128
• Q-SYS → full control & audio exchange
• MADI consoles via optional interface
• DAWs via AES67 (Reaper, Pro Tools via Ravenna/AES67 drivers)

The open API and open network-audio implementation allow the dMix 128 to sit inside any mixed-manufacturer ecosystem.

General positioning

• More competitive for large channel counts
• No paid audio-stream licenses
• High IO density per dollar
• DSP included — not modular add-on cards

Systems requiring 400–700 network I/O channels tend to be significantly more cost-efficient with dMix 128.

Compared to similar platforms, the dMix 128 reduces cost over 5–7 years.

Advantages:

• No costly option cards or expansion DSP
• Free firmware updates
• Built-in 96 kHz DSP (no upgrade needed)
• Cheaper servicing and easier field repair
• Higher channel count per unit, reducing rackspace and power
• Flexible architecture reduces need for ancillary gear (matrices, DSP cores, converters, etc.)

These are the reset options:

The dMix 128 provides two hardware reset modes depending on how long the reset button is held while the device is powered on.

Reset mode 1 – Network reset (3 seconds)

With the unit powered on, press and hold the reset button for approximately 3 seconds.

• The red LED will turn on.
• The blue LED remains unchanged (may appear violet).
• The device IP configuration is reset to DHCP.
• After reboot, the unit returns to the previous configuration (routing, DSP and system settings are preserved).

Reset mode 2 – Factory reset (10 seconds)

Press and hold the reset button for approximately 10 seconds.

• At 3 seconds, the red LED turns on.
• At 10 seconds, the LED turns off.
• The unit will reboot automatically.
• The device returns to factory configuration:
• IP mode: Auto IP
• Device name: dmix.local
• No mixer setups (all mixer configurations are cleared)