If you work in broadcasting, you already know that moving video from point A to point B is rarely as simple as connecting a pipe. Even when your stream formally ticks all the boxes and complies with the TR 101290 standard, you might still run into inexplicable failures downstream.
When dealing with certain use cases—especially hardware like DVB modulators—stream stability is absolutely critical. These devices are notoriously sensitive, and they don't just care about what data is arriving; they care deeply about when it arrives.
This brings us to a crucial metric for any broadcast engineer: IAT (Inter Arrival Time), which is the time interval between arriving packets. High or unstable IAT values are a measure of network jitter and a recipe for broadcast failures. To keep things running smoothly, we have to look closely at average and peak IAT.
But how do we actually fix high IAT and tame an unstable stream? The answer lies in Rate Control, a core function of modern gateways.
Here is a practical breakdown of how rate control works, the trade-offs involved, and the three main approaches you can use to stabilize your broadcasts.
The Core Mechanism: Buffering vs. Latency
At its heart, rate control manages the speed of data transmission. The primary way to achieve this is through output stream buffering.
By catching the incoming packets in a buffer and releasing them at a strictly controlled rate, a gateway can completely smooth out bitrate fluctuations and normalize your IAT.
However, physics demands a trade-off: latency. Buffering intrinsically introduces delay. For example, if you need to ensure rock-solid delivery over a highly unstable network, you might set a 4–5 second buffer. This will give you a perfectly stable output, but it will also delay your stream by that exact duration.
Because every broadcasting scenario is different—ranging from ultra-low latency internal routing to delivering streams across unpredictable public networks—professional gateways typically offer a few different rate control modes.
The 3 Approaches to Rate Control
1. No Rate Control (Pass-Through)
In this mode, the stream passes directly from input to output without any buffering.
The Good: It offers the absolute minimum latency and keeps your CPU load practically at zero.
The Bad: Any jitter, spike, or drop in the original stream will be passed straight through to your output.
When to use it: This is perfect for simple restreaming tasks where the input stream is already perfectly stable.
When to avoid it: For unstable input streams, remultiplexing, or transcoding.
2. Average Mode (Average Bitrate Control)
Here, the restreamer buffers the stream until a specific fill level is reached. The precise sending time for each packet is then calculated based on the actual input bitrate, which the system measures using its own internal clocks.
The Good: Because this mode ignores PCR (Program Clock Reference) timestamps, it is incredibly effective when your stream's PCR is missing, broken, or highly inaccurate.
The Bad: It requires higher CPU usage than a simple pass-through.
When to avoid it: This mode struggles with streams that have massive bitrate fluctuations exceeding 2 seconds—for example, streams that have been converted from HLS to UDP.
3. TS PCR Mode
This is the gold standard for broadcasting Transport Streams (TS). The stream is buffered, but unlike Average Mode, the packet sending time is strictly dictated by the PCR timestamps embedded within the stream itself.
The Good: It ensures that your output bitrate perfectly matches the PCR-defined bitrate, resulting in a highly compliant and stable stream.
The Bad: This precision comes at a cost—you can expect higher CPU usage and higher latency.
When to avoid it: Because this method relies entirely on the stream's internal timing, it absolutely cannot be used for input streams that have broken, missing, or inaccurate PCRs.
What About High-Bitrate Streams?
When you push bitrates higher (typically 10 Mbps and above), or when you are feeding incredibly picky equipment that requires sub-millisecond IAT precision, standard rate control might need an extra boost.
In these advanced scenarios, you need a high-precision broadcasting option. When enabled alongside Average or TS PCR modes, this feature performs extremely accurate IAT calculations to guarantee microscopic precision between packets. The trade-off? Doing math at that speed significantly increases CPU load, so it should only be enabled when your hardware truly requires it.
Bringing It All Together with Elecard
Understanding rate control is one thing; having the right tool to implement it is another.
At Elecard, we engineered the Elecard CodecWorks Gateway specifically to handle these real-world broadcast challenges. Whether you need to cleanly pass through a stable stream with zero latency, rebuild the timing of a stream with broken PCR, or feed a highly sensitive DVB modulator, CodecWorks Gateway gives you the exact tools you need to keep your broadcast stable, compliant, and flawless.
Want to learn more about optimizing your video delivery? Check out the full capabilities of Elecard CodecWorks Gateway and take control of your stream stability.
Top comments (0)