SAT>IP URL Builder & T2MI Configuration
Complete Technical Reference

🎯Why URL Construction Matters

When you connect to a SATLINE.TV virtual tuner or any SAT>IP server, you're essentially sending instructions via a specially formatted URL. This URL contains all tuning parameters: frequency, polarization, symbol rate, modulation type, and advanced features like multistream ISI/PLS codes for DVB-S2X.

• Basic parameters: Frequency, polarization, symbol rate, FEC — enough for standard DVB-S/S2 transponders
• Advanced parameters: ISI (Input Stream Identifier), PLSC (Physical Layer Scrambling Code), PLS mode for multistream
• T2-MI parameters: T2MI PID and PLP ID for DVB-T2 encapsulated in DVB-S2 (satellite to terrestrial gateway)
• PID filtering: Request specific PIDs (channels) instead of the full transponder stream
• Duration control: Specify how long to scan/capture for channel discovery

Essential Parameters Explained

📋 Example: Basic SAT>IP URL

This URL tells the SAT>IP server at your-satip-server-ip to tune to 11727 MHz Vertical with 30000 KSym/s symbol rate, using DVB-S2 with 8PSK modulation and 3/4 FEC.

🔍Understanding FEC Notation

FEC (Forward Error Correction) values use a compact notation where two digits represent the numerator and denominator:

🎛️ISI (Input Stream Identifier)

The ISI parameter selects which stream you want to receive from a multistream transponder. Each stream has a unique ISI value from 0 to 255.

📊 Real-World Multistream Example: Eutelsat 5 West B 12.536 GHz H

This transponder carries multiple regional Italian streams on the same frequency:

• Stream 1 (ISI=1): RAI mux MR 5 — 7 channels (Rai 1 HD, Rai 2 HD, Rai 3 HD regional variants)
• Stream 4 (ISI=4): RAI mux MR 10 — 7 channels (different regional Rai 3 variants)
• Stream 9 (ISI=9): Puglia/Basilicata Locale 1 — 17 local channels (TeleNorba HD, TeleDue HD, etc.)

Total: 31+ channels on one frequency. To access Stream 9, you'd add &isi=9 to your SAT>IP URL.

🔗 Example URL with ISI:

🔐PLSC (Physical Layer Scrambling Code) & PLS Mode

Some multistream transponders use PLS codes instead of (or in addition to) ISI. The PLS system has three modes:

PLS Mode Types:

• Gold: Most common mode. PLSC range: 0-262143. Used by most modern multistream transponders.
• Root: Alternative mode. PLSC range: 0-262143. Less common but used by some operators.
• Combo: Combined mode allowing both gold and root codes.

🔗 Example URL with PLS:

🎯When Do You Need T2-MI Parameters?

T2-MI is used in specific scenarios:

• Satellite-to-terrestrial distribution: Broadcasters transmit DVB-T2 signals via satellite to regional terrestrial transmitters
• Terrestrial network feeds: Some satellites carry complete DVB-T2 multiplex data for rebroadcast
• Professional broadcast infrastructure: Telecom operators receiving T2 content for local terrestrial distribution

🔧T2-MI Parameters Explained

Those are the literal query-string spellings. Earlier revisions of this page named these parameters only in prose as “T2MI PID” and “T2MI PLP”, which is not what you type — the URL takes t2mi_pid and t2mi_plp.

🔍 Understanding T2-MI PID:

The T2MI PID (Packet Identifier) tells the tuner which PID in the satellite MPEG-TS stream contains the T2-MI encapsulated data. Think of it as pointing to the "container" that holds the DVB-T2 signal.

• Default: 4096 — Most T2-MI transponders use PID 4096
• Range: 4095-4099 — Some operators use alternative PIDs in this range
• Check satellite databases (LyngSat, KingOfSat) for specific transponder T2MI PID values

🔍 Understanding T2MI PLP:

The T2MI PLP (Physical Layer Pipe) is the DVB-T2 stream identifier within the T2-MI container. A single T2-MI stream can carry multiple PLPs (similar to how multistream works).

