The Convergence of Audio and Video Over IP

In modern broadcast facilities, the boundary between audio and video production is dissolving. The integration of Audio over Internet Protocol (AoIP) with video production workflows is no longer a luxury—it is rapidly becoming a baseline requirement for any operation that demands real-time, synchronized, and scalable content creation. By unifying audio and video on a shared IP infrastructure, broadcasters can eliminate the silos of legacy SDI and analog audio systems, reduce hardware complexity, and unlock new levels of flexibility for live, remote, and cloud-based productions.

This article explores the technical standards, practical implementation steps, and strategic benefits of combining AoIP with video workflows. We’ll examine the key protocols that make integration possible, discuss network design considerations, and look at emerging trends that are shaping the next generation of broadcast. Whether you operate a local news station, a large sports network, or a streaming platform, understanding how to bridge audio and video over IP is essential for staying competitive in an increasingly software-defined media landscape.

The Evolution of Broadcast Infrastructure

For decades, broadcast facilities operated two separate signal paths: one for video (typically SDI) and one for audio (analog or AES/EBU). Each path required its own cabling, routing matrices, and synchronization systems. This approach worked, but it came with significant overhead. Adding a new source meant pulling new cables, configuring crosspoint routers, and aligning timing across multiple domains. The result was a patchwork of point-to-point connections that resisted scaling and made remote production almost impossible.

The industry’s move toward all-IP infrastructure began in the audio world with the introduction of protocols like CobraNet, EtherSound, and later Dante and AES67. These allowed audio to be transported, routed, and processed over standard Ethernet networks. Video followed with the development of SMPTE ST 2110, a suite of standards that separates video, audio, and ancillary data into distinct streams over IP. The goal was simple: create a unified network where any signal—audio, video, or metadata—exists as a stream that can be routed with the same agility as data packets. Today, major broadcasters and OB truck vendors have adopted this approach, and the transition is accelerating as SDI-based hardware becomes harder to source.

Key Protocols and Standards for Integration

Successful integration of AoIP with video production hinges on selecting interoperable protocols that support synchronization, low latency, and deterministic performance. The following are the dominant standards in use today.

AES67 – The Audio Interoperability Layer

AES67 is an Audio Engineering Society standard that defines how to transport high-quality audio over IP networks using RTP (Real-time Transport Protocol). It acts as a common layer that allows AoIP systems from different manufacturers (Dante, Ravenna, Livewire, Q-LAN) to communicate. Any AoIP device that supports AES67 can talk to an AES67-compliant video-over-IP system, provided timing and QoS requirements are met. This interoperability is critical because it lets broadcasters mix and match equipment without being locked into a single vendor ecosystem. Many modern AoIP devices ship with AES67 compliance enabled by default, making integration straightforward.

Dante

Developed by Audinate, Dante is one of the most widely adopted AoIP solutions for live sound and broadcast. Dante devices can be easily discovered and routed via software. Modern Dante interfaces support AES67 compliance, making them suitable for integration with video workflows that use SMPTE ST 2110-30 (the audio transport part of ST 2110). Dante also provides built-in redundancy via dual-redundant network ports and automatic failover, which is a boon for mission-critical broadcast operations. The Dante controller software offers a clear routing matrix, and third-party plugins allow integration with video switchers and production control systems.

Ravenna

Ravenna, developed by ALC NetworX (now part of Lawo), is another robust AoIP protocol that uses RTP and is fully AES67-compatible. It is especially popular in broadcast environments where high channel counts and ultra-low latency are required. Ravenna systems often serve as the audio backbone in ST 2110 installations. Ravenna supports sample rates up to 192 kHz and can carry up to 256 audio channels per stream, making it ideal for large-scale productions with many microphones and intercom feeds. Lawo’s VSM (Virtual Studio Manager) provides a unified control layer for both Ravenna audio and ST 2110 video streams, enabling operators to route all signals from a single interface.

SMPTE ST 2110 – The Video Over IP Standard

