Technical Article

Most broadcast engineering teams are now more fluent in IP than in RF. Satellite has not gone away — it remains the only practical way to deliver one signal to many receivers across a wide footprint, and it remains independent of terrestrial infrastructure in a way no IP path can match — but the people responsible for it increasingly arrived through networking rather than through transmission engineering. They inherit a leased transponder, a set of modulation parameters someone chose years ago, and a demodulator whose output they treat as a black box that produces a transport stream.

This article covers the satellite half of a hybrid contribution and distribution chain in the terms that half is actually specified in: modulation and coding, spectral efficiency, transponder capacity, link budget and margin, and what happens at the boundary where recovered RF becomes IP. It assumes familiarity with IP media transport and none with RF.

For the IP side of the same chain — ST 2110, JPEG XS, SRT and their latency and bandwidth characteristics — see Broadcast network modernisation for IP- and cloud-based live production, which is the canonical comparison.

Satellite ground infrastructure

How it works

The chain, end to end

A satellite contribution or distribution path runs: encoder → multiplexer → modulator → upconverter and high-power amplifier → uplink antenna → satellite transponder → downlink antenna → low-noise block downconverter → demodulator → transport stream. The satellite itself is, for most contribution purposes, a bent-pipe repeater: it receives on one frequency band, amplifies, translates to another band, and retransmits across its coverage footprint. It does not decode, buffer or route.

Everything that determines whether the link works — and how much data it carries — is decided at the two ends and in the choice of transponder.

DVB-S2 and DVB-S2X: what the parameters mean

DVB-S2 and its extension DVB-S2X define how a transport stream is turned into a modulated carrier. Three parameters do the work.

Modulation order determines how many bits each transmitted symbol carries. QPSK carries 2 bits per symbol, 8PSK carries 3, 16APSK carries 4, 32APSK carries 5, and DVB-S2X extends the range further. Higher orders carry more data in the same bandwidth but require a better signal-to-noise ratio at the receiver to distinguish the symbols. This is the central trade in satellite link design: spectral efficiency is bought with link margin.

Forward error correction rate — expressed as a fraction such as 3/4 or 9/10 — determines what proportion of transmitted bits carry payload rather than error protection. A rate of 3/4 means three of every four bits are payload. Lower rates spend more capacity on protection and tolerate worse conditions.

Roll-off factor determines how much bandwidth the carrier occupies beyond its symbol rate. DVB-S2 offers 0.35, 0.25 and 0.20; DVB-S2X adds 0.15, 0.10 and 0.05. A lower roll-off packs the same symbol rate into less spectrum, which directly increases how much you can fit in a leased transponder.

Together, modulation order and FEC rate give spectral efficiency in bits per second per hertz — the single number that converts leased bandwidth into usable throughput.

Transponder capacity: from megahertz to megabits

Satellite capacity is leased in megahertz of transponder bandwidth, not in megabits. Converting between the two is the calculation that determines how many services a lease will carry.

Symbol rate (Msym/s) ≈ transponder bandwidth (MHz) ÷ (1 + roll-off)

Useful bitrate (Mbps) ≈ symbol rate (Msym/s) × bits per symbol × FEC rate

A 36 MHz transponder at 0.20 roll-off supports roughly 30 Msym/s. At 8PSK (3 bits per symbol) with FEC 3/4, that is approximately 67 Mbps of usable payload. The same transponder at QPSK with FEC 1/2 delivers roughly 30 Mbps — less than half — but tolerates a far worse link.

Two consequences follow directly. First, the modulation and coding decision is a capacity decision with a reliability price, and it is made once for the whole multiplex rather than per service. Second, roll-off matters more than it looks: moving from 0.35 to 0.20 on the same transponder yields around 11% more symbol rate for no change in modulation or coding, which is capacity available for the cost of a modulator configuration.

Link budget and margin

The link budget is the accounting that determines whether the receiver sees enough signal to demodulate at the chosen modulation and coding. Its terms:

Transmit power and antenna gain at the uplink, combined as effective isotropic radiated power. Larger antennas and higher-power amplifiers raise it.

Free-space path loss — the dominant term, and a function of distance and frequency. A geostationary path is roughly 36,000 km each way, and higher frequency bands lose more.

Satellite performance — the transponder’s receive sensitivity and its downlink transmit power over the coverage footprint, published by the operator as contours. Where you sit in that footprint materially changes your budget.

Receive antenna gain and system noise temperature, combined as G/T. Larger dishes and better low-noise blocks raise it.