• PLP 0: Usually the main multiplex with primary channels
• PLP 1+: Additional multiplexes (e.g., regional variants, HD/SD splits)
• Typical usage: Most T2-MI transponders have only PLP 0

🔗 Example URL with T2-MI:

This URL requests T2-MI data from PID 4096, extracting PLP 0 (the primary DVB-T2 multiplex).

✅T2-MI is demultiplexed natively, on the fly — corrected 2026-08-05

SAT>IP Servers Pro runs the T2-MI demux itself, in real time as the stream passes through, and delivers the inner transport stream. Set t2mi_pid, and optionally t2mi_plp or t2mi_pids, and the inner DVB-T2 multiplex comes out of the server. There is no separate decapsulation stage, no extra hop and no store-and-forward buffering step between the tuner and your output — the demux sits inside the streaming path rather than alongside it.

An earlier version of this page said the opposite: that the server “does not perform T2-MI decapsulation” and that you “must decapsulate using external software or hardware”. That was wrong, and it contradicted our own T2-MI processing comparison, which correctly describes native handling. The workflow below is still useful for discovering what is inside a T2-MI carrier, but treat external decapsulators as an option for existing signal chains, not a requirement.

🔧 T2-MI Decapsulation Workflow

To work with T2-MI transponders on SATLINE.TV SAT>IP Server Pro, follow this professional workflow:

#EXTM3U
# Generated: 2025-11-18T17:22:16Z
# Source: http://your-satip-server-ip:8875/?freq=12226&msys=DVBS2&mtype=8psk&fec=56&isi=20&src=1&sr=30000&pol=V&pids=all
# Scanner: T2MI (PID=4096, PLP=0)

Srv Id  Service Name                              Access          Bitrate  |
|  0x0015  Новий канал .................................. C    2,145,803 b/s  |
|  0x0016   TET ......................................... C    2,694,486 b/s  |
|  0x0017   2+2 ......................................... C    2,666,440 b/s  |
|  0x0018  M-1 .......................................... C    1,980,959 b/s  |
|  0x0019  НТН .......................................... C    2,692,994 b/s  |
|  0x001A  Мега ......................................... C    1,395,130 b/s  |
|  0x001B   ПЛЮСПЛЮС .................................... C    1,717,507 b/s  |
|  0x001C  МИ-УKРАЇНА+ .................................. C    2,663,009 b/s  |
|  0x001D  ROZPAKUY ..................................... C    1,771,212 b/s  |
|  0x001E  ICTV2 ........................................ C    1,702,291 b/s  |
|  0x0034  ОЦЕ .......................................... C    2,269,920 b/s  |

📊 Why analyse first, then tune?

• You cannot request a pipe you have not identified: the analyzer returns the service list, PIDs and encryption status inside the container, which is what t2mi_pid and t2mi_plp then point at
• Flexibility: native demux for a clean deployment, or the outer stream if you have an existing decapsulator to feed
• Professional grade: The T2-MI Channels Analyzer provides complete metadata, bitrates, and encryption status for production planning
• Efficiency: Stream the full transponder once, then decapsulate multiple channels locally without additional SAT>IP tuner load

🧩Raw DVB-S2 BBFrame input mode (bbframe)

Some DVB-S2 multistream (MIS) transponders carry a bursty T2-MI feed that the demodulator’s hardware MIS→TS de-encapsulation drops — typically around 9% packet loss, which leaves the inner DVB-T2 multiplex undecodable with near-100% T2-MI CRC failures even though the RF is perfect. That combination is the tell: excellent signal quality, unusable output.

On STiD135-based tuners with the raw-bbframe driver patch, bbframe=1 tunes the adapter so the demodulator emits raw DVB-S2 BBFrames instead of de-encapsulating in hardware. SAT>IP Servers Pro then reconstructs the outer transport stream losslessly in software and feeds it to the normal t2mi_pid demux. It applies to HTTP, RTSP and SRT outputs alike.

📋 Example: RAI 4K over T2-MI with raw BBFrame reconstruction

