The Evolving Landscape of Remote Production and Streaming

Modern broadcast, live event production, and streaming increasingly depend on the ability to move high-quality audio across vast distances with minimal latency and maximum reliability. Traditional point‑to‑point analog or digital copper connections quickly become unmanageable when multiple contributors, venues, and destinations are involved. Audio networking—the practice of transporting digital audio over standard Internet Protocol (IP) networks—has emerged as the essential infrastructure for this new reality. By decoupling audio signals from dedicated cabling, audio networking gives producers, engineers, and content creators the flexibility to route, monitor, and manage audio from anywhere, enabling truly remote production workflows that were impractical just a few years ago.

This article provides a comprehensive look at audio networking for remote production and streaming, covering the core technologies, real‑world applications, deployment best practices, and emerging trends. Whether you are a broadcast engineer planning a distributed sports feed, a music producer coordinating a live stream with remote talent, or a system integrator designing scalable studio infrastructure, understanding these principles is critical for delivering consistent, professional audio experiences.

What Is Audio Networking?

At its simplest, audio networking replaces dedicated audio cables (balanced analog XLR, AES/EBU, MADI, etc.) with Ethernet or IP networks. The audio signal is sampled, packetized, and transmitted alongside other network traffic—or on a dedicated audio‑over‑IP (AoIP) network—using one or more standardized protocols. This approach allows any audio source to be connected to any destination, provided both are on the same network and support a common protocol. The key performance metrics for professional audio networking are ultra‑low latency (typically under 1 millisecond per hop), sample‑accurate synchronization, and robust error recovery that is imperceptible to listeners.

Early attempts at IP‑based audio transport date back to the late 1990s with protocols like Livewire, but the modern era truly began in the mid‑2000s with the introduction of Dante by Audinate, AVB (Audio Video Bridging) as an IEEE standard, and Ravenna (developed by ALC NetworX). Each uses slightly different approaches to timing, discovery, and clocking, but they all share the same fundamental goal: enable audio to flow over standard network hardware—switches, routers, and fiber—with the same or better quality than dedicated cabling.

The Core Benefits of IP‑Based Audio

  • Elimination of dedicated cabling: A single Ethernet cable or fiber link can carry dozens, hundreds, or even thousands of audio channels simultaneously. This reduces copper weight, installation cost, and infrastructure complexity.
  • Remote access and distributed workflows: Talent, commentators, and engineers can connect from anywhere with a stable Internet connection. A remote producer can receive microphone feeds, send IFB mixes, and control console parameters without being in the same building.
  • Scalability on demand: Adding a new audio node or stream is often as simple as connecting a device to the network and configuring its IP address. Physical rewiring is rarely required.
  • Centralized resource sharing: Shared audio resources—such as codecs, mixers, and processing engines—can be accessed by multiple production locations, reducing equipment duplication.
  • Future‑proofing: As network speeds increase (1 GbE, 10 GbE, 25 GbE, and beyond), audio networking can easily scale to accommodate higher channel counts and higher sample rates without replacing the entire infrastructure.

Key Technologies and Protocols

While several AoIP protocols exist, three dominate the professional audio market: Dante, AVB (IEEE 802.1BA/1722), and Ravenna/AES67. Understanding their differences and interoperability is crucial for building reliable systems.

Dante

Dante, developed by Audinate, is the most widely deployed AoIP protocol. It operates on standard Gigabit Ethernet networks and supports up to 512 audio channels per stream (depending on sample rate and bit depth). Dante manages clocking using a Precision Time Protocol (PTP) variant that achieves sample‑accurate synchronization across devices. Its automatic device discovery (via mDNS), redundant network support (primary/secondary Ethernet ports), and software‑based routing (Dante Controller) make it user‑friendly for both installed and temporary production setups. Dante is licensed to hundreds of manufacturers, including Yamaha, Allen & Heath, Shure, and Focusrite.

For remote production, Dante supports wide‑area networking through Dante Domain Manager (DDM), which enables secure, auditable routing across different subnets and even over the public Internet. Managed switches with Quality of Service (QoS) settings are recommended to prioritize audio traffic and prevent packet loss. Audinate’s official site provides detailed whitepapers and deployment guides.

