What is Adaptive Bitrate Streaming (ABR)?
Protocol Definition & Architecture: Developer Api Reference
Technical Definition
ABR encodes each channel into a ladder of renditions (e.g. 2160p 18.5 Mbps, 1080p 8.5 Mbps, 720p 4.5 Mbps, 480p 2 Mbps) and lets the player switch rendition per segment based on measured throughput and buffer level.
How It Operates Under the Hood
Throughput-based algorithms pick the highest rendition below recent bandwidth; buffer-based algorithms (BOLA) pick based on seconds buffered. Players begin on a mid rung for fast start and ramp up after three stable segments. ABR applies to HLS and DASH; raw .ts output is single-bitrate.
Developer Reference
Developers integrating Adaptive Bitrate Streaming (ABR) should follow the governing standards cited below, use the Xtream Codes JSON endpoints for discovery, and respect RFC 3986 URI encoding for credentials. Device login flows on TVs should implement the RFC 8628 device-code pattern.
Protocol Engineering Specifications
| Stream Engineering Metric | Reference Specification | Governing Standard |
|---|---|---|
| Ladder rungs | 4-6 |
Master playlist |
| Switch granularity | Per segment (4 s) |
Client decision |
| Startup rendition | 720p |
Fast start |
| Transport Container | MPEG-TS (188 bytes: 4 B header + 184 B payload, 0x47 sync) |
ISO/IEC 13818-1 |
| Manifest Specification | Extended M3U8 playlist / LL-HLS 0.5 s parts |
IETF RFC 8216 |
| Decoder Pipeline | Hardware MediaCodec HEVC Main 10 (ExoPlayer / Media3) |
Android Media3 |
Client buffer time is the allocated buffer memory converted to bits, divided by the stream bitrate. Drag the sliders to see how much protection a given allocation gives against ISP shaping bursts:
A 15 MB allocation on an 18.5 Mbps 4K feed yields 6.49 seconds of reserve, enough to absorb a 2-4 second ISP shaping burst without a visible freeze.
Adaptive Bitrate Streaming (ABR) FAQ
What is Adaptive Bitrate Streaming (ABR) in simple terms?
ABR encodes each channel into a ladder of renditions (e.g. 2160p 18.5 Mbps, 1080p 8.5 Mbps, 720p 4.5 Mbps, 480p 2 Mbps) and lets the player switch rendition per segment based on measured throughput and buffer level.
Why does the quality drop during a match?
Shaped throughput pushes the ABR algorithm to a lower rung; a WireGuard tunnel restores bandwidth and the player climbs back.
What is the difference between Xtream Codes API, M3U URL, and Stalker Portal login?
All three deliver the same channels. Xtream Codes API uses player_api.php JSON endpoints so the player lazy-loads categories and EPG in seconds. An M3U URL (get.php) downloads a single text playlist of every stream, which is slow with 45,000 channels but works on any player. Stalker Portal authenticates by MAC address through a /c/ portal URL and is used by MAG receivers and some Smart TV apps.
Why is my EPG guide empty or showing programs at the wrong time?
Players fetch an XMLTV file from xmltv.php and match each channel by tvg-id. An empty guide means the player downloaded the file before the server finished its 15-minute refresh or the file exceeded the player size cap (set TiviMate EPG update to "never limit"). Wrong times are a timezone offset issue: XMLTV timestamps carry +0000 and the player must apply your local offset, so set an EPG shift of +1 or -5 hours in the channel settings rather than changing the device clock.
What is device MAC address binding and why does my MAG box or Smart TV app ask for it?
Stalker / Ministra middleware authenticates a set-top box by its 48-bit MAC address (MAG boxes use the 00:1A:79 OUI prefix) instead of a username and password. The reseller panel binds that MAC to a subscription line; apps such as IBO Player and Smarters on Samsung or LG TVs generate a virtual MAC that must be registered the same way. If you replace the device, the panel must re-bind the new MAC or the portal returns an "unregistered device" error.
How does multi-screen concurrency work and what happens if I exceed max_connections?
The Xtream Codes player_api.php handshake returns max_connections and active_cons. Each live or VOD stream request opens one session counted against that limit; a second TV, phone, or multi-view tile is a second connection. When active_cons would exceed max_connections, the server answers the new stream request with HTTP 403 / 458 and the player shows "max connections reached". Resellers should sell lines with 2-5 connections for households and enable IP-lock only for single-device subscribers.
How far behind live are IPTV sports streams and can latency be reduced?
Standard HLS with 4-second segments and a 3-segment player window sits 12-18 seconds behind the broadcast. Low-Latency HLS with 0.5-second partial segments brings glass-to-glass delay to about 3.8 seconds, and raw MPEG-TS over HTTP (.ts output format) is typically 5-7 seconds behind. Choose the .ts output format in your player for live sports and reserve .m3u8 for VOD and catch-up.
Every external citation on this page points to a primary source: telecommunications RFCs, ITU-T and ISO codec standards, manufacturer and developer documentation, national regulators, or official sports governing bodies. No commercial IPTV competitor is cited.