Why it matters
A master-control operator sees a PCR alarm on an incoming transport stream. The encoder looks healthy, the contribution link is connected and the picture may still decode. Which team owns the fault?
Program Clock Reference (PCR) timestamps let an MPEG-TS receiver reconstruct the sender's clock. A bad PCR cadence, a discontinuity or inaccurate timing can affect decoder stability. But a probe analyzing packets after IP transport may also be observing packet pacing, buffering or remultiplexing effects rather than a defect in the encoder's original clock.
That distinction matters during incident response. Replacing an encoder because a downstream probe reports jitter can waste the outage window while leaving the actual cause untouched.
The underlying engineering guidance is established, not a newly announced 2026 standard. ETSI TR 101 290 V1.4.1, published June 2020, defines transport-stream monitoring and PCR measurement methods: https://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.04.01_60/tr_101290v010401p.pdf
What the alarm does and does not say
ETSI separates PCR repetition, discontinuity signaling and accuracy into distinct indicators. A repetition alarm concerns spacing between references; an unflagged discontinuity concerns a clock jump; accuracy requires comparing PCR values with a suitable timing model. They are not interchangeable diagnoses.
The frequently cited PCR accuracy threshold is plus or minus 500 nanoseconds, but applying it correctly requires appropriate timing and measurement conditions. Tektronix's technical explanation describes how a reference clock is used for the comparison: https://www.tek.com/en/support/faqs/what-definition-error-24-pcraccuracyerror
An important operational caveat: PCR accuracy analysis assumes a suitable constant-bitrate stream and reliable measurement timing. Arrival jitter from a packet network cannot simply be equated with encoder PCR inaccuracy. A transport-stream capture made after buffering can also behave differently from a live hardware-timestamped observation.
Six acceptance checks
1. Locate the first failing measurement point. Compare PCR measurements at encoder output, after the IP receiver and after any remultiplexer or gateway. Record the exact PID, service, probe clock source and observation interval. If only the downstream point alarms, investigate that boundary before escalating to encoding.
2. Separate PCR repetition from PCR accuracy. Log the actual metric and threshold, not just a generic "PCR error." Check whether a PCR PID is missing references, whether the timestamps jump or whether a timing estimate is unstable. Each suggests a different fault path.
3. Validate the measurement method. Confirm whether the probe uses hardware arrival timestamps, a recovered transport bitrate or software packet arrival times. A tool can correctly flag an irregular captured stream without proving which upstream device created the irregularity.
5. Test failover and remultiplexing deliberately. Switch contribution sources, restart a gateway and perform the expected programme transition in a controlled maintenance window. Record whether PCR PID selection, discontinuity flags and receiver recovery behave as intended. Do not interpret every signaled discontinuity as an encoder defect.
6. Verify the decoded service. Correlate alarms with audio/video synchronization, visible freezes, decoder lock and recovery time. A standards alarm is a valuable diagnostic signal, but viewer impact and service continuity determine incident severity. The TSDuck PCR verification plugin is one available independent inspection aid: https://www.tsduck.io/doxy/d7/d70/classts_1_1PCRVerifyPlugin.html
What operators should change
A useful alarm ticket should include the PCR PID, affected programme, threshold crossed, first failing observation point, bitrate assumption, timing source, concurrent packet-loss or continuity events, and decoded-output evidence.
For commissioning, collect a baseline from the encoder and each downstream processing boundary. Repeat the same measurement during normal operation, planned switching and recovery. This turns a generic red PCR indicator into an actionable comparison.
The engineering takeaway is simple: PCR monitoring belongs in the chain, but fault ownership must follow evidence across the chain. An encoder, IP gateway, remultiplexer and measurement probe can each influence what an operator observes. Treat PCR alarms as a starting point for localization, not a verdict on a single device.
Image credit: Peterspexarth, KCTV5 Tower-1, January 29, 2026, CC BY 4.0. Archival illustrative photograph, not an image of a documented PCR fault. For publication, crop the original photograph to 1600 × 838, re-encode as JPEG and disclose the modifications under CC BY 4.0.



