Everyone knows broadcast looks a lot different than it did 10 years ago.
IP dominates. Cloud workflows. Software defined. Remote production. Love it. But hang on…
Here’s what most people are forgetting…
Signal integrity still suffers. Hard.
Sure, IP delivery has solved a lot of problems. But migrate your broadcast infrastructure to IP and what do you have? More IP. Then watch all your signal alignment fall to pieces.
Enter the broadcast headend system. That’s where Thor Broadcast comes in.
Jump Ahead:
- What Is Signal Integrity in Broadcast AV?
- Why Jitter Hasn’t Gone Away in the IP Era
- The Broadcast Headend System’s Role
- Low-Jitter Transport: What It Means, Really
- How To Actually Protect Signal Integrity, Start-to-Finish
What Is Signal Integrity, Anyway?
If something looks weird on a screen, did the signal lose integrity?
Sort of. Signal integrity refers specifically to the accuracy with which a signal travels from point A to point B.
SDI stuff was easy. Cable quality. Impedance math. Termination. Boom.
IP infrastructure introduces a whole lot more failure points along the way. Compression. Encryption. Cloud. Streaming. Casting. WiFi. Each link is another chance for dropped frames.
Here’s the catch.
IP networks are asynchronous. SDI required synchronous clocks and always did point-to-point, full-speed video transport. IP was designed to solve business problems, not pass 3Gbps video streams from Point A to Point B.
That’s where jitter becomes a problem.
Why Jitter Hasn’t Gone Away in the IP Era
Have you ever seen a video buffer icon twitch when you’re streaming video? That’s jitter. Packet arrival time variance.
Old school SDI transmitted on house clocks with reliable hardware synchronisation. Framing errors were rare. Signals were consistent.
Ethernet and IP video networks experience jitter as packets come in late or out of order. Packets wait in the de-jitter buffer at the receiving device. If there are too many packets to process, buffer underflow occurs.
Visualize jitter like this:
- Frame skips
- Frozen image
- Audio going out of sync live on air
- Visible artifacts on screen
According to research data, every millisecond of deviation in packet arrival time can cause packets to be stalled and dropped at the receiver. Low-latency systems are much more sensitive to packet delay.
Broadcast has switched to SMPTE ST 2110 and ST 2022-6 everywhere. Those standards dictate how RTP, video, audio, and metadata travel over IP. That solved a lot of compatibility issues. But it doesn’t automatically fix jitter on your network.
How Your Broadcast Headend System Impacts Signal Integrity
If broadcast headsend systems are receiving signals from satellite, fibre, terrestrial, SDI, or IP inputs… what happens if those inputs don’t play nicely together?
That’s where the headend comes in. Hotels, hospitals, stadiums, cable ops, and enterprise AV shops use headend systems to prepare incoming feeds for distribution. They decode. They process. They re-encode and send signals out over IP to displays and outputs.
Think of your headend like the body’s immune system. Everything that comes down pipe needs to get scanned and treated for virus before it reaches the heart. Any corruption along the way impacts every downstream device.
Once audio and video reach the headend, there’s no going back. Signals travel from there to endpoints, out-of-sync, frozen, missing frames, with artifacts on screen. If your system doesn’t have world-class clock recovery and timing stability at the headend layer, jitter will destroy signal integrity by the time content reaches endpoint devices
The global live IP broadcast equipment market hit $1.84 billion in 2024 and will grow by a 17.6% CAGR through 2031.
IP is the present and future. The broadcast headend system is where it all starts.
Low-Jitter Transport: What The Heck Does That Mean?
Hopefully, by now, you’ve realized that low-jitter transport isn’t magical marketing speak.
It means your system delivers a clean, stable signal with guaranteed timing tolerance — no more and no less.
Signal recovery, clock regeneration, precision buffering. Its real stuff.
Low jitter-capable broadcast headend systems have all of these features:
- Proper timing recovery
- Clock regeneration at the headend layer
- Hardware buffering
- PTP synchronisation capability
- Low phase-noise oscillators used during the signal processing phase
- Correct QoS Configuration on your network to prioritise video traffic
Your go-to IT guy installing QoS on the network doesn’t fix things. Software clocking without iron-clad hardware stability at the headend does not equal low-jitter transport.
Strategies for Keeping Your Signal Clean From Start To Finish
Picture this: You’re live on air. Sound drops out. Video freezes on a presenter’s face. Then everyone watches her jaw twitch awkwardly for five seconds.
It happens. More often than you’d think. Disaster recovery plans do not apply to this situation.
Noise-on-air is usually caused by silent signal integrity failures. Jitter. Packet loss. Misconfiguration.
Any number of issues can cause dropped frames. Here’s how to spot them before you drop on air.
- Buy headend systems that measure jitter and tell you how bad it is.
- Check IPAT on your network regularly to see if packet timing is becoming irregular.
- Don’t trust cheap commodity switches. Spend the money on professional broadcast quality network devices designed for video traffic. They won’t map 5G-SDI to SMPTE 2022-6 correctly, either.
- Did someone say 3G-SDI? Make sure you’re feeding the right signal into your headend equipment.
- For the love of all that is holy, don’t skip clocking. End-to-end synchronisation is your friend.
The global broadcast equipment market size is expected to reach $9.38 billion by 2033.
Don’t let cheap equipment cause you heart attacks on air.
Signal Integrity Will Never Go Out Of Style
Broadcast has changed, but signal integrity isn’t going away. Adopting IP doesn’t magically eliminate jitter.
With SDI you could see where signal problems started. Now they’re hidden behind layers of software and network equipment.
Headend systems are the first line of defence against on-air failures. Everything that comes into your headend needs to get purified before it goes out.
So do you really want to take chances with software clocking?
True low-jitter transport starts at the headend layer. Everything else is just hoping for the best.
For broadcast environments. Hope is not a strategy.
