What is Audio over Internet Protocol (AoIP)?

Audio over Internet Protocol (AoIP) is a digital networking technology that encodes, transmits, and receives high-quality audio signals over standard Ethernet networks using IP-based protocols. Unlike traditional point-to-point analog or digital audio cabling (such as XLR, AES/EBU, or MADI), AoIP treats audio as data packets that can be routed, switched, and shared across local area networks (LANs), wide area networks (WANs), and even the public internet. This shift from dedicated audio infrastructure to shared networking infrastructure has fundamentally changed how audio production environments are designed, scaled, and operated.

The core idea behind AoIP is to replace multiple dedicated cables with a single network cable, carrying dozens or even hundreds of audio channels simultaneously. With the right networking hardware (switches, routers, network interface cards) and software (drivers, control applications), AoIP systems can deliver studio-grade audio with extremely low latency—often under one millisecond on local networks—and sample-accurate synchronization across all connected devices. This makes AoIP not only a convenience but a technical foundation for modern broadcast studios, live sound systems, recording facilities, and increasingly, remote audio production workflows.

How AoIP Enables Remote Audio Mixing and Production

Real-Time Collaboration Across Distances

Remote audio production relies on the ability to send and receive multiple audio channels with low enough latency that producers, engineers, and artists can interact in real time. AoIP protocols like Dante and AES67 are designed for exactly this kind of synchronous transport. By connecting a studio’s audio console, outboard gear, and computers to a managed network, engineers can route audio to a remote location—say, a producer working from home or a mix engineer in another country—and control the session as if they were in the same room.

This is especially valuable for live broadcasts, podcast recording sessions, and music production where immediate feedback and adjustment are critical. With AoIP, a sound engineer in New York can mix a live concert in Los Angeles, adjusting levels, adding effects, and monitoring the output in real time. The same technology supports distributed recording sessions where musicians in different cities record together over a network, with all tracks aligned to a single clock source.

Bridging Hardware and Software Environments

One of the key advantages of AoIP in remote work is its ability to bridge hardware-based mixing consoles with software-based digital audio workstations (DAWs) and virtual mixing environments. Protocols such as Dante allow a physical console to send its channel outputs directly to a computer running a DAW (like Pro Tools, Logic Pro, or Ableton Live) over a single Ethernet cable. Similarly, audio from software can be sent back to the console's inputs, enabling hybrid workflows where remote collaborators can use either hardware or software tools.

This interoperability is crucial for remote production because it means that the talent on location can use the studio’s high-end microphones, preamps, and monitors, while the remote engineer can apply compression, EQ, and mixing plugins using their own processing power. The result is a production quality that matches or exceeds what could be achieved in a single-room setup, without requiring everyone to be physically present.

Scalable Channel Counts and Flexible Routing

Traditional analog or digital audio snakes are limited by physical cable counts and fixed patching. AoIP removes those constraints entirely. On a modern Dante network, for example, a single Gigabit Ethernet link can carry up to 512 audio channels (in and out). Over a 10GbE network, that number jumps to thousands. This scalability is a game-changer for remote production because it allows engineers to add more microphones, instrument feeds, or return tracks without needing to run new cables or install additional patchbays.

Routing in an AoIP system is managed via software instead of hardware patches. A remote engineer can reassign which channels go to which destination in seconds, change the mix configuration for different segments of a broadcast, or route a talkback mic to any participant. This flexibility dramatically speeds up setup times and reduces the number of manual errors that occur with physical cabling.

Key AoIP Protocols and Standards for Remote Use

Dante (Audinate)

Dante is the most widely adopted AoIP protocol in the professional audio industry. It combines audio transport, routing, and device discovery into a single, user-friendly system that runs on standard Ethernet networks. Dante supports up to 512×512 audio channels on a 1GbE network, with sub-millisecond latency and sample-accurate synchronization. Its widespread support across hundreds of manufacturers (audio interfaces, consoles, amplifiers, speakers) makes it the de facto standard for integrating gear in both fixed installations and temporary remote setups. Audinate provides a free Dante Virtual Soundcard that allows any computer to connect to a Dante network, enabling remote engineers to join sessions with only a network connection.

For remote production, Dante’s ability to traverse Layer 3 networks (with proper routing and VPNs) means that devices on different subnets or even across the internet can exchange audio. Audinate offers Dante Domain Manager for managing secure, multi-site Dante networks. External link: Dante by Audinate.

AES67