Atmospheric and rain attenuation — the variable term. Ku-band and especially Ka-band suffer significant rain fade; C-band is far more resilient, which is why C-band remains preferred for high-availability contribution in tropical regions despite its larger antenna requirement and the pressure on its spectrum allocation.

The result is a received signal-to-noise ratio, compared against the threshold the chosen modulation and coding requires. The difference is link margin, and it is specified against an availability target — typically expressed as a percentage of the year the link must meet threshold. Designing for 99.9% availability rather than 99.5% costs several dB of margin, which is paid for either in antenna size, in transmit power, or in reduced spectral efficiency.

Adaptive coding and modulation

DVB-S2 and S2X support adaptive coding and modulation, which varies modulation order and FEC rate in response to measured link conditions rather than fixing them at worst case. In clear sky the link runs at high spectral efficiency; as rain fade develops, it steps down to more robust settings and lower throughput rather than failing.

This changes the design problem in a way that matters for IP integration. A fixed-modulation link delivers constant bitrate. An ACM link delivers variable bitrate, and the downstream chain must handle a capacity that changes with the weather. In practice this means either a statistically multiplexed service group that can absorb the variation, or a designed degradation policy that sheds or reduces services in a defined order. It is not a decision the demodulator can make on its own, and it is the single most common integration surprise when an ACM link is introduced into a chain designed around fixed capacity.

The RF-to-IP boundary

The demodulator is where the two halves meet, and understanding what it does and does not do resolves most of the confusion at this boundary.

What comes out. The demodulator recovers the MPEG transport stream that was fed to the modulator. Provided the link is above threshold, the recovered stream is bit-identical to the transmitted one — satellite transmission is not a lossy process in the way a congested IP path is. It either works or it degrades sharply once margin is exhausted. There is no gradual quality slope.

What has to be added. A transport stream recovered from RF has no IP identity. Encapsulation into TSoIP over UDP or RTP, or into SRT, is applied at this point, along with addressing, any required protection (FEC, ST 2022-7 duplication), and encryption for onward transport over networks the operator does not control.

Timing changes character. On the satellite side, timing is carried in the transport stream’s programme clock reference and recovered by the receiver. Once on IP, packet delay variation is introduced that did not exist on the RF path, and downstream receivers must have adequate buffering to recover the clock cleanly. Underestimating this is a common cause of intermittent downstream faults after a satellite-to-IP conversion that appears otherwise clean.

Monitoring domains do not overlap. RF health is measured in Eb/No or MER, symbol rate lock, and bit error rate before and after FEC. IP health is measured in packet loss, jitter, round-trip time and buffer occupancy. Neither set predicts the other, and a hybrid operation needs both correlated into one picture with defined failover triggers spanning the two — otherwise the operations team can see a healthy IP path and a failing service without being able to connect them.

Centralisation is the architectural payoff. Terminating RF at a small number of earth stations and distributing the recovered streams over IP means transponder capacity becomes available to any connected site, rather than to whichever sites have their own dish and receiver stack. This is the structural argument for satellite-to-IP migration and it is a consequence of this boundary, not of the IP transport itself.

Why GEO latency is what it is

Geostationary orbit sits at approximately 35,786 km. At the speed of light, one hop up and down is roughly 240 ms of propagation alone, and total one-way latency including encoding, modulation and ground processing typically falls in the 300–600 ms range.

This is physics, not implementation, and it cannot be tuned. It is why interactive formats, multi-site live mixing and tight lip-sync workflows either avoid GEO in the critical path or use it asymmetrically — bulk one-to-many distribution over satellite, with a low-latency IP return path for control, talkback and preview.

Medium and low earth orbit constellations reduce propagation delay substantially by being closer, at the cost of operational complexity: satellites move relative to the ground, so terminals must track and hand over between them, and the terminal and service model differs from a leased transponder. For broadcast contribution the practical position today is that LEO is viable for specific field-contribution use cases, generally in combination with bonding and resilient transport, rather than as a replacement for leased GEO capacity in one-to-many distribution.

Why it matters in broadcast

One-to-many is still satellite’s structural advantage. A single uplink reaches every receiver in the footprint simultaneously at no incremental cost per receiver. No IP architecture replicates that economic shape; IP distribution costs scale with the number of endpoints. For wide-footprint primary distribution to many affiliates, this remains decisive.

Independence from terrestrial infrastructure is a resilience property. A satellite path shares no failure mode with a terrestrial network. That makes it valuable as a protection path even in operations that have otherwise migrated, and it is why hybrid rather than replacement is the dominant architecture.