SMPTE ST 2110 is the most significant specification for video-over-IP in professional broadcast. It comprises several parts: ST 2110-20 (uncompressed video), ST 2110-30 (PCM audio), ST 2110-40 (ancillary data like captions and timecode), and others. Crucially, ST 2110-30 adopts AES67 as its audio transport, meaning any AES67-compliant AoIP source can be directly ingested into an ST 2110 environment. This is the technical foundation for unified broadcast solutions. Additionally, ST 2110-22 (JPEG XS compressed video) is gaining traction for applications where bandwidth is limited, such as remote contribution links. Together, these standards create a complete ecosystem where audio and video can coexist on the same network fabric.

Benefits of a Unified AoIP and Video Workflow

Combining audio and video on a single IP network delivers tangible advantages that improve efficiency, reduce cost, and enable new production models. Below we explore the most impactful benefits in detail.

Enforced Synchronization

IP networks use Precision Time Protocol (PTP) as defined by IEEE 1588 to synchronize all devices to a common grandmaster clock. In a unified environment, both audio and video devices share the same PTP domain, ensuring that all streams remain perfectly aligned throughout the facility—even across multiple switches and geographic distances. Lip-sync errors become a thing of the past. This level of deterministic timing is especially critical for live events where a single audio dropout or video glitch can ruin a broadcast. With PTP, the drift between audio and video is typically measured in nanoseconds, far beyond what human perception can detect.

Reduced Hardware Complexity

Legacy facilities require separate patch bays, routers, and cable runs for audio and video. With IP, a single Ethernet cable can carry multiple channels of audio, video, and control data. This dramatically reduces the cost of cabling, connectors, and infrastructure. It also simplifies reconfiguration: routing changes can be made in software rather than by physically repatching. For example, a broadcaster that needs to add a new camera and mic can simply plug into the nearest network switch and configure the routes through a management interface—no need to pull new SDI or XLR cables across the building. Over time, this reduces the physical footprint of the facility and lowers operational costs.

Flexible Remote and Distributed Production

IP networks are inherently location-agnostic. An audio console in one city can receive microphone feeds from a remote venue via AoIP, while video feeds from the same venue arrive via ST 2110 or JPEG XS. The signals can be aligned and processed as if they were in the same room. This capability is essential for distributed production models, where talent, engineers, and directors work from different sites. Major broadcasters now operate remote production hubs that handle multiple live events simultaneously, with all audio and video flowing over dedicated IP links. The result is a significant reduction in travel costs and carbon footprint, without sacrificing production quality.

Scalability on Demand

Adding new sources or destinations in an IP-based facility is a matter of licensing and network provisioning. There is no need to install new router cards or run additional cables. This scalability is critical for growing operations such as streaming channels, esports production, or multi-language programming. For instance, if a broadcaster acquires rights to a new sports league, they can spin up additional audio and video channels by simply configuring new multicast streams on the existing network, rather than waiting weeks for new hardware to arrive. This agility gives media companies a competitive edge in a fast-evolving market.

Technical Considerations for Successful Integration

Merging AoIP and video over IP is not without challenges. The network must be carefully engineered to meet the strict latency, jitter, and bandwidth requirements of both domains. Below are the key areas that demand attention.

Precision Time Protocol (PTP) Domain

A single PTP grandmaster clock should serve both the audio and video domains to avoid timing drift. All AoIP devices (Dante, Ravenna, AES67) and ST 2110 equipment must be configured as PTP slaves. Even a few microseconds of clock offset can cause audible pops or video tearing. It is essential to use boundary clocks or transparent clocks in switches to maintain accuracy across the network. When extending PTP across WAN links for remote production, use dedicated grandmaster appliances with built-in GPS or IEEE 1588-2008 profiles to overcome the jitter introduced by long-haul connections. Many manufacturers provide best practices for PTP deployment, and compliance with SMPTE ST 2059-1/2 is recommended for ST 2110 systems.

Quality of Service (QoS)

Audio and video streams are sensitive to packet loss and delay variation. DSCP (Differentiated Services Code Point) markings must be applied to prioritize real-time media traffic over best-effort data. The industry typically assigns high priority (e.g., EF or CS5) to ST 2110 video and AES67 audio, while control data and file transfers receive lower priority. Network switches must be configured to enforce these markings, and buffers should be sized to handle micro-bursts without dropping packets. In addition, use separate VLANs for media and control traffic to isolate streaming traffic from management overhead. Testing with a network analyzer before going live will reveal any misconfigured QoS policies.