AES67 is an interoperability standard developed by the Audio Engineering Society. It defines a common set of parameters—sampling rate, bit depth, packet timing, and network requirements—that allow different AoIP systems (Dante, Livewire, RAVENNA, Q-LAN) to exchange audio without a common manufacturer. AES67 ensures that a Dante system can communicate with a RAVENNA system, for example, which is vital for remote productions where multiple studios may be using different equipment brands. Many modern audio interfaces and consoles now support AES67 as a secondary mode, expanding connectivity options. External link: AES67 Standard.

RAVENNA

RAVENNA is an open standard for real-time distribution of audio and video over IP networks. Developed by ALC NetworX, RAVENNA is widely used in broadcast and media production environments, especially for high-channel-count and uncompressed audio. It supports both PCM audio and AES3 transport, and it is designed to work seamlessly with AES67. RAVENNA's focus on precise timing and redundant network paths makes it a strong choice for mission-critical remote broadcasts. External link: RAVENNA Network.

Livewire (Axia / Telos Alliance)

Livewire is a proprietary AoIP system developed by Axia Audio, part of the Telos Alliance, primarily for radio broadcast applications. It integrates audio routing, console control, and logic commands over standard Ethernet. Livewire devices are common in commercial radio stations and are often used in remote contribution links for live broadcasts from the field. While less common in general music production, its reliability and tight integration with broadcast automation systems make it a key player in the remote radio production space. External link: Axia Audio / Livewire.

Benefits of AoIP for Remote Audio Production

Lower Latency and Higher Audio Quality

Remote production traditionally faced obstacles like perceptual latency (echo/cancellation) and degraded audio quality due to compression. AoIP protocols are engineered to deliver uncompressed or lightly compressed audio with deterministic latency. On a well-managed local network, Dante can achieve sub-0.5 ms latency. Over the internet, with proper quality of service (QoS) and sufficient bandwidth, round-trip latency can be kept under 5–10 ms, which is acceptable for most mixing and monitoring tasks. Because AoIP preserves the audio signal in its native digital form (usually 24-bit, 48 kHz or higher), sonic transparency is maintained throughout the chain.

Cost and Infrastructure Efficiency

Setting up a traditional multi-track remote production required dedicated ISDN lines, codecs, and expensive satellite links. AoIP replaces almost all of that with off-the-shelf networking equipment. A single Cat6 cable can carry a full show’s worth of audio, control signals, and even video. This reduces the amount of gear that needs to be shipped to remote locations, lowers power consumption, and simplifies troubleshooting. For permanent remote studios (like a producer’s home office), only a network switch, a computer with a Dante Virtual Soundcard or hardware interface, and a few microphones are needed.

Enhanced Collaboration Workflows

AoIP makes it easy to set up “talkback” and “listen” feeds that connect remote and local teams. Engineers can talk to performers over a dedicated channel, send cue mixes to musicians, and receive high-quality stereo or multichannel returns. Because routing is software-defined, these workflows can be saved as presets and recalled instantly for recurring sessions. This level of flexibility is difficult to replicate with analog or even MADI-based systems, especially when participants are spread across multiple time zones.

Challenges and Considerations for Remote AoIP

Network Reliability and Bandwidth

While AoIP is robust on local networks, running it over the public internet introduces variables like jitter, packet loss, and variable latency. For reliable remote production, both ends must have stable, high-speed internet connections with low latency and minimal packet loss. Dedicated fiber connections are ideal, but bonded cellular or VPN tunnels can work with careful configuration. Engineers must also ensure that the network is not shared with bandwidth-intensive applications (like large file transfers) during critical sessions. Quality of Service (QoS) settings on managed switches can prioritize audio packets to maintain timing.

Clock Synchronization Across Sites

AoIP relies on a common clock to keep all devices sample-synchronized. On a single local network, a master clock (often a dedicated device or a device with PTP capability) distributes timing to all nodes. For remote setups, each site can operate with its own clock, but cross-site synchronization is more complex. Protocols like AES67 use Precision Time Protocol (PTP) to synchronize clocks over IP networks, but achieving sample accuracy between geographically separated sites requires careful network design and often a GPS-based grandmaster clock. Many remote productions accept asynchronous operation, using sample rate converters on the receiving end to re-clock audio that arrives on different timing domains.

Security and Access Control

Exposing an AoIP network to the internet poses security risks. Unauthorized access could allow someone to listen to or inject audio into a production. To mitigate this, remote AoIP connections should be encrypted or run through secure VPN tunnels. Many AoIP systems also support subnet filtering, MAC address whitelisting, and user authentication. For productions that require end-to-end encryption (e.g., confidential streaming), additional software or hardware may be necessary.

Learning Curve and Setup Complexity