Capacity is a fixed commitment, and it is fully spent or wasted. A leased transponder costs the same whether it is running at 60% or 95% of its usable bitrate. Modulation, coding and roll-off decisions therefore have direct commercial consequence, and reviewing them against current equipment capability frequently releases capacity that was configured conservatively years earlier.

The skills are genuinely different, and thinning. RF engineering — antenna alignment, link budgets, operator coordination — is a distinct discipline from network engineering, and the pool is shrinking. Centralising demodulation at fewer sites concentrates the requirement for that skill where it can be sustained, which is an operational argument for migration independent of the technical one.

Technical specifications and trade-offs

Modulation and coding trade-off

Figures are indicative and depend on roll-off, exact FEC rate and transponder characteristics. Required margin rises with modulation order, so the top rows are only available where the link budget supports them across the availability target.

Configuration

Bits per symbol

Approx. usable bitrate, 36 MHz at 0.20 roll-off

Required link margin

Typical use

QPSK, FEC 1/2

2

~30 Mbps

Lowest

High-availability paths, rain-prone regions, C-band contribution

QPSK, FEC 3/4

2

~45 Mbps

Low

General-purpose distribution with comfortable margin

8PSK, FEC 3/4

3

~67 Mbps

Moderate

Common distribution configuration

16APSK, FEC 3/4

4

~90 Mbps

High

Capacity-efficient links with good antennas and stable conditions

32APSK, FEC 5/6

5

~125 Mbps

Highest

Point-to-point contribution with large antennas, clear-sky regions

Frequency band characteristics

Band

Rain fade

Antenna size for given G/T

Typical broadcast use

C-band

Low

Largest

High-availability contribution and distribution, tropical regions

Ku-band

Moderate

Medium

Mainstream contribution and distribution

Ka-band

High

Smallest

Higher-throughput services where fade mitigation is designed in

Planning notes

  • Review roll-off before leasing more bandwidth. Moving from 0.35 to 0.20 on existing capacity releases roughly 11% more symbol rate with no change to modulation or coding.

  • Specify availability, not margin. Margin is the output of an availability target, a location and a band. Specifying margin directly hides the assumption that matters.

  • Model ACM as variable capacity from the start. If the downstream chain assumes constant bitrate, ACM will surface as an integration failure during the first significant rain event rather than during commissioning.

  • Size IP-side buffering for clock recovery. Packet delay variation introduced at the RF-to-IP boundary did not exist upstream; downstream receivers need buffer to recover PCR cleanly.

  • Correlate RF and IP monitoring into one view with failover triggers spanning both domains. Separate dashboards produce incidents nobody can diagnose.

Related approaches and standards

  • DVB-S2 (ETSI EN 302 307-1) defines second-generation satellite modulation and coding, including the ACM framework.

  • DVB-S2X (ETSI EN 302 307-2) extends it with finer modulation and coding granularity, lower roll-off options and additional higher-order modulation schemes.

  • MPEG-TS (ISO/IEC 13818-1) is the carriage format across the RF path and the format recovered by the demodulator, which is what makes the boundary conversion a wrapping operation rather than a transcode.

  • SMPTE ST 2022-2 defines constant-bitrate MPEG-2 transport stream carriage over IP — the standard TSoIP form recovered satellite streams are placed into.

  • SMPTE ST 2022-7 provides seamless protection switching across diverse paths, and is the mechanism by which a satellite-derived stream and an IP-derived stream can protect one another once both are on IP.

  • SRT provides resilient encrypted transport for onward distribution over networks the operator does not control, after the RF-to-IP conversion.

  • BISS and BISS-2 provide conditional access for contribution feeds, applied on the transport stream and therefore independent of whether the path is RF or IP.

How Appear addresses this

The X Platform carries the RF-to-IP boundary inside one chassis rather than across a chain of separate devices. On X10 and X20, the SRx100 is a DVB-S/S2/S2X demodulator with multiple demodulators per module, and the SMx100 is a DVB-S/S2X modulator carrying two modulated carriers. Both sit alongside transport-stream processing, conditional access, and IP output modules, so a recovered transport stream is remultiplexed, protected, encrypted, and encapsulated as TSoIP or SRT without leaving the chassis — which removes a set of inter-device conversion and timing handoffs that are a common source of the clock-recovery problems described above.