Bandwidth Planning

Uncompressed HD video (ST 2110-20 1080p59.94) consumes roughly 1.5–3 Gbps per stream, depending on color depth and sampling. The associated AES67 audio streams (48 kHz, 24-bit, 8 channels) add only about 12 Mbps, but when dozens or hundreds of streams are aggregated, the total bandwidth quickly exceeds the capacity of a 1 GbE link. 10 GbE or 25 GbE is the standard for aggregated video networks. Audio-only segments can often be served over 1 GbE but should still be connected via a backbone that supports the full media load. For UHD/4K video, 25 GbE or 50 GbE per link may be necessary. Always account for multicast replication: when many receivers subscribe to the same stream, the switch must be able to replicate it efficiently. Use IGMP snooping and queriers to manage multicast group membership.

Redundancy and Resilience

Broadcast cannot tolerate downtime. IP-based systems require redundant switches, power supplies, and links. Protocols like SMPTE ST 2022-7 (seamless protection switching) allow streams to be sent simultaneously over two paths. Audio systems should use redundant network stacks (e.g., Dante secondary port). Plan for dual PTP grandmasters (active/standby), automatic failover, and diverse routing to ensure uptime. In a facility with multiple switches, consider a spine-leaf architecture to minimize hop count and increase resilience. Regular failover testing during maintenance windows will validate that redundancy mechanisms work as expected.

Implementation Roadmap for Unified Broadcast Solutions

Transitioning from a legacy or hybrid infrastructure to a fully integrated AoIP/video IP ecosystem requires a methodical approach. The following steps outline a recommended path based on industry best practices.

1. Audit Existing Infrastructure

Document all current audio and video sources, processing equipment, routing, and signal flow. Identify which devices already support IP or can be upgraded with IP interfaces (e.g., breakout boxes or gateway cards). Determine the physical locations of studios, control rooms, and machine rooms to plan network topology. This audit also helps identify which legacy systems must be retained for a transitional period and which can be retired immediately.

2. Choose a Common Standard

Select either AES67 or SMPTE ST 2110-30 as the audio transport. If the facility will also handle video over IP, commit to ST 2110 as the overall framework. Ensure that any new AoIP gear (mixing consoles, microphone preamps, intercoms) explicitly supports ST 2110-30 or at minimum AES67. For new purchases, interoperability certification (such as the Dante Certified program or Ravenna compliance) is a strong indicator of reliable integration.

3. Design the Network

Engage a qualified network engineer with broadcast IP experience. Design a dedicated media network (often separate from corporate IT) using multicast-capable switches. Configure PTP profiles (preferably SMPTE ST 2059-1/2 for ST 2110), set up VLANs to segregate media from control traffic, and enable IGMP snooping for multicast stream management. Use a network management tool (e.g., Lawo VSM, Audinate Dante Controller, Harman HiQnet) to discover and route streams. Consider using a software-defined networking (SDN) controller for dynamic routing and bandwidth allocation.

4. Validate Interoperability

Before full deployment, set up a test lab with representative equipment from different vendors. Test stream registration, PTP synchronization, and ability to route audio from a Ravenna console to an ST 2110 video switcher. Verify that the Dante controller can discover AES67 audio sources and deliver them to the network. Document any quirks or required firmware updates. Many manufacturers offer pre-configured test kits or virtual instances for remote validation.

5. Train Technical Staff

Operators, engineers, and system administrators must understand IP fundamentals. Provide training on PTP configuration, multicast addressing, QoS troubleshooting, and the specific routing interfaces of the chosen platform. Many manufacturers offer certification programs (e.g., Dante Certification, Lawo Training). Hands-on workshops with the test lab are invaluable for building confidence before the system goes live.

6. Roll Out in Phases

Begin with one production area (e.g., a single news studio) and run parallel legacy and IP systems for a period. Allow time to shake out issues with timing, stability, and workflow integration. Once stable, expand to other studios, control rooms, and remote contribution links. Use a phased approach to minimize risk and allow staff to adjust. Keep the legacy system available as a fallback until the IP network has proven its reliability over several months of operation.

Real-World Use Cases

Unified AoIP and video workflows are already powering major broadcast operations worldwide. Here are three representative examples that demonstrate the value of convergence.

