Quick Answer
PTP is the timing layer used when millisecond-grade computer time is not enough. In broadcast and AoIP systems, it is there to keep devices aligned tightly enough for audio, video, and timing-sensitive transport. The exact behavior still depends on the profile, device support, and switch design.
Why typical Network Time fails
NTP (Network Time Protocol) is the standard for computer clocks. It syncs laptops to the correct time of day globally, accurate to a few milliseconds. But in broadcast audio (working at 48,000 samples per second), one sample is 20 microseconds long. Syncing audio interfaces with millisecond jitter results in severe phase distortion and dropped samples.
PTP (Precision Time Protocol) was designed for industrial automation and later adopted by Dante, AES67, and SMPTE 2110. It can provide synchronization in the sub-microsecond range in well-designed systems, and it often fills the timing role that legacy reference signals handled in all-IP facilities.
The BMCA (Best Master Clock Algorithm)
In PTP, you don't manually assign a master clock (though you can weight priorities). The BMCA runs automatically on the network, evaluating every PTP-capable device.
- It checks clock quality (e.g., GPS-locked hardware vs a software clock).
- It checks priority settings (Priority 1 and Priority 2 vectors).
- It checks MAC addresses in the event of a tie.
The winner becomes the Grandmaster Clock. Every other device on the network becomes a Follower, constantly listening to Announce and Sync messages to adjust their local oscillators.
L2 vs. L3 PTP Profiles
PTP can operate at different layers of the OSI model depending on the industry standard:
- Dante (L3): Uses Multicast PTP over IP (Layer 3). Requires a router or a Layer 3 switch to handle traffic across subnets, though it typically resides in a single VLAN.
- SMPTE 2110 (L2/L3): Often uses the ST 2059-2 profile, which relies on a specific set of PTP parameters (like 128 messages per second) to ensure sub-microsecond alignment for video frames.
How to Use It
When a system depends on PTP, check the profile, clock domain, switch behavior, and QoS model before patching media. Treat timing as infrastructure, not as an afterthought that will fix itself once audio or video starts moving.
Common Mistakes
If your devices are not syncing, start with these common failure points:
- Clock Domain Mismatch: devices must share the correct domain and timing profile.
- QoS or queue problems: timing packets need the switch behavior the system was designed for.
- Profile mismatch: not every PTP-capable device is using the same broadcast-oriented profile.
- Unsupported switch behavior: boundary, transparent, and multicast behavior still matter.