Documentation
DVB Standards & C/N Reference
A reference for DVB-S2 and DVB-S2X link planning: ideal Es/N0 thresholds for each MODCOD from the ETSI standards, the difference between Es/N0, Eb/N0 and C/N, bitrate and bandwidth calculations, and the margins to add for real-world links.
- 2026-10-09 12:11
- 2026-10-13 12:12
- MODCOD tables
- C/N vs Es/N0 vs Eb/N0
- Symbol rate & bandwidth
- Standards family
- Margin
Get This Right First
Three ratios, routinely swapped
They differ by real decibels. Quoting the wrong one sizes the wrong dish.
Es/N0 — per symbol. What the tables give
Eb/N0 — per information bit
C/N — carrier over noise in a stated bandwidth
- S2 modes28EN 302 307-1 Table 13
- S2X floor−9,9dB, π/2 BPSK-S 1/5
1. Scope and sources
Every figure on this page was read from the published standard, not from a secondary table. The two documents that matter are ETSI EN 302 307-1 V1.4.1 (2014-11) for DVB-S2 and ETSI EN 302 307-2 V1.4.1 (2024-08) for DVB-S2X. Both were downloaded from the ETSI portal and parsed directly; the version numbers were confirmed against the ETSI directory rather than assumed.
What this page deliberately does not contain: DVB-T2 C/N figures. Reasonable to expect them here, and they are genuinely useful — but they are not in EN 302 755, the DVB-T2 standard. That document specifies the system without stating required C/N per mode; the performance figures live in the DVB-T2 implementation guidelines, which could not be retrieved while preparing this sheet. Rather than reproduce numbers from a secondary source and present them with the same authority as the satellite tables, section 9 says where they live and stops there. The DVB-T2 structural parameters below are from EN 302 755.
Terrestrial and cable C/N thresholds also depend far more on channel model than satellite ones do. A satellite link is close to AWGN; a terrestrial one is a multipath channel where the required C/N for the same modulation and code rate can differ by several decibels between a fixed-roof and a portable-indoor reception model. A single number per mode is meaningful for satellite in a way it is not for terrestrial.
2. Es/N0, Eb/N0 and C/N — the distinction that costs money
These three are used interchangeably in conversation and are not interchangeable in arithmetic. Confusing them is the most common way a link budget comes out wrong by two or three decibels, which at Ku band is the difference between two antenna sizes.
| Ratio | Normalised per | Where it appears |
|---|---|---|
| Es/N0 | Transmitted symbol | What the DVB-S2 and S2X tables give. Independent of code rate, because the code rate is already reflected in which row you are reading |
| Eb/N0 | Information bit | Standard in communications theory. Lets you compare schemes of different spectral efficiency on equal footing |
| C/N | A stated bandwidth | What a receiver reports and what a link budget produces. Meaningless without knowing the bandwidth |
The conversion between the first two is given in the note under Table 13 itself:
Eb/N0 = Es/N0 − 10·log₁₀(ηtot)where ηtot is the spectral efficiency in bits per symbol. The sign matters and catches people out. For a high-efficiency mode η > 1, so Eb/N0 is lower than Es/N0. For a strong low-rate code η < 1 and Eb/N0 is higher. Worked from the table’s own numbers:
| Mode | η (bit/symbol) | Es/N0 (dB) | 10·log₁₀(η) | Eb/N0 (dB) |
|---|---|---|---|---|
| QPSK 1/4 | 0,490243 | −2,35 | −3,10 | +0,75 |
| QPSK 3/4 | 1,487473 | 4,03 | 1,72 | 2,31 |
| 8PSK 2/3 | 1,980636 | 6,62 | 2,97 | 3,65 |
| 16APSK 3/4 | 2,966728 | 10,21 | 4,72 | 5,49 |
| 32APSK 5/6 | 4,119540 | 14,28 | 6,15 | 8,13 |
QPSK 1/4 is the instructive row: a negative Es/N0 of −2,35 dB and a positive Eb/N0 of +0,75 dB describe the same link. The carrier really can sit below the noise floor and still be decoded, because each information bit is spread across more than two symbols. Anyone who says “you cannot receive a signal below the noise floor” is thinking in Eb/N0 while reading an Es/N0 number.
For C/N, the relationship to Es/N0 depends on the bandwidth you measure in. Measured in a bandwidth equal to the symbol rate, C/N and Es/N0 are numerically the same. Measured in the occupied bandwidth — symbol rate times one plus roll-off — C/N is lower by 10·log₁₀(1 + α):
| Roll-off α | 10·log₁₀(1 + α) | Meaning |
|---|---|---|
| 0,35 | 1,30 dB | DVB-S2 default, inherited from DVB-S |
| 0,25 | 0,97 dB | DVB-S2 option |
| 0,20 | 0,79 dB | DVB-S2 option |
| 0,15 | 0,61 dB | DVB-S2X addition |
| 0,10 | 0,41 dB | DVB-S2X addition |
| 0,05 | 0,21 dB | DVB-S2X addition |
So “C/N = 7 dB” is not a complete statement. In symbol-rate bandwidth it means Es/N0 = 7 dB, comfortably above 8PSK 2/3. In occupied bandwidth at α = 0,35 the same measurement means Es/N0 = 8,3 dB. Whenever a datasheet or a receiver quotes C/N, establish the reference bandwidth before comparing it with any table on this page.
3. What “works” means — the QEF definition
Every threshold on this page is the point at which the system reaches Quasi-Error-Free operation. That phrase has a precise definition in EN 302 307-1, and it is not “no errors”:
QEF for DVB-S2: “less than one uncorrected error-event per transmission hour at the level of a 5 Mbit/s single TV service decoder”, corresponding approximately to a transport stream Packet Error Ratio below 10⁻⁷ before the demultiplexer.
Two consequences that matter operationally. First, the target is tied to a 5 Mbit/s service — a higher-bitrate service passes more packets per hour, so the same PER produces more error events. Second, QEF is a threshold with a cliff below it: LDPC coding means performance does not degrade gracefully. A link half a decibel above threshold is perfect; half a decibel below it fails almost completely. There is very little of the gradual picture degradation that analogue and even DVB-S exhibited.
DVB-S2X changed the metric. The S2X tables are specified at FER = 10⁻⁵ — Frame Error Ratio, the proportion of FECFRAMEs received in error — not the PER = 10⁻⁷ used for S2. These are different quantities measured on different objects, so S2 and S2X threshold figures are not strictly comparable at the third decimal place. For engineering purposes they are close enough to tabulate together, which is what section 5 does, but a specification document comparing them should say which metric it means.
4. Why these are “ideal” figures, and what to add
This is the caveat that most reproductions of these tables drop, and it is the difference between a table and a link budget. EN 302 307-1 states the conditions under which its numbers were obtained:
| Condition assumed | Reality |
|---|---|
| Figures from computer simulation | Not measured on hardware |
| 50 LDPC fixed-point decoding iterations | A receiver that stops earlier to save power performs worse |
| Perfect carrier and synchronisation recovery | Real demodulators lose a fraction of a decibel acquiring and tracking |
| No phase noise | Every real LNB and receiver contributes phase noise, and higher-order APSK is far more sensitive to it |
| AWGN channel | Real links add rain fade, interference, and transponder non-linearity |
| Normal FECFRAME (64 800 bits), no pilots | Short FECFRAMEs cost 0,2 to 0,3 dB more, per the standard |
The standard is explicit about the conclusion: “For calculating link budgets, specific satellite channel impairments should be taken into account.” In other words the table gives you a floor, and the implementation margin plus channel impairments plus rain fade allowance sit on top of it. Treating an ideal Es/N0 as a design threshold produces a link that works in clear sky and fails on the first weather event.
How close is this to theory, and how close is it usually claimed to be? EN 302 307-1’s introduction says DVB-S2 allows QEF operation “at about 0,7 dB to 1 dB from the Shannon limit”. That figure is the gap from the constellation-constrained capacity — the best achievable with that specific constellation. Measured against unconstrained Gaussian capacity, the gap is larger: computing 10·log₁₀(2η − 1) from the table’s own spectral efficiencies gives 1,07 dB for QPSK 1/2, 1,93 dB for 8PSK 2/3, 2,14 dB for 32APSK 5/6 and 2,85 dB for 32APSK 9/10. Both statements are correct about different quantities. Neither is a reason to expect a real receiver to hit the table.
5. DVB-S2 — the complete Table 13
All 28 modes, transcribed from EN 302 307-1 V1.4.1 Table 13. Es/N0 at QEF, PER = 10⁻⁷, AWGN, FECFRAME length 64 800, no pilots. Decimal commas are as printed in the standard.
| Mode | Spectral efficiency (bit/symbol) | Ideal Es/N0 (dB) |
|---|---|---|
| QPSK 1/4 | 0,490243 | −2,35 |
| QPSK 1/3 | 0,656448 | −1,24 |
| QPSK 2/5 | 0,789412 | −0,30 |
| QPSK 1/2 | 0,988858 | 1,00 |
| QPSK 3/5 | 1,188304 | 2,23 |
| QPSK 2/3 | 1,322253 | 3,10 |
| QPSK 3/4 | 1,487473 | 4,03 |
| QPSK 4/5 | 1,587196 | 4,68 |
| QPSK 5/6 | 1,654663 | 5,18 |
| QPSK 8/9 | 1,766451 | 6,20 |
| QPSK 9/10 | 1,788612 | 6,42 |
| 8PSK 3/5 | 1,779991 | 5,50 |
| 8PSK 2/3 | 1,980636 | 6,62 |
| 8PSK 3/4 | 2,228124 | 7,91 |
| 8PSK 5/6 | 2,478562 | 9,35 |
| 8PSK 8/9 | 2,646012 | 10,69 |
| 8PSK 9/10 | 2,679207 | 10,98 |
| 16APSK 2/3 | 2,637201 | 8,97 |
| 16APSK 3/4 | 2,966728 | 10,21 |
| 16APSK 4/5 | 3,165623 | 11,03 |
| 16APSK 5/6 | 3,300184 | 11,61 |
| 16APSK 8/9 | 3,523143 | 12,89 |
| 16APSK 9/10 | 3,567342 | 13,13 |
| 32APSK 3/4 | 3,703295 | 12,73 |
| 32APSK 4/5 | 3,951571 | 13,64 |
| 32APSK 5/6 | 4,119540 | 14,28 |
| 32APSK 8/9 | 4,397854 | 15,69 |
| 32APSK 9/10 | 4,453027 | 16,05 |
Read the overlaps — they are where the engineering decisions live. 8PSK 3/5 needs 5,50 dB for 1,780 bit/symbol, while QPSK 9/10 needs 6,42 dB for almost exactly the same 1,789 bit/symbol. The 8PSK mode delivers the same throughput at nearly a decibel less C/N. Similarly 16APSK 2/3 (8,97 dB, 2,637 bit/symbol) beats 8PSK 8/9 (10,69 dB, 2,646 bit/symbol) by 1,7 dB at equal efficiency. A higher-order constellation with a stronger code frequently outperforms a lower-order one straining at 9/10 — so “lower modulation order is more robust” is only true at equal code rate, which is rarely the comparison anyone actually faces.
6. DVB-S2X — the extended modes
From EN 302 307-2 V1.4.1 Table 20a. Es/N0 at QEF, FER = 10⁻⁵, normal FECFRAMEs, 50 iterations. The second figure is the informative non-linear hard-limiter channel result — the same mode through a saturated transponder, at optimised input back-off and 10 % roll-off.
| MODCOD | η (bit/symbol) | Es/N0 linear AWGN (dB) | Csat/(N0·Rs) non-linear (dB) |
|---|---|---|---|
| QPSK 2/9 | 0,434841 | −2,85 | −2,45 |
| QPSK 13/45 | 0,567805 | −2,03 | −1,60 |
| QPSK 9/20 | 0,889135 | 0,22 | 0,69 |
| QPSK 11/20 | 1,088581 | 1,45 | 1,97 |
| 8APSK 5/9-L | 1,647211 | 4,73 | 5,95 |
| 8APSK 26/45-L | 1,713601 | 5,13 | 6,35 |
| 8PSK 23/36 | 1,896173 | 6,12 | 6,96 |
| 8PSK 25/36 | 2,062148 | 7,02 | 7,93 |
| 8PSK 13/18 | 2,145136 | 7,49 | 8,42 |
| 16APSK 1/2-L | 1,972253 | 5,97 | 8,4 |
| 16APSK 8/15-L | 2,104850 | 6,55 | 9,0 |
| 16APSK 5/9-L | 2,193247 | 6,84 | 9,35 |
| 16APSK 26/45 | 2,281645 | 7,51 | 9,17 |
| 16APSK 3/5 | 2,370043 | 7,80 | 9,38 |
| 16APSK 3/5-L | 2,370043 | 7,41 | 9,94 |
| 16APSK 28/45 | 2,458441 | 8,10 | 9,76 |
| 16APSK 23/36 | 2,524739 | 8,38 | 10,04 |
| 16APSK 2/3-L | 2,635236 | 8,43 | 11,06 |
| 16APSK 25/36 | 2,745734 | 9,27 | 11,04 |
| 16APSK 13/18 | 2,856231 | 9,71 | 11,52 |
| 16APSK 7/9 | 3,077225 | 10,65 | 12,50 |
| 16APSK 77/90 | 3,386618 | 11,99 | 14,00 |
| 32APSK 2/3-L | 3,291954 | 11,10 | 13,81 |
| 32APSK 32/45 | 3,510192 | 11,75 | 14,50 |
| 32APSK 11/15 | 3,620536 | 12,17 | 14,91 |
| 32APSK 7/9 | 3,841226 | 13,05 | 15,84 |
| 64APSK 32/45-L | 4,206428 | 13,98 | 17,7 |
| 64APSK 11/15 | 4,338659 | 14,81 | 17,97 |
| 64APSK 7/9 | 4,603122 | 15,47 | 19,10 |
| 64APSK 4/5 | 4,735354 | 15,87 | 19,54 |
| 64APSK 5/6 | 4,936639 | 16,55 | 20,44 |
| 128APSK 3/4 | 5,163248 | 17,73 | 21,43 |
| 128APSK 7/9 | 5,355556 | 18,53 | 22,21 |
| 256APSK 29/45-L | 5,065690 | 16,98 | 21,6 |
| 256APSK 2/3-L | 5,241514 | 17,24 | 21,89 |
| 256APSK 31/45-L | 5,417338 | 18,10 | 22,9 |
| 256APSK 32/45 | 5,593162 | 18,59 | 22,91 |
| 256APSK 11/15-L | 5,768987 | 18,84 | 23,80 |
| 256APSK 3/4 | 5,900855 | 19,57 | 24,02 |
Three things to read out of this table:
- The
-Lsuffix means linear.Those MODCODs use constellations optimised for a linear channel. Compare 16APSK 3/5 and 16APSK 3/5-L: identical spectral efficiency, but the linear variant needs 0,39 dB less on a linear channel and 0,56 dB more through a hard limiter. The choice depends on whether your transponder runs near saturation. - The non-linear penalty grows with constellation order.QPSK 2/9 loses 0,4 dB through the hard limiter; 16APSK 1/2-L loses 2,4 dB; 256APSK 3/4 loses 4,45 dB. Amplitude-modulated constellations suffer when the amplifier compresses, which is why high-order APSK belongs on a lightly-loaded transponder or a linearised chain.
- The finer code-rate granularity is the practical gain.S2 jumps from 8PSK 2/3 (6,62 dB) to 8PSK 3/4 (7,91 dB) — a 1,3 dB gap you must either waste or fall through. S2X fills it with 8PSK 23/36, 25/36 and 13/18 at 6,12, 7,02 and 7,49 dB. On a link that varies with weather, that granularity converts directly into available hours.
7. Very Low SNR modes
S2X adds modes for links that DVB-S2 simply cannot close, using π/2 BPSK and very low code rates. From Tables 20b and 20c of EN 302 307-2 V1.4.1, at FER = 10⁻⁵:
| MODCOD | FECFRAME length | Ideal Es/N0 (dB) |
|---|---|---|
| π/2 BPSK-S 1/5 | 15 390 | −9,9 |
| π/2 BPSK-S 11/45 | 15 390 | −8,3 |
| π/2 BPSK 1/5 | 30 780 (medium) | −6,85 |
| π/2 BPSK 1/5 | 14 976 | −6,1 |
| π/2 BPSK 11/45 | 30 780 (medium) | −5,50 |
| π/2 BPSK 4/15 | 14 976 | −4,9 |
| π/2 BPSK 1/3 | 30 780 (medium) | −4,00 |
| π/2 BPSK 1/3 | 16 200 | −3,72 |
The medium and short XFECFRAME tables use 75 decoding iterations rather than 50 for the BPSK modes — more decoder work traded for threshold. At −9,9 dB the carrier is nearly ten decibels below the noise, which is what makes very small terminals, deep rain fade operation and emergency links feasible at all.
Why the frame length appears in this table and not the S2 one. S2X defines several FECFRAME lengths — normal 64 800, medium 30 780, short 16 200, and the odd lengths 15 390 and 14 976 for specific BPSK modes — and the threshold depends on which is used, because a longer code performs closer to capacity. When someone quotes a VL-SNR figure, the frame length is part of the specification, not an implementation detail.
8. From symbol rate to bitrate and bandwidth
Two relationships turn a MODCOD into the numbers you actually need. Both come straight from the table’s own definitions.
Useful bitrate = Rs × η (η from the spectral efficiency column)
Occupied bandwidth = Rs × (1 + α) (α = roll-off factor)Worked examples, computed from the table values above:
| MODCOD | Rs (Msym/s) | α | Occupied BW (MHz) | Useful bitrate (Mb/s) | Ideal Es/N0 (dB) |
|---|---|---|---|---|---|
| 8PSK 2/3 | 35,3 | 0,20 | 42,36 | 69,92 | 6,62 |
| 8PSK 2/3 | 30,0 | 0,20 | 36,00 | 59,42 | 6,62 |
| QPSK 3/4 | 27,5 | 0,35 | 37,12 | 40,91 | 4,03 |
| 16APSK 3/4 | 30,0 | 0,15 | 34,50 | 89,00 | 10,21 |
| 32APSK 5/6 | 33,0 | 0,10 | 36,30 | 135,94 | 14,28 |
| QPSK 1/4 | 5,0 | 0,35 | 6,75 | 2,45 | −2,35 |
The first row is a real transponder configuration referenced elsewhere on this site — 35 300 ksym/s, FEC 2/3, DVB-S2 8PSK — which works out to roughly 70 Mb/s of usable transport stream in about 42 MHz, needing at least 6,62 dB before any margin. The last row is the same arithmetic at the other extreme: a narrow 5 Msym/s carrier delivering 2,45 Mb/s but closing at −2,35 dB.
Two caveats on the spectral efficiency column. First, the values are computed for no pilots; enabling pilot symbols for easier carrier recovery reduces useful throughput. Second, they are normalised to a bandwidth equal to the symbol rate. To express efficiency per unit of occupied bandwidth, EN 302 307-2 says explicitly to divide by (1 + roll-off) — so 32APSK 5/6 at α = 0,10 gives 4,1195 / 1,10 = 3,745 bit/s/Hz of occupied spectrum, not 4,12.
The bitrate figure is the transport stream rate, which is what you compare against the numbers tsbitrate reports. If a measured stream rate does not match the arithmetic above, either the symbol rate, the code rate, or the pilot setting is not what you were told.
9. The standards family
Every version below was confirmed against the ETSI portal while preparing this sheet. Where a standard is old, that is because it is stable, not because it is superseded — DVB-S from 1997 still carries services today.
| System | Standard | Version confirmed | Notes |
|---|---|---|---|
| DVB-S | ETSI EN 300 421 | V1.1.2 (1997-08) | QPSK only, convolutional plus Reed-Solomon coding, roll-off fixed at 0,35 |
| DVB-S2 | ETSI EN 302 307-1 | V1.4.1 (2014-11) | LDPC plus BCH, QPSK to 32APSK, roll-off 0,35/0,25/0,20. Source of section 5 |
| DVB-S2X | ETSI EN 302 307-2 | V1.4.1 (2024-08) | Adds 8APSK, 64/128/256APSK, π/2 BPSK VL-SNR, finer code rates, roll-off down to 0,05, beam hopping. Sections 6 and 7 |
| DVB-T | ETSI EN 300 744 | V1.6.2 (2015-10) | OFDM, QPSK to 64-QAM, 2K and 8K FFT |
| DVB-T2 | ETSI EN 302 755 | V1.4.1 (2015-07) | Structural parameters in the next table. Contains no required-C/N table |
| DVB-C | ETSI EN 300 429 | V1.1.2 (1997-08) | Single-carrier QAM, 16 to 256-QAM, Reed-Solomon |
| DVB-C2 | ETSI EN 302 769 | — | OFDM with LDPC, up to 4096-QAM. Little deployed |
| T2-MI | ETSI TS 102 773 | V1.4.1 (2016-03) | Modulator interface. See the MPEG-TS sheet |
| Video and audio codecs | ETSI TS 101 154 | V2.10.1 | Which codecs may ride in the container |
| Service information | ETSI EN 300 468 | V1.19.1 (2025-02) | See the PSI/SI sheet |
| Measurement guidelines | ETSI TR 101 290 | V1.4.1 | See the DVB errors sheet |
| Conditional access | ETSI TS 103 197 | V1.5.1 (2008-10) | See the CA sheet |
| Adaptive streaming | ETSI TS 103 285 | — | DVB-DASH. Uses ISOBMFF and CMAF, not transport stream |
9.1 DVB-T2 structural parameters
From EN 302 755 V1.4.1. These are specified values, unlike the C/N thresholds:
| Parameter | Values |
|---|---|
| FFT sizes | 1K, 2K, 4K, 8K, 16K, 32K |
| Guard intervals | 1/128, 19/256, 19/128 (with the larger FFTs) and 1/32, 1/16, 1/8, 1/4 |
| Constellations | QPSK, 16-QAM, 64-QAM, 256-QAM |
| Constellation rotation | Available, but not used with 256-QAM in the T2-Lite profile |
| Multiple services | Physical Layer Pipes (PLPs), each independently modulated and coded |
| Transmit diversity | MISO using a modified Alamouti scheme, with pilot modification |
Where DVB-T2 C/N figures live. Not in EN 302 755. The required C/N per mode is published in the DVB-T2 implementation guidelines, and unlike the satellite case a single figure per mode is not very meaningful: the same modulation and code rate can differ by several decibels depending on whether the channel model is fixed rooftop, portable outdoor or portable indoor. Ask which channel model any quoted DVB-T2 C/N figure assumes; if the answer is not available, the figure is not comparable to anything.
10. Margin — what to add to a table figure
The tables give an ideal threshold. A design threshold is that plus everything the simulation excluded. The components are well known even though their magnitudes are installation-specific, and the honest position is to measure them rather than assume a rule of thumb.
| Component | Why it applies |
|---|---|
| Implementation margin | Real demodulator versus ideal simulation: imperfect carrier recovery, finite decoder iterations, quantisation. Comes from the receiver’s datasheet, not from a standard |
| Phase noise | LNB and receiver oscillators. Roughly negligible for QPSK, significant for 32APSK and above |
| Short FECFRAME penalty | 0,2 to 0,3 dB — this one is quantified, by EN 302 307-1 itself |
| Pilot overhead | Pilots ease carrier recovery but reduce useful throughput; the table’s efficiencies assume none |
| Transponder non-linearity | Quantified for S2X in the hard-limiter column of section 6 — up to 4,45 dB for 256APSK 3/4 |
| Adjacent channel and co-channel interference | Raises the effective noise floor. The standard’s threshold is against C/N+I, not C/N alone |
| Rain fade allowance | Frequency, geography and availability target dependent. The largest term at Ka band and often the dominant one at Ku |
| Antenna pointing and polarisation error | Installation quality. Small, but it does not improve over time |
Why a generous margin is not simply “safer”. Margin is bought with bandwidth. Choosing a mode 3 dB more robust than necessary means accepting materially lower spectral efficiency for the same transponder — 8PSK 2/3 rather than 16APSK 3/4 costs roughly a third of the capacity. The engineering question is not “how much margin can I add” but “what availability do I need, and what is the cheapest mode that delivers it”. That is a decision about the service, not about the modulation.
For a service where continuity matters more than efficiency, there is a structural alternative to buying margin in decibels: receive the same transponder at more than one site and fail over between them. That trades RF margin for geographic diversity, which addresses rain fade — a local phenomenon — in a way that no amount of coding gain at a single site can. The TSDuck cookbook covers the mechanics with tsswitch, and the tuner sheet covers how the sources differ.
11. Standards
| Specification | Role here |
|---|---|
| ETSI EN 302 307-1 V1.4.1 (2014-11) | DVB-S2. Downloaded and parsed. Source of Table 13 in section 5, the QEF definition in section 3, the ideal-conditions caveats in section 4, the Eb/N0 relation in section 2, and the roll-off options |
| ETSI EN 302 307-2 V1.4.1 (2024-08) | DVB-S2X. Downloaded and parsed. Source of Table 20a in section 6, Tables 20b and 20c in section 7, the additional roll-off factors, and the bandwidth-normalisation note in section 8 |
| ETSI EN 302 755 V1.4.1 (2015-07) | DVB-T2. Downloaded; source of the structural parameters in 9.1, and the basis for stating that it contains no required-C/N table |
| ETSI EN 300 421, EN 300 429, EN 300 744 | DVB-S, DVB-C, DVB-T. Versions confirmed against the ETSI portal for the family table |
| ETSI TR 102 376 | DVB-S2 implementation guidelines, referenced by EN 302 307-1 for the LDPC decoding assumptions |
12. Sources
[1] ETSI Standards portal, https://www.etsi.org/standards, retrieved 5 August 2026. Source for EN 302 307-1, EN 302 307-2, EN 302 755 and the rest of the standards family.
[2] DVB Project, https://dvb.org/, retrieved 5 August 2026. Source for the DVB specification index and status.
[3] MPEG Transport Stream Explained, Satline technical sheet, https://docs.satline.tv/satline-Technical-Sheets/in-depth/mpeg-transport-stream-explained.html, retrieved 5 August 2026. Covers the container these carriers deliver.
[4] The TSDuck Cookbook, Satline technical sheet, https://docs.satline.tv/satline-Technical-Sheets/in-depth/tsduck-cookbook.html, retrieved 5 August 2026. Covers measuring the bitrate this page predicts.
[5] Locked vs Unlocked SAT>IP Virtual Tuners, Satline technical sheet, https://docs.satline.tv/satline-Technical-Sheets/in-depth/locked-unlocked-virtual-tuners.html, retrieved 5 August 2026.
[6] SATLINE.TV Virtual SAT>IP Servers, https://satline.tv/virtual-sat-ip-servers/, retrieved 5 August 2026.
Gleb Sazanov
Chief Technology Officer
Gleb Sazanov is an accomplished Chief Technology Officer (CTO) with over 20 years of experience in software development, system architecture, and cloud-based solutions. As the CTO of SATLINE, a leading provider of virtual and colocation services tailored to SATCOM businesses, Gleb drives the company’s technological strategy, fostering innovation and efficiency in data center services. His expertise spans various domains, including DevOps, system scaling, and high-performance infrastructure management. With a deep passion for cutting-edge technologies, Gleb plays a pivotal role in shaping the future of the SATCOM industry.