Live Sports Production

At a major sports broadcaster, multiple camera and microphone feeds from a stadium are carried over a single IP network using ST 2110 for video and AES67 for audio. The audio from pitch-side microphones arrives at the production console synchronized with the video from the main camera. Engineers can mix, add commentary, and feed clean outputs to broadcast and streaming platforms—all from a remote production center located miles away. The unified network also allows the broadcast engineer to adjust audio gain via remote control without any additional cabling, saving time during fast-paced events.

Radio and Television Convergence

A public broadcaster integrated its radio production studios (AoIP using Ravenna) with its television control rooms (ST 2110). Now audio from the radio studio can be seamlessly shared with the TV side for simulcasts. The same PTP grandmaster serves both facilities, ensuring zero drift. The unified routing system allows any audio source to be patched to any destination with simple drag-and-drop. This convergence has eliminated the need for dedicated audio tie-lines and has enabled cross-training of operators who can now work interchangeably between radio and TV productions.

Cloud-Based Production

Some broadcasters are extending AoIP and ST 2110 workflows into the cloud. By using virtualized processing nodes and high-bandwidth connections (e.g., AWS Direct Connect or Azure ExpressRoute), they can run audio mixing and video switching software in the cloud while maintaining low latency. PTP timing is extended to the cloud using specialized grandmaster appliances with hardware timestamping. This enables fully remote production with no hardware on-site. For example, a major news network now processes all its feed contributions from around the world via a cloud-based facility, with AoIP and ST 2110 streams coming from hundreds of remote reporters and camera crews. The result is a flexible, scalable operation that can scale up during breaking news events without capital expenditure.

The trajectory is clear: broadcast infrastructure will become entirely IP-based, with a single converged network carrying all media types. Several developments will accelerate this trend and shape the next decade of production.

Native SMPTE ST 2110 in More Devices

As the cost of FPGA-based ST 2110 processing decreases, smaller and lower-cost equipment (cameras, microphone converters, monitors) will include native IP interfaces. This eliminates the need for external gateways and reduces complexity. We are already seeing PTZ cameras and wireless microphone receivers with integrated ST 2110 output, making it easier for smaller production companies to adopt IP workflows.

5G Contribution

5G networks with low latency and network slicing capabilities will allow broadcasters to send AoIP and ST 2110 video directly from mobile units or even handheld devices. This will transform electronic news gathering and live event coverage, as a single 5G link can carry multiple audio and video streams without the need for satellite trucks or fixed fiber connections. Early field tests have demonstrated less than 10 ms end-to-end latency over 5G, well within broadcast requirements.

AI-Assisted Routing and Monitoring

Machine learning algorithms can analyze traffic patterns and automatically re-route streams to avoid congestion or equipment failure. AI-driven audio monitoring can detect sync errors or audio anomalies and alert engineers instantly. Some vendors are already embedding AI into network management platforms to predict bandwidth bottlenecks and suggest optimal routing paths. This will reduce the need for manual engineering oversight and increase uptime for complex multi-site productions.

Immersive Audio Over IP

Formats like Dolby Atmos require multiple audio objects transported with high precision. AoIP networks can handle these object-based streams (e.g., via AES67 or ST 2110-30 with channel mapping). Future standards may incorporate spatial audio metadata directly in the IP stream, enabling object-based mixing across a unified network. Broadcasters producing immersive sports or live events will benefit from the same low-latency, synchronized infrastructure that already powers traditional stereo production.

Conclusion

The integration of Audio over IP with video production workflows is not just a technological upgrade—it is a strategic imperative for broadcasters who want to remain agile and cost-effective. By adopting open standards like AES67 and SMPTE ST 2110, designing robust IP networks with proper timing and QoS, and training staff on IP operations, facilities can achieve a unified broadcast environment that simplifies operations, enables remote and cloud workflows, and scales effortlessly.

Those who embrace this convergence today will be better prepared for the future of media production. The era of separate audio and video infrastructures is ending. The unified IP broadcast plant is now the industry standard. For further reading, consult the official AES67 standard, the SMPTE ST 2110 overview, and the Audinate Dante platform. Additional resources include Ravenna by ALC NetworX and Lawo case studies.