Introduction to Audio over IP in Post-Production

Audio over IP (AoIP) has become a foundational technology in modern post-production studios, replacing traditional point-to-point analog and digital connections with networked audio distribution. By transmitting multiple audio channels over standard Ethernet networks, AoIP reduces cable clutter, simplifies patching, and enables flexible routing that can be reconfigured in software. For post-production facilities handling complex projects with tight deadlines, the scalability and cost efficiency of AoIP are compelling advantages.

However, transitioning to an AoIP environment requires careful planning. Unlike consumer-grade audio networking, professional post-production demands deterministic, low-latency transport, robust synchronization, and reliable integration with existing digital audio workstations (DAWs) and video systems. This article provides actionable tips and best practices for implementing AoIP successfully in a post-production setting.

Understanding Audio over IP Protocols

Not all AoIP implementations are created equal. Several protocols have emerged, each with specific strengths. The most common in professional audio include:

  • Dante – Developed by Audinate, Dante is widely adopted in live sound and recording studios. It offers plug-and-play discovery, low latency (as low as 250 µs), and support for up to 512 channels per link. Dante Controller provides intuitive routing management, and Dante Virtual Soundcard allows a computer to send and receive audio over a standard network interface.
  • AES67 – An open standard from the Audio Engineering Society that enables interoperability between different AoIP systems (e.g., Dante, Ravenna, Q-LAN). AES67 defines layer 3 transport and can coexist with other protocols on the same network. For post-production studios that need to mix equipment from multiple vendors, AES67 compliance is essential.
  • Ravenna – Used extensively in broadcast and high-end recording, Ravenna offers flexible sample rates (up to 192 kHz) and supports both unicast and multicast streams. It is often paired with the Ravenna ASIO driver for low-latency performance on Windows systems.
  • AVB (Audio Video Bridging) – An IEEE 802.1 standard that guarantees bounded latency and reserved bandwidth. While less common in post-production than Dante or Ravenna, AVB is found in some pro-sumer interfaces and is gaining traction in automotive and live event markets.

When selecting a protocol, consider your studio‘s existing equipment, required channel counts, and interoperability needs. Many modern converters and interfaces support multiple protocols (e.g., AES67 and Dante simultaneously), providing flexibility for future expansion.

Key Tips for Implementation

1. Assess Your Network Infrastructure

A reliable network is the backbone of any AoIP deployment. Standard office networks are rarely suitable without upgrades. Key factors to evaluate:

  • Bandwidth – Each 48 kHz, 24-bit audio channel consumes about 1.5 Mbps (including overhead). A 128-channel mix can easily exceed 200 Mbps. Ensure your switches and cabling (Cat6a or better) support the required throughput without congestion.
  • Latency – Post-production workflows often require round-trip latencies under 10 ms to avoid audible phasing or monitoring delay. Choose switches with low store-and-forward latency (below 10 µs per hop) and enable cut-through forwarding if supported.
  • Quality of Service (QoS) – Prioritize audio traffic on your network. Use DiffServ to mark audio packets (e.g., DSCP 46 for EF). Configure strict priority queuing so that audio packets are never dropped during high network loads. Without proper QoS, file transfers or backups can cause audio dropouts.
  • Jitter – Jitter causes sample clock instability. Use switches with precise timing (IEEE 1588 Precision Time Protocol support) and maintain a stable clock master through PTP (IEEE 1588v2). In practice, network switches should have jitter below 1 µs for professional-grade audio.

2. Choose Compatible Hardware and Software

Not every audio interface or switch will work seamlessly with your chosen AoIP protocol. Look for products that are explicitly certified for your protocol (e.g., Dante-certified devices, AES67-compatible units). Important considerations:

  • Audio interfaces – Ensure they support the desired sample rate and bit depth (e.g., 96 kHz, 24-bit for high-resolution post-production). Check for redundant power supplies and dual network ports if uptime is critical.
  • Network switches – Use managed switches that support IGMP snooping (for multicast optimization), VLANs, and PTP. Avoid consumer-grade switches; instead, choose enterprise models from Cisco, Netgear, or Ubiquiti that allow configuration of QoS and storm control.
  • Software – Your DAW or audio routing software must be able to communicate with the AoIP network. Dante Virtual Soundcard (DVS) or Ravenna ASIO drivers allow a standard computer to become an AoIP endpoint. For advanced routing, tools like Dante Domain Manager provide user authentication and device management across multiple subnets.

3. Implement Proper Network Segmentation

To prevent interference from general network traffic, segment your AoIP network from data, video, and control networks. Two common approaches:

  • Physical VLANs – Assign a dedicated VLAN for audio traffic on your managed switches. Tag audio streams with a specific VLAN ID and restrict other VLANs from accessing the audio subnet. This isolates broadcast storms and reduces unnecessary packet processing.
  • Dedicated network – Use a separate physical switch for audio only, particularly if your existing network carries heavy file transfers or video streams. This avoids any chance of QoS misconfiguration affecting real-time audio.