Scenario: 5°W, 12606 MHz Vertical, DVB-S2 8PSK 2/3, 35300 KSym/s, roll-off 0.35, ISI 5, gold scrambling code 131070, T2-MI PID 4096, PLP 0.

Reading it as a pipeline: tune the multistream carrier (isi, plsm, plsc), take raw BBFrames rather than hardware de-encapsulation (bbframe=1), pass the whole stream through (pids=all), then extract the inner DVB-T2 multiplex (t2mi_pid, t2mi_plp).

If you are analysing this from a shell rather than a player, quote the URL — the ampersands are shell operators, and on bash an unquoted SAT>IP URL fails silently and wrongly. The TSDuck cookbook documents that trap with the verified before-and-after.

📐Sizing the Link for Your PID Request

Because PID selection is a runtime parameter you control rather than something applied upstream, bandwidth planning has to follow the request you actually intend to make. Sizing against the wrong one of these is a common and avoidable planning error:

• pids=all — budget the full multiplex bitrate of the transponder. The whole carrier crosses your link, because nothing is filtered on your behalf.
• Explicit PID list — budget the selected elementary streams plus PSI/SI overhead. Only what you asked for is transported, which is how a WAN path is kept from carrying services you would discard on arrival.

Use pids=all when analyzing a carrier, harvesting tables, or feeding a remultiplexer that expects the complete stream. Use an explicit list for production delivery of a known service set. The choice can be changed between sessions without altering the service, so it is worth measuring the real multiplex bitrate once and then selecting deliberately.

Example 1: Standard DVB-S2 Transponder

Scenario: Astra 19.2°E, 11.954 GHz Horizontal, 27500 KSym/s, DVB-S2 8PSK 3/4

Example 2: Multistream Transponder with ISI

Scenario: Eutelsat 5W, 12.536 GHz Horizontal, 35300 KSym/s, DVB-S2 8PSK 2/3, ISI=9

Example 3: Multistream with PLS Gold Code

Scenario: Hotbird 13°E, 11.470 GHz Vertical, 27500 KSym/s, DVB-S2 8PSK 3/4, PLS Gold 131070

Example 4: T2-MI Transponder

Scenario: T2-MI encapsulated DVB-T2, 11.727 GHz Vertical, 30000 KSym/s, DVB-S2 8PSK 3/4, T2MI PID 4096, PLP 0

Example 5: PID Filtered with Duration (Channel Scan)

Scenario: Scan Astra 19.2°E transponder for 15 seconds, capturing metadata only

Example 6: Complete Professional Configuration

Scenario: All advanced parameters combined (multistream + T2MI + PID filtering + duration)

🎯 For IPTV Operators & System Integrators

• Document your URLs: Maintain a spreadsheet of working SAT>IP URLs for each transponder
• Use descriptive naming: Label URLs by satellite position + frequency (e.g., "Astra192E-11954H")
• Test URLs in VLC first: Quick validation before deploying to production middleware
• Monitor signal quality: Set up alerts in SATLINE.TV admin panel for SNR drops
• Plan for multistream: When selecting transponders, prefer multistream for bandwidth efficiency
• Regular rescans: Broadcasters change parameters — schedule monthly transponder rescans
• Backup tuners: For mission-critical channels, provision redundant locked tuners

🔍 For Channel Discovery & Research

• Use adequate duration: 15-20 seconds ensures complete PSI/SI table capture
• Capture all PIDs initially: pids=all for first scan, then filter later
• Check multiple ISI values: Try ISI 0-15 if databases don't list correct value
• Log your findings: Contribute to satellite databases (LyngSat forums)
• Watch for updates: Satellites launch new transponders monthly — stay informed

🎓 SATLINE.TV Support

Need help with complex SAT>IP URL construction or T2-MI configuration? SATLINE.TV provides comprehensive support:

• Admin Panel SAT>IP Scanner: Auto-generates correct URLs for any transponder
• Live Monitoring Dashboard: Real-time signal quality metrics to diagnose issues
• Technical Documentation: Detailed guides for TVHeadend, Cesbo Astra, Enigma2 integration
• Email Support: Expert assistance for multistream and T2-MI configurations