What is RTMP vs HLS Latency?
Protocol Definition & Architecture: How It Works In Iptv
Technical Definition
RTMP is a persistent TCP streaming protocol with 2-5 seconds of latency, used for encoder ingest; HLS is segment-based HTTP delivery with 12-18 seconds of standard latency or 3-4 seconds in Low-Latency mode. IPTV uses RTMP (or SRT) for ingest and HLS or raw MPEG-TS for delivery.
How It Operates Under the Hood
RTMP streams are chunked at the message level with no segment boundaries, so latency equals encoder plus network delay. HLS must finish a segment before publishing it and the player buffers several segments, so latency is a multiple of the segment duration.
Role in the IPTV Delivery Chain
Within a panel, RTMP vs HLS Latency sits between the ingest / transcoding cluster and the subscriber player. Edge nodes implement it, the Xtream Codes API exposes its parameters, and player applications such as TiviMate and IPTV Smarters consume it.
Protocol Engineering Specifications
| Stream Engineering Metric | Reference Specification | Governing Standard |
|---|---|---|
| RTMP latency | 2-5 s |
TCP 1935 |
| HLS latency | 12-18 s / 3.8 s LL-HLS |
RFC 8216 |
| MPEG-TS over HTTP | 5-7 s |
.ts output |
| 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 |
RTMP vs HLS Latency FAQ
What is RTMP vs HLS Latency in simple terms?
RTMP is a persistent TCP streaming protocol with 2-5 seconds of latency, used for encoder ingest; HLS is segment-based HTTP delivery with 12-18 seconds of standard latency or 3-4 seconds in Low-Latency mode. IPTV uses RTMP (or SRT) for ingest and HLS or raw MPEG-TS for delivery.
Can I watch RTMP directly?
Most TV players do not support RTMP playback; use the .ts output for the lowest consumer latency.
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.
What buffer size should I set in TiviMate, Smarters, or XCIPTV for 4K sports?
Set the largest option (5,000 ms in TiviMate, "Large" in Smarters). Buffer time in seconds equals buffer bytes multiplied by 8, divided by the stream bitrate in Mbps: a 15 MB allocation on an 18.5 Mbps 4K feed yields 6.5 seconds of protection, which covers typical ISP shaping bursts of 2-4 seconds without a visible freeze.
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.
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.
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.