On the RF monitoring side, the demodulator reports per-carrier CNR, link margin, Eb/N0, bit and packet error rate, carrier and symbol-rate offset, and input power, along with whether the carrier is currently running ACM or CCM — which is the field that tells an operator a link has stepped down before the capacity change surfaces downstream. Two limits are worth knowing when specifying a monitoring regime: MER is not reported, and on multi-stream transponders signal quality is measured at carrier level rather than per ISI. Where either is required, that remains the province of dedicated RF test equipment.

Conditional access is handled at the same boundary: BISS-1 and BISS-2 descrambling on the demodulator, BISS scrambling on the modulator, applied to the transport stream and therefore unaffected by whether the onward path is RF or IP.

At a centralised earth station this is what makes transponder capacity permanently available on the IP network rather than tied to the site that owns the dish. Open JSON-RPC APIs across both the RF and IP modules allow the two monitoring domains to be pulled into a single operational view and failover to be automated across them.

The migration architecture this enables — moving from a distributed, site-based satellite model to centralised demodulation with IP distribution — is set out on the Satellite to IP migration page.

Frequently asked questions

How do I convert transponder bandwidth in MHz to usable bitrate?

Divide bandwidth by one plus the roll-off factor to get symbol rate, then multiply by bits per symbol for the modulation order and by the FEC rate. A 36 MHz transponder at 0.20 roll-off, 8PSK and FEC 3/4 gives approximately 67 Mbps.

What does the roll-off factor actually change?

How much spectrum a carrier occupies beyond its symbol rate. Lower roll-off fits more symbol rate into the same leased bandwidth. Moving from 0.35 to 0.20 releases roughly 11% more capacity with no change to modulation or coding.

Why does higher-order modulation need a better link?

Higher orders pack more bits into each symbol by using more closely spaced signal states, which requires a higher signal-to-noise ratio at the receiver to distinguish them reliably. Spectral efficiency is bought with link margin.

What is link margin and how much do I need?

The difference between the received signal-to-noise ratio and the threshold your modulation and coding requires. The amount needed is determined by your availability target, your location in the satellite footprint, and the frequency band’s rain-fade characteristics — not chosen directly.

Why is C-band still used when Ku and Ka offer more throughput?

C-band suffers far less rain attenuation, which makes it the practical choice for high-availability contribution and distribution in tropical and heavy-rainfall regions, despite requiring larger antennas.

What breaks when I introduce adaptive coding and modulation?

Capacity becomes variable rather than fixed. Any downstream design that assumes constant bitrate will fail during the first significant fade event. Handle it with statistical multiplexing across the service group or a defined degradation policy.

Is a satellite-recovered transport stream degraded?

No. Above threshold, the recovered stream is bit-identical to the transmitted one. Satellite links do not degrade gradually — they work, then fail sharply once margin is exhausted.

Why is geostationary latency around 300–600 ms?

Propagation alone is roughly 240 ms for the 35,786 km up-and-down path, with encoding, modulation and ground processing making up the rest. It is set by physics and cannot be tuned.

Does LEO solve the latency problem for broadcast?

It reduces propagation delay substantially, at the cost of tracking, handover and a different terminal and service model. Today it is viable for specific field-contribution use cases, generally bonded and paired with resilient transport, rather than as a replacement for leased GEO capacity in one-to-many distribution.

What changes at the demodulator output?

The transport stream gains an IP identity: encapsulation into TSoIP or SRT, addressing, protection and encryption. It also acquires packet delay variation that did not exist on the RF path, so downstream buffering must be sized for clean clock recovery.

Why do I need separate RF and IP monitoring?

They measure different things — Eb/No, MER, symbol lock and bit error rate on one side; packet loss, jitter, RTT and buffer occupancy on the other — and neither predicts the other. Hybrid operations need both correlated with failover triggers spanning the two domains.

When does satellite still make better commercial sense than IP?

For wide-footprint one-to-many distribution, where a single uplink reaches every receiver at no incremental cost per endpoint, and in regions where terrestrial networks are absent, unreliable or expensive to provision. It also remains valuable as a protection path with no shared failure mode with terrestrial networks.

Learn more

For the migration architecture and centralised earth-station model, see Satellite to IP migration. For the IP transport comparison this article deliberately omits, see Broadcast network modernisation for IP- and cloud-based live production. For SRT recovery-buffer tuning on the onward path, see SRT stream density and transport for broadcast contribution.

Guide
Plan your satellite to IP migration

Key challenges, benefits, and practical considerations for a smooth transition from satellite contribution and distribution.

Download the guide
Satellite to IP Migration guide cover
Related articles
View all articles
The future of live production, in your inbox.

Insight on contribution, distribution, and IP delivery—from the team building the infrastructure behind it.