The dMix 128 family uses two Ethernet network ports for two very different jobs: carrying control (the settings, gain, routing and metering exchanged with the mixer GUI and remote software) and carrying audio (live multichannel streams to and from computers and other devices). This guide walks through each connection method in the order you are most likely to need it — starting from a single cable on a bench, through a managed network, the audio driver, and finally Dante / AES67 streaming. The control port only carries control settings, while the dNet ports can carry control and audio at the same time.
Reaching the mixer to configure it — IP settings, naming, routing, firmware.
Moving up to 128 × 128 channels between a computer and the dMix 128 via the CoreAudio / ASIO driver (still over AES67).
Exchanging standards-based multicast audio with other dMix 128 units and AES67-based systems (320 channels).
| Item | Value / behaviour |
|---|---|
| AES67 ports | 2 dedicated AES67 network ports (dNet1 is only enabled in V1 firmware) |
| Network channels | Up to 320 network channels on the dMix 128. |
| IP mode | Manual or Auto (set per device in its configuration page). |
| Multicast base | Default 239.200.0.0 — the AAA octet (200) is configurable as 239.AAA.0.0. |
| Clocking | Auto — IEEE 1588 (PTP) chooses the master automatically; or Forced to nominate one. |
| Audio driver | CoreAudio (macOS) and ASIO (Windows), 128 × 128 channels at 48 kHz or 96 kHz. |
| Sample rates | 48 kHz or 96 kHz, set on the mixer. |
Whatever method you use, the golden rule is that the device you are connecting from and the dMix 128 must sit on the same IP subnet. Most connection problems come down to a mismatch here — keep this in mind as you read each section.
This is the fastest way to reach a dMix 128 on a bench or at front-of-house when there is no network in place: a single Ethernet cable straight from your computer to the mixer. No router, switch or DHCP server is involved. Both ends fall back to a self-assigned link-local address (the 169.254.x.x range), which puts them on the same subnet automatically.
169.254.x.x address within a minute.169.254.x.x range — they are now on the same link-local subnet.dmix.local into the address bar). The dMix 128 should appear and connect. It may take a few seconds for the name server to propagate (DNS) and for the browser to detect it for the first time.169.254. If one end has a 192.168 or 10.x address, it is on a different subnet — disable other adapters (Wi-Fi, secondary NICs) that may be steering traffic.
For anything beyond a quick bench check — multiple devices, a control laptop, audio computers and AES67 endpoints all together — connect everything through a router or managed switch. The router hands out IP addresses (DHCP) and keeps every device on one subnet, and a managed switch lets you keep the audio traffic healthy.
192.168.1.0/24). Open the control software and connect.Fixed addresses are recommended for installed or touring systems because a device always lives at a known location. Set every device manually within one subnet:
192.168.1.20, computer 192.168.1.50, mask 255.255.255.0.
To record from or play back to the dMix 128 from a computer, install the dMix audio driver. It presents the mixer to your DAW or media software as a standard audio interface — CoreAudio on macOS, ASIO on Windows — carrying up to 128 channels in each direction.
violetaudio.com).
Every dMix on the network has one control IP address. How it gets that address decides how you find it:
192.168.1.x); with no DHCP server it self-assigns a link-local address in the 169.254.x.x range.Read the address straight off the unit. Connect a compatible DisplayPort screen to the unit and navigate to the Settings page — you will then see the IP address.
Your computer and the dMix must be on the same subnet. If your Mac is on 169.254.x.x and the dMix is on 192.168.1.x, no scan will find it. Confirm your own address first, then scan within that range.
First find which interface faces the dMix and what address it holds. Ethernet adapters are usually named en1, en5, en7, etc.; Wi-Fi is typically en0.
# List every hardware port and its device name (en0, en7 ...)
networksetup -listallhardwareports
# Your IPv4 address on a given interface
ipconfig getifaddr en7
# Full detail incl. subnet mask
ifconfig en7 | grep "inet "
macOS keeps a table mapping IP addresses to MAC (hardware) addresses for devices it has recently spoken to. List it with:
arp -a # every cached neighbour
arp -i en7 -a # only the interface facing the dMix
If the dMix is not listed yet, “wake” the whole subnet with a quick ping sweep, then read the table again. Adjust the 192.168.1 prefix to match your own address:
# Ping every host on a /24, in parallel, then show the table
for i in $(seq 1 254); do ping -c1 -W200 192.168.1.$i >/dev/null & done; wait
arp -an
A dedicated ARP scanner is faster and more reliable than a ping sweep, because it finds devices even when they ignore ICMP. Install either tool once with Homebrew:
brew install arp-scan
# Scan the subnet on the chosen interface (lists IP, MAC, vendor)
sudo arp-scan --interface=en7 --localnet
# For a link-local (169.254) direct connection
sudo arp-scan --interface=en7 169.254.0.0/16
brew install nmap
# Ping-scan a subnet (run with sudo to also show MAC + vendor)
sudo nmap -sn 192.168.1.0/24
dns-sd -B _services._dns-sd._udp local. # list advertised service types
ping dmix-foh.local # if the unit has an mDNS name
Open Command Prompt or PowerShell and read your own configuration. Note the adapter that faces the dMix, its IPv4 address, subnet mask and Physical Address (your MAC).
:: Command Prompt
ipconfig /all
# PowerShell equivalent
Get-NetIPConfiguration
:: Show the current IP-to-MAC table
arp -a
If the dMix is missing, sweep the subnet to populate the table, then list it again.
:: Command Prompt: ping each host (use %%i inside a .bat file)
for /L %i in (1,1,254) do @ping -n 1 -w 200 192.168.1.%i >nul
arp -a
PowerShell gives a cleaner neighbour list:
# Sweep, then show reachable IPv4 neighbours with their MACs
1..254 | ForEach-Object { Test-Connection "192.168.1.$_" -Count 1 -Quiet }
Get-NetNeighbor -AddressFamily IPv4 | Where-Object State -ne Unreachable
nmap -sn 192.168.1.0/24.This is where Mac users most often get caught out: plug a Mac into an audio network and suddenly the internet “stops working,” or the control software cannot see the dMix. The cause is almost always the network service order.
macOS tries network services from the top of the list down. Crucially, the order only decides the default route — where traffic goes when its destination is not on any directly-connected network (i.e. the internet). Traffic to a directly-connected subnet, such as the dMix's, always leaves through the matching interface regardless of order. That single fact is the key to keeping both working at once.
169.254 connections have no gateway anyway.)The same ordering is scriptable. The set command must list every service, in the order you want them:
# View the current order and the device each service maps to
networksetup -listnetworkserviceorder
# Set the order (names must match exactly; list ALL services)
networksetup -ordernetworkservices "Wi-Fi" "Ethernet" "USB 10/100/1000 LAN"
# Inspect a single service (IP, router, etc.)
networksetup -getinfo "Ethernet"
VPN connections always take priority and cannot be reordered. If a VPN is active, it sits above everything in the list.
Windows decides the preferred connection with an interface metric. A lower metric wins — the adapter with the smallest metric is used for the default route. The same blank-gateway trick applies as on macOS.
ncpa.cpl (Control Panel → Network Connections). Right-click the adapter → Properties.10, audio adapter 50).# View interfaces sorted by metric (lowest = preferred)
Get-NetIPInterface -AddressFamily IPv4 | Sort-Object InterfaceMetric
# Prefer the internet adapter, de-prioritise the audio adapter
Set-NetIPInterface -InterfaceAlias "Wi-Fi" -InterfaceMetric 10
Set-NetIPInterface -InterfaceAlias "Ethernet" -InterfaceMetric 50
On the audio adapter's IPv4 properties, set a static IP and subnet mask but leave the Default gateway empty. Windows then installs no default route through that NIC, so it cannot hijack your internet — yet the dMix's subnet stays directly reachable.
| Task | Command | OS |
|---|---|---|
| Your own IP | ipconfig getifaddr en7 | macOS |
| Your own IP | ipconfig /all | Windows |
| List neighbours | arp -a | Both |
| Best scan | sudo arp-scan --localnet | macOS |
| Best scan | nmap -sn 192.168.1.0/24 | Both |
| View priority | networksetup -listnetworkserviceorder | macOS |
| View priority | Get-NetIPInterface | Windows |
| Set priority | networksetup -ordernetworkservices ... | macOS |
| Set priority | Set-NetIPInterface -InterfaceMetric n | Windows |
| Symptom | Likely cause & fix |
|---|---|
| Scan finds nothing | You and the dMix are on different subnets. Check your own address first; scan within that range. A device on 169.254.x.x cannot see one on 192.168.x.x. |
| arp shows (incomplete) | The device has not answered yet. Ping it (or the subnet) once, then read the table again. |
| Internet drops when audio NIC is plugged in | The audio adapter became the default route. Raise its metric (Windows) or lower its service-order position (macOS), or leave its gateway blank. |
| Control software still cannot connect | Two adapters may share one subnet, or Energy-Efficient Ethernet / a firewall is interfering. Use distinct subnets and disable EEE on audio ports. |
| Found by name but not IP | The unit is advertising via Bonjour/mDNS. Use its .local name, or scan with arp-scan to resolve the actual address. |
AES67 is the open standard that lets audio cross between different manufacturers' systems. The dMix 128 transmits and receives AES67 multicast streams natively from its two AES67 ports, using its configurable multicast base (default 239.200.0.0) and an IEEE 1588 (PTP) clock. To exchange audio with a Dante-based system, the Dante devices must first be switched into AES67 mode in Dante Controller. The steps below cover both sides and the all-important clock alignment between them.
239.200.0.0 sits inside the 239.x/16 range that AES67 receivers expect, so leave it unless you have a specific reason to change it.239.x). If the prefixes differ, a subscription can look successful but pass no audio.Dante / third-party → dMix 128
$mixer-foh.i.2.src = $stage-center.n.1.dMix 128 → Dante / third-party
239.x/16 rule: the receiver's multicast prefix must match the transmitting flow or no audio will pass.Between two Dante devices, Dante's own transport is always used — even with AES67 enabled on both. AES67 only comes into play when one end is a non-Dante device, such as the dMix 128 talking to a Dante system, or a Q-SYS / Ravenna endpoint. Presets do not store AES67 flows, so recreate flows after loading a preset.
| Goal | Use | Section |
|---|---|---|
| Quickly configure a mixer on a bench | Direct cable, IP Mode = Auto | 1 |
| A permanent multi-device system | Router / managed switch, fixed IPs | 2 |
| Record / play back from a computer | CoreAudio or ASIO driver | 3 |
| Share audio with Dante / Q-SYS / Ravenna | AES67 multicast streams | 10 |
| Symptom | Likely cause & fix |
|---|---|
| Control software cannot find the dMix 128 | Different subnets. Confirm both ends share a range (169.254.x.x direct, or one router subnet). Disable extra network adapters. |
| Audio dropouts / clicks | Energy-Efficient Ethernet enabled, or an unmanaged switch. Disable EEE; use a managed gigabit switch with IGMP snooping. |
| AES67 subscription shows connected but no audio | Multicast prefixes do not match. Set both ends inside 239.x/16. |
| Clock errors on the network | PTP not aligned. Check Clock Status; confirm one PTPv2 master and that switches pass PTP. |
| AES67 flow disappeared after recall | Presets do not store AES67 flows. Recreate the multicast flow after loading. |
You can always connect a screen to the dMix 128 to read the IP address it is set to. A full recovery mode is also possible via a connected phone — see Part 2.
Using the mobile-device recovery interface at 10.10.10.10 — restore firmware, back up or restore data, upgrade firmware and review network settings.
This guide explains how to connect a mobile device to the dMix 128 in recovery mode, open the browser interface, restore firmware, back up or restore data, upgrade firmware, and review network settings.
Recovery mode is a built-in service mode hosted directly by the dMix 128. When a phone or tablet is connected by USB-C, the mixer serves a local browser interface at 10.10.10.10. No internet connection is required.
Recovery mode is intended for service, recovery, maintenance, and firmware work. Audio operation and normal mixer control should be handled from the normal dMix 128 interface.
| Item | What to check |
|---|---|
| USB-C cable | Use a reliable USB-C cable connected directly between the mobile device and the dMix 128 recovery USB-C connection. |
| Mobile device | Use a phone or tablet with a web browser. Put it into Airplane Mode before opening the recovery page. |
| Power | Make sure the dMix 128 is powered and stable. Do not interrupt power during firmware installation. |
| Firmware file | For upgrades, use the correct signed firmware file or full image supplied for the dMix 128. |
10.10.10.10 into the address bar.Type 10.10.10.10 directly into the address bar. Do not search for it in Google.
Use Restore Factory Firmware when the mixer needs to roll back to the protected factory base. This rolls back firmware and resets network / settings. Shows are kept unless you explicitly erase user data.
Restore Factory Firmware keeps shows. Erase All Shows & Presets permanently deletes user data.
The screenshots show both .dmiximg and .zip files. Use the official firmware package supplied for the recovery process.
While the screen shows Full Image Flash or writing blocks, do not unplug USB-C, remove power, or restart the device.
10.10.10.10 again.
Before erasing data, restoring firmware, or performing major service work, export a backup where possible.
Note: the dMix 128 does not have a Wi-Fi Hotspot or Client, but other products in the range may include them.
The Settings screen states that these settings apply when the device boots normally, not only while recovery mode is active.
| Symptom | What to do |
|---|---|
| Browser will not open 10.10.10.10 | Check USB-C connection, confirm Airplane Mode is on, and re-enter recovery mode by holding RESET for 5 seconds. |
| Connection Lost dialog appears | This is normal after reboot or if the device restarts. Tap RELOAD after the mixer has restarted. |
| Upgrade button is disabled | Select a signed firmware file first, or confirm a USB storage device with a valid firmware image is attached. |
| USB firmware file not shown | Check the USB storage device, file name, firmware type, and that the package is intended for dMix 128 recovery. |
| Changes applied banner stays visible | Tap REBOOT NOW to activate the applied settings or firmware. |
| Network still wrong after reboot | Open Settings, use RESET NETWORK TO DEFAULTS, Save if required, then reboot. |
10.10.10.10.Violet Audio dMix 128 — Networking & Recovery Guide. © Violet Audio. All rights reserved.