While AoIP simplifies routing after it is set up, the initial configuration requires networking knowledge—IP addressing, VLANs, multicast management, and QoS. Engineers accustomed to analog patchbays may find the software-based routing unfamiliar. There are also multiple protocols and compatibility layers to navigate. However, training resources from major vendors and community forums have made the learning curve more manageable. Many audio interfaces now ship with Dante or AES67 support enabled out of the box, reducing setup time.

Setting Up a Remote AoIP Mixing System

Hardware Requirements

  • Audio Console or Interface: A Dante-compatible mixing console (e.g., Yamaha CL/QL, Allen & Heath dLive, Behringer Wing) or an audio interface with Dante expansion (Focusrite RedNet, RME MADIface with ADI-2 Pro).
  • Network Switch: A managed Gigabit Ethernet switch with QoS and IGMP snooping capabilities. For remote setups, the switch should be dedicated to audio traffic to avoid congestion.
  • Network Interface: A computer running Dante Virtual Soundcard (or hardware like a Focusrite RedNet PCIe card) to join the network and use a DAW for mixing.
  • Remote Connection: A reliable internet link with at least 100 Mbps symmetrical speed for high channel counts. A hardware VPN router or software VPN client to secure the link.

Software Workflow

  1. Configure local AoIP network: Set up devices on the same subnet, assign IP addresses (or use DHCP), and designate a master clock (usually from the console or an RME device).
  2. Establish the remote link: Connect the two sites via VPN or dedicated tunnel. Ensure QoS markings are passed through the tunnel.
  3. Route audio across sites: Use device discovery software (e.g., Dante Controller) to create “transmit” flows from the remote console to the local computer, and “receive” flows for returns.
  4. Mix in your DAW: Open your DAW (Pro Tools, Cubase, etc.) and assign the AoIP channels to tracks. Monitor via headphones or studio monitors connected to the local interface.
  5. Use talkback: Create a dedicated channel for communication between engineer and talent, routed to both sides.

Case Studies: Remote Production with AoIP

Live Broadcast of a Music Festival

A major European broadcaster needed to mix a three-day music festival from a central production hub 200 km away. Each stage had a Dante-compatible console and a computer with Dante Virtual Soundcard. The computer encoded the multichannel audio (up to 64 channels per stage) and transmitted it via a dedicated fiber link with QoS. At the hub, engineers received the streams, mixed in their DAWs, and sent back two stereo returns for monitoring. The setup allowed seamless switching between stages and instant collaboration with on-site technicians.

Remote Recording for a Film Score

A film composer in Los Angeles worked with a 60-piece orchestra in Prague. The Prague studio was equipped with a Yamaha CL5 console, 128 channels of Focusrite RedNet preamps, and a Dante network. The engineer in LA used a RedNet PCIe card in a Mac Pro running Pro Tools. Over the internet, 48 channels of audio were transmitted using AES67 with RAVENNA at 24-bit/96 kHz. Latency was below 12 ms round-trip, allowing the composer to hear the performance in real time and give immediate direction. The session was recorded simultaneously in both locations for backup.

The adoption of cloud-native audio processing is accelerating. Services like AWS Wave and Azure Media Services are beginning to support AoIP streams directly, allowing mixing and processing to happen in the cloud rather than on local hardware. This could eliminate the need for powerful local computers, as remote engineers would connect to a virtual mixing environment. Additionally, the rollout of 5G networks with ultra-reliable low-latency communication (URLLC) will make it feasible to transmit AoIP wirelessly from remote locations without fiber backhaul. Standards like SMPTE ST 2110 (for broadcast video and audio over IP) are also converging with audio-only AoIP, enabling unified media production workflows that handle audio, video, and metadata on a single network.

As AoIP matures, we can expect even tighter integration with cloud storage, AI-assisted mixing tools, and automated session management. The line between local and remote production will continue to blur, with AoIP serving as the invisible backbone that connects talent and engineers anywhere in the world.

Conclusion

Audio over Internet Protocol has moved from a niche technology to a cornerstone of modern audio production, especially in remote contexts. By enabling real-time, high-quality, and flexible audio transport over standard networks, AoIP empowers producers, engineers, and artists to collaborate without geographic boundaries. While challenges around network reliability, synchronization, and security remain, the benefits in scalability, cost savings, and workflow efficiency are undeniable. Whether for a live broadcast, a podcast recording, or a complex orchestral session, AoIP provides the technical foundation necessary to produce professional-grade audio from anywhere in the world.

With ongoing developments in interoperability standards, cloud integration, and wireless connectivity, the role of AoIP in facilitating remote audio mixing and production will only expand. For anyone serious about remote audio work, investing in AoIP knowledge and equipment is no longer optional—it is essential to staying competitive in a distributed production landscape.