AVB (Audio Video Bridging) / TSN

AVB is an IEEE standard (now part of Time‑Sensitive Networking – TSN) that guarantees low latency and synchronized streaming over Ethernet. Unlike Dante, which is proprietary, AVB/TSN is an open standard that defines a set of sub‑protocols for clock synchronization (IEEE 802.1AS), stream reservation (IEEE 802.1Qat), and packet format (IEEE 1722). AVB requires special network switches that support credit‑based shaping and stream reservation to ensure deterministic delivery. This makes AVB particularly attractive for automotive and industrial applications, but it has also gained traction in live sound and installed sound environments—Meyer Sound, L‑Acoustics, and Biamp are notable adopters.

AVB’s main strength is guaranteed latency (2 ms for a 7‑hop network) and bandwidth reservation, which eliminates competition with other traffic. The downside is a stricter hardware requirement; not all switches support AVB/TSN, and interoperability between vendors can still be challenging. For remote production, AVB’s capabilities are most useful within a dedicated local network segment; carrying AVB over the wide area remains uncommon.

Ravenna / AES67

Ravenna is an open‑source protocol suite developed by ALC NetworX that operates over standard IP networks. It uses the Real‑time Transport Protocol (RTP) and PTP for synchronization (IEEE 1588‑2008). Ravenna is designed for high‑performance, multi‑channel audio transport and supports sample rates up to 192 kHz with up to 128 channels per stream. Its modular architecture makes it a popular choice for broadcast facilities and recording studios where interoperability with AES67 is required.

AES67 is a standard published by the Audio Engineering Society that defines how high‑performance audio streams can be exchanged between different AoIP implementations. It is not a protocol itself but a “bridge” that enables Dante, Ravenna, Livewire, and Q‑Sys systems to share audio at a basic level (PCM, unicast/multicast, PTP‑based sync). For remote production, AES67 is invaluable because it allows a show that uses Dante microphones on stage to send feeds to a Ravenna‑based broadcast console over the same network. AES67 resources and compliance lists are maintained by the AES.

Other Relevant Protocols

  • Livewire+ – Used by Telos and Axia for broadcast audio routing, often coexisting with AES67.
  • Milan – An open standard based on AVB/TSN, promoted by the Milan Alliance for guaranteed interoperability.
  • NDI (Network Device Interface) – While primarily for video, NDI also supports audio and is used in streaming workflows for low‑latency IP transport.

Applications in Remote Production and Streaming

Audio networking underpins virtually all modern remote production scenarios. The ability to bring microphone feeds, mix minus signals, IFB (interrupt foldback) mixes, and program returns across distance enables geographically distributed teams to collaborate as if they were in the same room.

Live Sports Broadcasting

Sports remote production (REMI – Remote Integration Model) relies heavily on audio networking. Commentators, sideline reporters, and on‑air talent are often miles apart. A typical setup uses Dante or Ravenna to transport commentary microphones from the stadium to a central production hub, while return audio (program feed, director’s cues) flows back to the venue. Low latency is critical: more than 30 ms of delay between the commentator’s voice and the program audio creates an unusable listening experience. By using dedicated AoIP codecs (such as the Sonifex Net‑2 or Glensound GTC‑2) and managed networks, broadcasters achieve latencies under 10 ms end‑to‑end.

Additionally, audio networking enables seamless integration of crowd microphones, referee microphones, and ambient sound effects into the remote mix. The same network can carry intercom (often via separate VLANs) for crew communication, further simplifying cabling and infrastructure.

Concert and Festival Streaming

Music festivals now stream performances globally in real‑time. Audio networking allows front‑of‑house consoles, monitor consoles, and broadcast mix trucks to share audio without creating a tangled mess of analog splits. A common configuration uses a Dante‑capable stagebox (e.g., Yamaha Rio or Allen & Heath DT168) to capture all inputs, then routes those channels over a private network to multiple mix positions. The broadcast truck can pull clean feeds directly from the stage network, avoiding ground loops and signal degradation. For the streaming mix, the FOH engineer can send a dedicated stereo or 5.1 mix over the same AoIP infrastructure to an encoder for platforms like Twitch, YouTube, or HLS.

