Skip to main content

NetAudio — unofficial Dante Controller alternative

NetAudio is an unofficial Dante Controller alternative for discovering, routing, configuring, and monitoring Dante network audio devices. The project provides open-source command-line tools, a web interface, a persistent daemon, and a protocol library for Linux, macOS, and Windows.

NetAudio is a native Dante Controller alternative for iOS and iPadOS, available now for iPhone and iPad through TestFlight. The app communicates directly with Dante devices for live discovery, audio subscription routing, device and channel configuration, live device metering, clock and status monitoring, and diagnostics. Local direct-device control runs on the phone or tablet without a separate computer, remote desktop session, or NetAudio daemon. The app also supports Dante Domain Manager (DDM) networks and connections to a NetAudio daemon.

Website and iOS app · Install the CLI and web interface · Quick start

Interfaces and architecture

NetAudio serves both interactive device control and software automation. A shared Rust protocol core implements Dante packet encoding and parsing for the Python application and native iOS client.

Interface Use
Native iOS/iPadOS app Discover, route, configure, and monitor devices from an iPhone or iPad using direct control or a NetAudio daemon. Available as a TestFlight beta.
Command-line interface (CLI) Inspect devices, manage subscriptions and settings, apply presets, and integrate with scripts using structured JSON output. Supports direct device access and daemon integration.
Web interface Control and monitor the network in a browser, served by the NetAudio daemon.
Background daemon Maintain network discovery, device inventory, monitoring, event history, and control services across client sessions.
HTTP API and live events Integrate network state and device control into other applications, with server-sent events (SSE) for live updates.
Protocol library Use the Rust core directly or through its C interface.

The CLI and daemon run on Linux, macOS, and Windows. Automated checks cover all three platforms, including native libraries and installed Python packages.

Capabilities

  • Discovery and routing: discover Dante devices and their receive/transmit channels, inspect subscription status, and add or remove audio subscriptions.
  • Device configuration: device and channel names, sample rate, encoding, latency, analog gain, device locking, preferred clock leader, AES67 settings, and primary/secondary network configuration on supported devices.
  • Audio flows: inspect receive and transmit flows, plan and manage supported native Dante multicast transmit flows, discover advertised AES67 audio streams, and subscribe compatible receivers to them.
  • Device metering and monitoring: live signal levels, clock status, interface statistics and errors, device diagnostics, monitoring issues, and event history through the CLI, API, and browser.
  • Dante Domain Manager: discover managed inventory and control supported settings on DDM-enrolled devices using configured credentials and operation permissions.
  • Presets and automation: save and apply device/routing presets, map device identities, inspect application results, and consume structured output from scripts and other control systems.

Device capabilities and the selected control transport determine which operations are available.

Installation

iOS and iPadOS (iPhone and iPad)

Install the native NetAudio iOS/iPadOS app through TestFlight. See netaudio.app for app information and support.

Linux, macOS, and Windows

Install the CLI, daemon, and web interface from PyPI:

uv tool install netaudio

Or with pip:

pip install netaudio

Arch Linux

Install the netaudio AUR package.

Containers

The daemon, web interface and MCP server also run as a container image, s00pcan/netaudio, for Linux hosts on the Dante network. Dante discovery, heartbeats and metering need the host's network, so the container shares it instead of getting its own. Docker Desktop on macOS and Windows runs containers inside a virtual machine that cannot see Dante traffic.

With Docker:

docker run -d --name netaudio --network host --init --restart unless-stopped \
  -v netaudio:/var/lib/netaudio s00pcan/netaudio
docker exec netaudio netaudio device list

From a checkout of this repository, docker compose -f containers/compose.yaml up -d does the same. Settings, the TLS identity, presets and MCP sign-ins are kept in the netaudio volume. Pass the options below with -e, or set them in containers/.env for Compose. The latest tag is the newest release, and edge is built from every change to master. To update, run docker pull s00pcan/netaudio, then remove and run the container again; with Compose, pull and then up -d.