Additionally, enable IGMP snooping on your switches. Multicast audio streams are only forwarded to ports that have explicitly requested them, preventing bandwidth waste and potential overload on unrelated segments.

Best Practices for Day-to-Day Operation

1. Regular Network Monitoring

Even a well-designed AoIP network can develop issues over time. Implement monitoring tools to detect problems early:

  • Dante Controller provides latency measurements, clock status, and device health. It can export logs for review.
  • Wireshark with the Dissector for AES67 can analyze packet loss, jitter, and PTP timing. Set up alerts for abnormal packet counts.
  • Network analyzers like SolarWinds or PRTG can monitor switch port statistics, CPU usage, and error counters.

2. Use Redundant Connections

In mission-critical post-production, a single network failure can halt a session. Deploy redundancy through:

  • Dual network ports – Many AoIP devices support two Ethernet ports for failover. Configure them in primary/backup mode using spanning tree protocol (RSTP) or proprietary protocols like Dante Redundancy (uses separate primary and secondary networks).
  • Redundant switches – Connect each AoIP device to two switches (link aggregation or separate uplinks). If one switch fails, traffic routes through the other, provided your network topology supports it.
  • Clock redundancy – Configure a backup PTP master. If the primary clock fails, the secondary takes over without disrupting audio synchronization.

3. Maintain Firmware and Software Updates

Manufacturers regularly release updates to fix bugs, improve stability, and add features (e.g., support for new sample rates or AES67 profiles). Keep your switches, audio interfaces, and software (Dante Controller, Ravenna drivers, DAW plugins) patched. Before updating, test on a non-production device to ensure compatibility.

Advanced Considerations for Post-Production Workflows

Synchronization: PTP and Word Clock

Audio over IP relies on Precision Time Protocol (PTP) to synchronize sample clocks across devices. In a post-production facility, you may also have legacy gear requiring word clock. Use a master clock that can output both PTP and word clock simultaneously (e.g., an Audio Science Lab or Mutec device). Configure PTP on your switches with the boundary clock feature to improve accuracy across large networks. For most workflows, a grandmaster clock with ±10 ppm accuracy is sufficient, but for projects with video frames (24, 25, 29.97 fps), ensure the clock source can pull to video reference (black burst or tri-level sync).

Integration with DAWs and Video Systems

To bring AoIP into your DAW, you need a virtual soundcard driver (e.g., Dante Virtual Soundcard) that presents the network audio as standard ASIO or Core Audio devices. Set buffer sizes appropriately: typically 64 or 128 samples for real-time monitoring, 256 samples for mixing with plugins. For video editing suites (Pro Tools, DaVinci Resolve, Adobe Premiere), use physical AoIP interfaces that connect to the computer via Thunderbolt or USB and provide network ports. Many modern interfaces (e.g., Focusrite RedNet, RME Digiface) offer both.

For video-plus-audio workflows (e.g., ADR, Foley), consider SMPTE ST 2110, which integrates video and audio over IP with precise timing. This is more common in broadcast but is appearing in high-end post-production houses. If your facility supports many real-time video streams, you may need a separate network for video to avoid congestion.

Common Pitfalls and How to Avoid Them

  • Insufficient QoS – Unprotected audio traffic can be preempted by large file transfers. Always set QoS markings at the source and verify them at the switch.
  • Overloaded switches – Even a managed switch can drop packets if multiple high-bandwidth streams converge on a single port. Use link aggregation (LACP) for uplinks carrying many channels.
  • Clock domain mismatch – Mixing PTP clocks from different masters can cause drift and audible clicks. Designate one grandmaster and ensure all devices get PTP from it.
  • Forgetting about cable quality – Use high-quality shielded Cat6a or Cat7 cables to minimize electromagnetic interference, especially in studios with strong power lines or wireless transmitters.

External Resources for Deeper Learning

Future Trends in AoIP for Post-Production

The industry is moving toward higher channel counts and deeper integration with video. SMPTE ST 2110 is increasingly deployed in broadcast and large post facilities, offering a unified IP infrastructure for audio, video, and data. Meanwhile, the Audio Networking Alliance (ANA) continues to promote AVB as a low-latency alternative, though its adoption remains niche. On the software side, cloud-based AoIP routing (e.g., Waves Tracks Live, Source-Connect) is expanding remote collaboration capabilities. Post-production engineers should stay informed about these developments to future-proof their investments.

Implementing Audio over IP in a post-production studio is a multi-step process that rewards careful planning. By focusing on network infrastructure, protocol compatibility, and robust best practices, you can achieve a system that offers greater flexibility, lower latency, and easier maintenance than traditional wiring. Start with a pilot installation, document your configuration, and then scale gradually. With the right approach, AoIP can transform your workflow and improve the quality of your final mix.