HTTP-TS Browser Experimental Playback Guide
Learn how HTTP-TS differs from HLS and the limits of testing raw MPEG-TS streams with mpegts.js.
Short answer
HTTP-TS serves MPEG-TS data directly over HTTP. It resembles HLS segments but has no m3u8 playlist management, so it fits experiments or internal pipelines better.
Where it sits in a video pipeline
TS is a container common in broadcast and HLS segments. Raw HTTP-TS has no playlist telling the player bitrate, segment order or update window.
How to use it in a browser project
Browsers usually cannot natively play raw TS; a player such as mpegts.js must parse it into browser media APIs.
What the server has to do
The server must output continuous valid TS packets with continuous timestamps, otherwise players may stall or fail.
Common development scenarios
- Player experiments, internal debugging and temporary ingest from legacy devices or intermediate pipelines.
Debugging order
- Confirm it is real MPEG-TS data, not m3u8. Then check TS packets, PAT/PMT, timestamps and codecs.
Recommended conversion paths
- For user-facing playback, wrap it as HLS first.
- For low latency, evaluate WebRTC or FLV.
Minimum usable implementation
- Frontend: attempt playback with mpegts.js.
- Backend: ensure valid TS packets, continuous response and CORS.
Developer decision rule
HTTP-TS should be judged by its role in the delivery chain, not by the protocol name alone. Browser result: Experimental, MSE-player based. Before promising playback, confirm the source type, whether a server conversion is required, CORS and HTTPS policy, codec support and the latency target.