To build the image yourself, use docker compose -f containers/compose.yaml -f containers/compose.build.yaml up -d --build. One machine builds both architectures without emulation: docker buildx build --platform linux/amd64,linux/arm64 --file containers/Dockerfile .

With systemd-nspawn (systemd 260 or newer), the same image runs without Docker. Save these settings as /etc/systemd/nspawn/netaudio.nspawn; they are also in containers/netaudio.nspawn:

[Exec]
Boot=no
KillSignal=TERM
Parameters=/usr/local/bin/netaudio daemon run
User=netaudio
WorkingDirectory=/var/lib/netaudio
Environment=HOME=/var/lib/netaudio
Environment=NETAUDIO_CONFIG=/var/lib/netaudio/config.toml
Environment=PYTHONUNBUFFERED=1
Environment=NOTIFY_SOCKET=
PrivateUsers=no
RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX AF_NETLINK

[Files]
Bind=/var/lib/netaudio

[Network]
Private=no
VirtualEthernet=no

Then name the container after this host, so the certificate, Bonjour name and MCP address use the host's name, pull the image, and start it now and at boot:

sudo sed -i "/^\[Exec\]/a Hostname=$(hostnamectl hostname)" /etc/systemd/nspawn/netaudio.nspawn
sudo importctl pull-oci --class=machine docker.io/s00pcan/netaudio:latest netaudio
sudo install -d -o 10001 -g 10001 -m 0750 /var/lib/netaudio
sudo machinectl enable --now netaudio
journalctl -u systemd-nspawn@netaudio -f

To update, stop the container, pull again with --force, and start it:

sudo machinectl stop netaudio
sudo importctl pull-oci --force --class=machine docker.io/s00pcan/netaudio:latest netaudio
sudo machinectl start netaudio

Settings and state live in /var/lib/netaudio on the host, including config.toml; add Environment= lines for the options below. To run CLI commands inside the container, save this as /usr/local/bin/netaudio and use sudo netaudio device list:

#!/bin/sh
exec nsenter --target "$(machinectl show netaudio --property=Leader --value)" --all \
  --setuid 10001 --setgid 10001 \
  env HOME=/var/lib/netaudio NETAUDIO_CONFIG=/var/lib/netaudio/config.toml netaudio "$@"

Container options, as environment variables:

Variable Purpose
NETAUDIO_INTERFACE Network interface for Dante traffic on hosts with more than one
NETAUDIO_DAEMON_PORT Plain HTTP port, loopback only while HTTPS is on (default 4780)
NETAUDIO_TLS_PORT HTTPS port for the web interface, apps and MCP (default 4781)
NETAUDIO_TLS_CERTIFICATE, NETAUDIO_TLS_KEY Your own certificate and key, mounted into the container and readable by user 10001
NETAUDIO_NO_SSL true serves plain HTTP on the network instead of HTTPS
REDIS_HOST, REDIS_PORT, REDIS_SOCKET, REDIS_DB, REDIS_PASSWORD Publish device state to this Redis server

The host firewall must allow the HTTPS port from clients, and UDP from the Dante network for discovery, heartbeats and metering.

From source

A source checkout requires Python 3.10 or newer, uv, and a Rust toolchain:

uv sync
uv run netaudio --help

Quick start

Start the daemon and open the web interface:

netaudio daemon start
netaudio daemon web --open

Use netaudio --help for the command list and netaudio COMMAND --help for individual commands. From a source checkout, use uv run netaudio.

For example, inspect a device by name and request JSON output:

netaudio -n avio-usb-1 device show
netaudio --json -n avio-usb-1 device show

Use your device's name in place of avio-usb-1. Put device filters before the command: -n matches names (including quoted patterns such as 'avio-*'), -s matches server names, -m matches MAC addresses, and --host selects an IP address.

