How IP audio stays in sync
Once audio travels over a network, timing, multicast behaviour and security become part of the audio design. This page shows how we treat them as one system.
One signal path, planned end to end
Timing, transport and control designed as one system.
One clock, one transport, one control plane
Once audio travels over a network, timing, multicast behaviour and security become part of the audio design. We treat them together, not as separate projects.
Timing
PTP domain design, grandmaster redundancy and boundary clocks, so every device stays in one sync.
Transport
Multicast and IGMP planning, QoS, and redundant ST 2022-7 paths, so the signal arrives without dropouts.
Interoperability & control
Dante to AES67 stream mapping, ST 2110-30 workflows, and NMOS IS-04 and IS-05 discovery and connection management.
Where IP audio projects go wrong
These five problems cause most of the clicks, drops and lost streams we are asked to diagnose.
The grandmaster is chosen by accident
If nobody sets a priority, the best-looking clock wins, and it may be a device that is switched off overnight. We name the grandmaster and its backup.
No querier, so multicast floods the network
IGMP snooping needs a querier. Without one, multicast can reach every port and slow devices drop out.
Mixed PTP profiles with no boundary clock
Dante and AES67 or ST 2110 devices can use different PTP profiles. Boundary clocks and a clear plan keep them in one time domain.
Audio and timing share a queue with everything else
Without QoS, a large file transfer can delay timing packets. We mark and prioritise audio and PTP end to end.
Two networks that share one weak point
Redundancy only helps if the paths are separate. A shared switch, cable route or power feed removes the benefit.
Let's talk about your project
Tell us what you have, and we will suggest the right first step.