News and Talk Radio

Remote studios and field reporters often use portable codecs that connect over the public Internet. Modern codecs support Dante and AES67, allowing them to plug directly into a studio’s AoIP network. Reporters at a press conference can send a four‑channel feed (anchors mic, guest mic, ambient, line from podium) over a bonded cellular or VPN connection. At the studio, the engineer patches those channels into the mixing console and recording system via Dante patching, all without patching a single XLR cable. This agility is vital for breaking news where speed of setup is paramount.

Streaming and Content Creation

For solo streamers and small content creators, audio networking may seem overkill, but it solves the problem of multiple USB audio devices and driver conflicts. A Dante‑compatible interface (like the Focusrite RedNet or smaller devices like the Neutrik NYS‑DLC) allows a streamer to capture a microphone, game audio, and chat audio as separate network streams, which can be routed to digital audio workstations (DAWs) and streaming software (OBS, vMix) with sample‑accurate timing. Remote guests can also participate via low‑latency audio networking using solutions like Discord's Krisp integration or dedicated Dante‑over‑WAN setups, providing broadcast‑quality voice without compression artifacts.

Case Study: Remote Sports Broadcast with Distributed Talent

To illustrate a real‑world deployment, consider a regional soccer championship broadcast. The host broadcaster operates a main production studio in City A, while the venue is in City B, 400 km away. Commentators are at the venue, but analysis and hosting are done from the studio. The set requires three commentator microphones, two sideline reporter microphones, a handheld mic for audience interviews, and four ambient microphones positioned around the stadium.

Audio networking design:

  • At the venue: All microphones connect to a Dante‑enabled stagebox (e.g., Yamaha Rio3224‑D). The stagebox converts analog to digital and publishes all channels on a private VLAN.
  • Two Dante‑to‑WAN codecs (e.g., Digigram ethersound over VPN) encapsulate the eight needed channels (one mix minus feed is sent back) and transmit them over a dedicated MPLS link.
  • At the studio: The WAN codec receives the streams and decapsulates back into Dante, where they appear on the studio’s Dante network. The broadcast console (e.g., Calrec or Lawo) pulls the feeds directly as if they were local.
  • Return audio: A program mix (minus the commentator’s own voice) is sent back to the venue for IFB. Latency is measured at 8 ms round‑trip, well within broadcast tolerances.
  • Redundancy: Both the venue and studio have redundant Dante networks (primary and secondary IP paths). The WAN link uses dual bonded connections; if one fails, the other takes over seamlessly.

This setup eliminated the need for a separate outside broadcast truck at the venue, reduced travel costs, and allowed the same production team to cover multiple games simultaneously from the central hub.

Challenges and Considerations

Despite its many benefits, audio networking introduces complexities that engineers must plan for. The most common pitfalls involve network configuration, security, and latency management.

Network Infrastructure and QoS

AoIP streams are sensitive to jitter, packet loss, and latency variation. Using consumer‑grade switches can result in dropped packets, audible clicks, and loss of sync. For reliable operation, use fully managed Gigabit switches with IGMP snooping (for multicast traffic), DiffServ/DSCP tagging for QoS (priority queues for audio traffic), and per‑port bandwidth limits. Switches must also support sufficient MAC address table capacity and buffer sizes to handle multiple audio streams simultaneously. Many manufacturers provide pre‑configured profiles for Dante or AVB networks; applying these is highly recommended.

Security

When audio networking extends over public or semi‑public networks (WAN, cloud, IP over cellular), encryption and authentication become critical. Unprotected audio streams can be intercepted, spoofed, or disrupted. Solutions include:

  • Using VPN tunnels (IPsec, OpenVPN) between remote locations.
  • Implementing 802.1X network access control to prevent unauthorized devices from connecting to the AoIP VLAN.
  • Separating audio traffic into a dedicated VLAN with ACLs restricting access to known IP addresses.
  • For Dante Domain Manager, enabling TLS and authentication for management traffic.

Latency and Synchronization