Commands that change a device send the change and return. Add --verify before the command to wait until a fresh readback confirms it.

Channels and routing

Channels use tx:NUMBER or rx:NUMBER; a channel name can replace the number. For example, rename input 1 and connect output 1 of stagebox to it:

netaudio -n avio-usb-1 channel name rx:1 vocal-in
netaudio subscription add --tx tx:1@stagebox --rx rx:1@avio-usb-1

Remove that subscription with:

netaudio subscription remove --rx rx:1@avio-usb-1

Presets

Save selected devices, then preview the saved settings before applying them:

netaudio -n 'avio-*' preset save stage
netaudio preset show stage
netaudio preset load stage

preset show reads current device state but makes no changes. Presets are XML files in presets/ beside the configuration file; use preset list to see them, or supply an explicit .xml path. Saving over an existing file requires --force.

Configuration and troubleshooting

The daemon serves HTTPS on port 4781 with a self-signed certificate that it creates and renews automatically. Plain HTTP on port 4780 stays available on loopback for the local CLI and browser. netaudio daemon web lists the addresses.

To use your own certificate or other ports, add these settings to the configuration file shown by netaudio config path and restart the daemon:

[daemon]
tls_certificate = "/path/to/certificate.pem"
tls_key = "/path/to/private-key.pem"
tls_port = 4781
port = 4780

To serve plain HTTP on the network instead, set no_ssl = true under [daemon].

The daemon can publish device state to Redis for other programs. Install netaudio[redis] and name the server; without a [redis] section the daemon does not use Redis:

[redis]
host = "localhost"
port = 6379

The daemon follows this computer's JACK and PulseAudio audio only when host_audio = true is set under [daemon] and JACK or PulseAudio is installed.

netaudio config path shows which configuration file is used. For a DDM network, netaudio ddm login --default guides you through connecting to a server and choosing a domain.

Use netaudio daemon status to check the daemon and netaudio daemon logs -f to follow its logs. Logs default to warnings and errors. To run in the foreground with detailed logging, stop the background daemon first:

netaudio daemon stop
netaudio --log-level DEBUG daemon run

The browser's Events page keeps recent events and issues in memory. Restarting the daemon clears them. Use netaudio events export --file events.json to save the current event history before restarting.

Development

The project develops an independent implementation and understanding of Dante control protocols. Protocol work is recorded in reviewed source, focused tests, and evidence records identifying observed behavior and remaining unknowns. Research tooling is separate from normal application use.

Run the shared local/CI checks for the current host, using installed dependencies:

make check-local

This incrementally builds the Rust core, selects that library for Python tests, and checks the native ABI, generated interfaces, formatting, lint, types, Rust tests, Python tests, and web unit tests. The run has a five-minute total limit. Its printed report path contains results, per-check logs, source identity, and the tested library digest. Failed checks stop the run; timeouts are incomplete.

Run only source-quality/native checks or select another check group:

make quality
.venv/bin/python scripts/check_project.py --scope python --offline
.venv/bin/python scripts/check_project.py --scope webapp --offline

The manually dispatched CI workflow uses the same check commands. Browser tests and installed-wheel/platform matrices are separate, explicitly selected checks.

make audit checks uv.lock and the Rust core's Cargo.lock for known vulnerabilities, and make audit-fix upgrades the affected packages and audits again. The daily security workflow runs the same audit on master and the latest release, and rebuilds the published container images when their Python base image is updated.

Project background

NetAudio is an independent interoperability project and is not affiliated with or endorsed by Audinate.

The project grew out of packet capture replay and modification experiments first written up in a Gearspace discussion.

Metadata

Release files for netaudio 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for netaudio 0.4.0
File Size Uploaded
netaudio-0.4.0.tar.gz 1.4 MB Details

Built distributions (wheels)

