Synchronising Networked Audio at Scale with PTP² Mesh

Audio is unforgiving

Networked audio standards (AES67 for IP audio interoperability, Ravenna for high-end broadcast audio, Dante for AV installations) all deliver multichannel audio across IP networks, replacing the analogue and AES/EBU digital audio infrastructure that dominated broadcast for decades. The synchronisation requirements are tight — phase alignment between channels is audible if it slips beyond a sample period (about 21 microseconds at 48 kHz). Unlike video, where a frame misalignment is annoying but recoverable, an audio sample misalignment is a click or a pop that the listener notices immediately.

The unforgiving nature of audio sync is what makes the operational discipline so important. A timing fabric that's correct 99.9% of the time but slips for a few seconds occasionally is fine for video — the artifact passes and the next frame is aligned. The same fabric is unacceptable for audio, because every slip is audible to the listener and there's no recovery from a sample-level click.

Why PTP² Mesh exists

Standard PTP — linear boundary clock chain from a single grandmaster — works fine for audio in a stable network. The problem is that real audio fabrics often span unreliable links. Event venues with intermittent network conditions during setup. Outside broadcast trucks connecting back to a studio over multiple network paths. Distributed broadcast facilities where the audio fabric crosses building boundaries and depends on links that occasionally drop. In each of these environments, a single grandmaster failure or a single link failure can disrupt the audio fabric just long enough to produce an audible artifact.

PTP² Mesh addresses this by running PTP across a self-healing mesh topology with automatic path failover. Every PTP-aware device in the mesh maintains multiple paths to the active grandmaster, and link failures trigger immediate path switching rather than waiting for the standard PTP announce timeout. The audio fabric stays in sync through link transitions that would disrupt a linear PTP deployment.

How PTP² Mesh works in practice

Architecturally, every PTP-aware device in the mesh maintains active PTP sessions with multiple neighbours and tracks the current best path to the active grandmaster. When a link drops or a neighbour becomes unreachable, the device immediately fails over to its next-best path without waiting for the announce timeout. The transition is fast enough (typically sub-second) to avoid the audible artifact a slower failover would produce.

From an audio engineer's perspective, the mesh is invisible during normal operation — the timing fabric just works, and the engineer manages the audio fabric without thinking about the underlying PTP topology. During link failures, the mesh handles the failover automatically and the audio stays in sync. This is the right operational model for environments where the timing fabric needs to be reliable but the engineering team is focused on the audio rather than the network.

Where TimeBeat fits

TimeBeat ships PTP² Mesh as part of the broader hardware and software platform that broadcast and audio facilities use to run reliable timing fabrics. Our customers include broadcasters, OB truck operators, event audio specialists, and distributed audio production facilities across European and US markets. For audio engineering teams running into reliability issues with standard linear PTP, the conversation usually starts with whether PTP² Mesh fits the operational profile.