Every packetization, switch hop, and routing element adds latency. The brain can detect delays above 20 ms in audio‑video sync (a bigger concern for streaming) and above 30 ms in foldback paths. In remote production, the total round‑trip latency must be kept low enough that the talent does not hear their own voice delayed. Best practices include:

  • Using codecs that support low‑latency modes (e.g., Opus vs. AAC).
  • Minimizing the number of network hops; direct fiber or MPLS links are preferable to the public Internet.
  • Enabling PTP boundary clocks or transparent clocks to correct for switch delays.
  • Testing with latency measurement tools (e.g., Audinate’s Dante Latency Analyzer).

Interoperability and Standards

Even though AES67 provides a common baseline, not all devices support it, and those that do may have limitations (e.g., only 48 kHz sample rate, or only unicast mode). When mixing different vendors, verify compatibility in advance. The AES67 Application Profile lists compliant products. For systems using Dante and Ravenna, ensure both are using the same PTP profile (IEEE 1588‑2008, domain 0 for Dante, domain 1 for Ravenna; domain conflicts cause sync issues).

Network Design for Remote Production

When deploying audio networking across a wide area, consider using a Software‑Defined Wide Area Network (SD‑WAN) with QoS policies specifically for audio. Many broadcasters now use multicast VPN (mVPN) to efficiently distribute live audio to multiple remote destinations. Inside the facility, a best practice is to use a dedicated audio network (or VLAN) with its own subnet to keep traffic predictable. The “three‑network” approach—production LAN, control VLAN, and AoIP VLAN—is widely recommended.

As the industry moves towards all‑IP infrastructures, several developments are shaping the next decade of audio networking.

Cloud‑Native Audio Workflows

Cloud platforms like AWS, Google Cloud, and Azure now support real‑time audio transport via virtual AoIP instances. Tools such as Ravenna Cloud and Dante Cloud Connect allow producers to run mixers, recorders, and routing matrices entirely in the cloud, ingesting and outputting audio via AES67 or NDI from edge compute nodes. This enables “production from anywhere” with centralized resources, though careful attention to latency and clock synchronization is still required.

AI‑Driven Audio Management

Machine learning is being applied to automatically balance gain, reduce noise, and even detect network anomalies before they affect an audio stream. For remote production, AI can monitor dozens of audio channels simultaneously, flagging feedback, clipping, or dropouts. Companies like iZotope and Waves are integrating AI‑based plugins that work seamlessly with AoIP streams.

SMPTE ST 2110 Adoption

The SMPTE ST 2110 suite of standards is widely adopted in broadcast television for transporting uncompressed video, audio, and ancillary data over IP. For audio, ST 2110‑30 is essentially AES67. As broadcasters transition from SDI to IP, ST 2110‑compliant switches and routers become the norm. This convergence means that a single network can carry both video and audio with deterministic timing, eliminating separate AVB/Dante networks in large facilities. Expect to see more hybrid systems combining ST 2110 for core broadcast with Dante or Ravenna for edge devices.

Lower‑Cost, Higher‑Performance Hardware

The cost of entry for AoIP continues to fall. Devices like the Sonifex RB‑Dante and Audinate D64 have dropped in price, and many consumer/prosumer interfaces now include Dante or AES67 functionality. This democratization allows small studios, podcasters, and streaming start‑ups to tap into professional‑grade routing and remote capabilities without a huge investment.

Conclusion

Audio networking has transformed remote production and streaming from a niche, high‑cost operation into a mainstream, flexible, and scalable workflow. By adopting protocols like Dante, AVB, and AES67, engineers and content creators can manage high‑quality audio with low latency across local and wide‑area networks, breaking down geographic barriers and enabling collaborative production at a distance. While challenges around network design, security, and interoperability remain, they are well understood and can be addressed with proper planning and the right infrastructure. As cloud integration, AI, and broader standards like ST 2110 continue to mature, audio networking will become even more powerful—and more essential—for delivering the immersive audio experiences that audiences expect.

For teams setting up new remote production systems, investing time in learning the nuances of AoIP protocols, switch configuration, and synchronization is time well spent. The resources available from Audinate, the AES standards page, and vendors like ALC NetworX offer comprehensive guidance. With the right approach, audio networking becomes not just a technical enabler, but a creative advantage for any production involving sound over distance.