What Did PTP Kill in Broadcast?
What Did PTP Kill in Broadcast?
Summary
The short answer is a bit sharp:
PTP killed the era of separate physical synchronization infrastructure in broadcast.
Black burst, tri-level sync, LTC, VITC, word clock, and SDI ANC timecode are still historically important. Some of them still live in certain facilities, and some are still required for gateways and legacy devices. But they are no longer the main timing model of an ST 2110 system.
In the ST 2110 world, the common reference is:
PTP + SMPTE ST 2059
In other words, video, audio, ANC, RTP timestamp alignment, and device synchronization are managed through a single IP timing infrastructure.
1. PTP’s victims
The following table is intentionally provocative. When I say “dead”, I do not mean these signals were never used or have no historical value. I mean they are no longer the central synchronization backbone in an ST 2110 system.
| Legacy reference / timing system | Role in the SDI world | ST 2110 equivalent | Status |
|---|---|---|---|
| Black Burst | SD video reference / analog genlock | PTP / ST 2059 | Dead as the main backbone |
| Tri-Level Sync | HD video reference / genlock | PTP / ST 2059 | Dead as the main backbone |
| LTC | Linear timecode over a separate cable | PTP time + ST 2110 timing + metadata workflows | Dead as the main timing carrier |
| VITC | Timecode embedded in the video signal | RTP timestamp, PTP alignment, ANC metadata | Its SDI-centric role is dead |
| Word Clock | Separate clock reference for audio devices | PTP / ST 2110-30 / AES67 timing | Dead as a separate clock backbone |
| ATC / SDI ANC TC | SDI ancillary timecode | ST 2110-40 ANC flow | Its SDI-carrier-dependent role is dead |
The important nuance is this: PTP did not remove the need for timecode or synchronization. It connected those needs to one common timing model.
2. Why did the SDI world need so many references?
In the SDI world, every problem had its own physical habit:
- Black burst or tri-level sync for video reference
- LTC or VITC for timecode
- Word clock for audio synchronization
- ANC timecode for auxiliary timing information carried inside SDI
This approach worked; in fact, it worked reliably for years. But physically, it was complex:
- Separate reference distribution amplifiers
- Separate cable paths
- Separate patch and test points
- Separate measurement tools
- Separate troubleshooting logic
In a broadcast facility, video may be working, audio may be drifting, timecode may come from another reference, and video genlock may be fed by a different distribution path. So the question “is sync present?” does not have a single answer.
The advantage of this model was simplicity and familiarity. The disadvantage was that time was managed not as one system, but as several parallel systems.
3. What did PTP actually do?
PTP came into the broadcast facility and effectively said:
“You do not need separate physical reference distribution for video, a separate clock for audio, and a separate cable for timecode. Lock everyone to the same time and derive media timing from there.”
In ST 2110 systems, PTP gains its broadcast profile through SMPTE ST 2059. This means devices do not merely say “I received time from the network”; they use an epoch, domain, alignment, and timing behavior that make sense for broadcast.
That is why PTP is not just a “network clock”. In the ST 2110 world, PTP is the facility’s shared timing reality.
4. The mental difference between SDI and ST 2110
In the SDI world, time was often a physical reference that accompanied the signal. In the ST 2110 world, media and time are separated:
- Media is carried as RTP packets
- Flow information is described by SDP
- Connections are managed through NMOS or orchestration
- Time is distributed through PTP
This separation may look complex at first. But at facility scale it is very powerful. Video, audio, and ANC no longer have to be embedded in the same cable; they can be separate flows while still being locked to the same time reference.
| SDI approach | ST 2110 + PTP approach |
|---|---|
| Video, audio, and ANC are often inside the same SDI carrier | Video, audio, and ANC may be separate RTP flows |
| Reference is distributed through physical sync cables | Reference is distributed through PTP on the IP network |
| LTC / VITC / ATC may be different time carriage methods | Time is derived from PTP; metadata may be a separate flow |
| Audio may require a separate word clock infrastructure | Audio clock is tied to PTP through ST 2110-30 / AES67 timing |
| Troubleshooting is cable- and signal-based | Troubleshooting is based on PTP, RTP, multicast, SDP, and NMOS |
5. The technically correct version of “PTP killed all of them”
A more technically accurate sentence is:
PTP killed the separate physical timing distribution model represented by black burst, tri-level sync, LTC, VITC, and word clock.
Their functions did not disappear completely:
- Video still needs frame alignment
- Audio still needs a sample-accurate clock
- Timecode is still important for production and archive workflows
- ANC may still carry captions, AFD, timecode, and metadata
But all of these now connect back to the same fundamental question:
Are the devices locked to the same PTP time?
6. How does ST 2110-40 change the role of ATC?
In the SDI world, timecode and some auxiliary information can be carried in the ancillary data area. ATC is one of the important ways to carry timecode inside SDI.
In the ST 2110 world, video, audio, and ANC are separated. Therefore ANC data can also be carried as a separate RTP flow. This is where ST 2110-40 comes in.
ST 2110-40 provides:
- Transport of SDI ancillary data as a separate flow in IP
- Separation of timecode, captions, AFD, and similar metadata from the video flow
- Correct receiver-side alignment of metadata through the PTP/RTP timing relationship
So when we say “ATC is dead”, the more accurate statement is:
ATC’s central role as something tied to the SDI carrier is dead; ANC metadata moved into the IP flow model through ST 2110-40.
7. Did PTP make everything easier?
No. PTP simplified the cabling and the reference model, but it made system engineering more invisible and more disciplined.
In the SDI world, if the reference cable was missing, you could often see it physically. In the ST 2110 world, a PTP problem can be more subtle:
- The grandmaster has changed
- The PTP domain is wrong
- A boundary clock behaves incorrectly
- A switch is assumed to be PTP-aware but is not
- QoS does not protect PTP packets
- An audio device remains in AES67 domain 0 while the video system operates in ST 2059 domain 127
So when PTP says “I do everything over one network”, it also requires this:
You must design that network as broadcast timing infrastructure.
8. The new operational checklist
In a PTP-centric ST 2110 facility, the old reference checklist changes.
| Old question | New question |
|---|---|
| Is black burst present? | Is PTP lock present? |
| Is tri-level genlock correct? | Are the ST 2059-2 domain and profile correct? |
| Is LTC arriving? | Is the timecode/metadata flow correct and aligned to PTP? |
| Is word clock present? | Is ST 2110-30 / AES67 audio clock locked to PTP? |
| Is SDI ANC timecode passing? | Is the ST 2110-40 ANC flow carried correctly? |
| Is the reference DA working? | Are the grandmaster, BMCA, boundary clocks, and QoS correct? |
This transition is not only technical; it is operational. A broadcast engineer now needs to read PTP offset, RTP sequence, multicast state, and NMOS connection state as naturally as an oscilloscope.
9. Conclusion
PTP did not remove time from broadcast. It put time at the center.
But it did kill:
- Dependency on a separate analog sync backbone for video reference
- The habit of distributing timecode over separate physical cabling
- Separate word clock distribution for audio sync
- The centrality of timing tied to the SDI carrier
- The era where every subsystem lived with its own reference
The SDI world could be summarized like this:
A separate cable, distribution path, and reference for everything.
The ST 2110 + PTP world can be summarized like this:
One time source, one IP timing infrastructure, multiple media flows.
That is the biggest change PTP brought to broadcast: it took time out of the cable and made it the shared IP reality of the facility.