Table of built distributions (wheels) for netaudio 0.4.0
File
netaudio-0.4.0-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details
netaudio-0.4.0-py3-none-manylinux_2_28_x86_64.whl Python 3 none Linux glibc 2.28+ x86-64 Details
netaudio-0.4.0-py3-none-manylinux_2_28_aarch64.whl Python 3 none Linux glibc 2.28+ ARM64 Details
netaudio-0.4.0-py3-none-macosx_11_0_x86_64.whl Python 3 none macOS 11.0+ x86-64 Details
netaudio-0.4.0-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details

Total release size: 17.0 MB

Release files / netaudio-0.4.0.tar.gz

Download URL netaudio-0.4.0.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
8cb6f16191c89c089fc02914bf5882a14c98cbf176cccf0d4b2f3151b8986d65
BLAKE2b-256 checksum
How to use checksums
1b659d1bcc5d699dbfd3ff161bc36ea697dfd872a4a442dbb574fcee9c0112ac
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Release files / netaudio-0.4.0-py3-none-win_amd64.whl

Download URL netaudio-0.4.0-py3-none-win_amd64.whl
Size 3.1 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
971c54dc006051204deb5349fe904ba30a8712948fcbabd0ca4d0d06ed178561
BLAKE2b-256 checksum
How to use checksums
3b235d3590d43816924ea434db993217d0dbecae8e2c91e8a4d22e9e0ae4d54a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Release files / netaudio-0.4.0-py3-none-manylinux_2_28_x86_64.whl

Download URL netaudio-0.4.0-py3-none-manylinux_2_28_x86_64.whl
Size 3.2 MB
Tags Linux glibc 2.28+ x86-64 Python 3
SHA-256 checksum
How to use checksums
3ab4ebee8350f87d65aada823b0aae2afcc7ec7994fa0cb20d7087088a101382
BLAKE2b-256 checksum
How to use checksums
4d24ff785e48daab82c8c642016d1e3c33b12917e659c8c2247fa7e11c3162a7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Release files / netaudio-0.4.0-py3-none-manylinux_2_28_aarch64.whl

Download URL netaudio-0.4.0-py3-none-manylinux_2_28_aarch64.whl
Size 3.2 MB
Tags Linux glibc 2.28+ ARM64 Python 3
SHA-256 checksum
How to use checksums
e137facbf42cfd3b22391edb6cc307dcce47f554746c83d4296a77db7e6cf0d6
BLAKE2b-256 checksum
How to use checksums
e1136c5842d7274cdbf321ca5996a3b855a3d7b57b487a0e082a428811fc9a53
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Release files / netaudio-0.4.0-py3-none-macosx_11_0_x86_64.whl

Download URL netaudio-0.4.0-py3-none-macosx_11_0_x86_64.whl
Size 3.1 MB
Tags Python 3 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
92eb81fecbcb598d14706653ca3092c150e5a435094a46b4716eea55c30ecd3c
BLAKE2b-256 checksum
How to use checksums
da7abe4662e8dcb92940b35823d147fa99befa201fc0bfc6b85c4f260913ea94
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Release files / netaudio-0.4.0-py3-none-macosx_11_0_arm64.whl

Download URL netaudio-0.4.0-py3-none-macosx_11_0_arm64.whl
Size 3.0 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3c0ea1cd12f08fdd576b266899817cd3fc66a8b85960338d5defda6d282bd255
BLAKE2b-256 checksum
How to use checksums
53f525c51a5c408b22b7b87648748884a0f8d1be2829e1500ae9fd8b20e7b6d2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.2

6 release files

0.4.1

6 release files

This release

0.4.0 This release

6 release files

0.3.14

6 release files

0.3.13

6 release files

0.3.12

6 release files

0.3.9

6 release files

0.3.7

6 release files

0.3.6

6 release files

0.3.5

6 release files

0.3.4

6 release files

0.3.3

6 release files

0.3.1

6 release files

0.3.0

6 release files

0.2.5

5 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page