2 views collected around this technical thread.
HTTP Live Streaming (HLS) is Apple’s HTTP‑based media protocol that segments video into .ts files indexed by .m3u8 playlists, supporting adaptive bitrate, encryption, and CDN acceleration, and the article compares its features, workflow, VOD vs live modes, and how to generate segments with ffmpeg.
Adaptive Bitrate (ABR) streaming dynamically selects among multiple video representations using protocols like HLS, DASH, and CMAF, leveraging bandwidth predictions and buffer metrics to balance quality and re‑buffering, while evolving through hybrid, buffer‑based, rate‑based, and machine‑learning algorithms for optimal user experience.
This article details a solution for playing newly added drink videos on Android TV devices by converting large files into HLS streams, using service workers to cache each fragment in IndexedDB, and employing hls.js to enable seamless offline playback while managing memory constraints.
This article walks through the complete process of capturing a Hikvision RTSP camera stream, converting it with FFmpeg, serving it via Nginx (including RTMP/HLS modules), and finally playing the HLS stream in a Vue 3 web page using video.js, while also providing installation scripts and performance tips.
The article recaps Tubi’s eighth Elixir Meetup, detailing Horvo’s presentation on building a live HLS video streaming backend with Elixir, covering the system’s transcoder, scheduler, HLS server, encryption, ad‑insertion strategies, and why Elixir was chosen for high‑performance backend services.
Bilibili designed a self‑built live‑streaming P2P system that uses WebRTC DataChannels and a Tracker‑mediated handshake to exchange 60 KB MessagePack‑encoded HLS segment blocks among viewers, employing a free‑market task allocation to balance seeding and consumption, thereby significantly cutting CDN bandwidth costs.
Bilibili migrated its massive live‑streaming infrastructure from RTMP/FLV to MPEG‑TS‑free HLS using fragmented MP4, designing clustered slicing, dynamic back‑source selection, 1‑second key‑frame segments, cache pre‑warming and replay playlists, thereby cutting start‑up latency, supporting modern codecs, DRM and future immersive audio features.
This article explains the background, challenges, and technical solutions for protecting video content using HLS encryption, DRM standards, key protection, and token-based authentication, highlighting the limitations of simple encryption and proposing a multi-layered approach for secure streaming across platforms.
Youku’s engineering team introduced two Low‑Latency HLS solutions—an Apple‑based LHLS using HTTP/2 extensions and a community‑driven chunked‑transfer variant—while detailing latency sources in traditional HLS and presenting six protocol‑level optimizations that together reduce end‑to‑end live‑stream delay to under two seconds.
This article explains a front‑end solution for generating on‑hover video frame previews by extracting frames from HLS streams using WebAssembly‑compiled FFmpeg, covering playlist parsing, TS decryption, WASM integration, canvas rendering, caching strategies, and performance considerations.
The article outlines core live‑streaming principles, workflow, and major protocols (RTMP, HLS, HTTP‑FLV), then examines Vivo’s product‑launch challenges—massive concurrency, QPS spikes, and content safety—and presents practical solutions such as multi‑level caching, circuit‑breaker degradation, token‑bucket rate limiting to ensure stable, high‑quality streaming.
To meet the post‑COVID surge in K‑song live broadcasts, the team replaced high‑latency HLS with low‑latency HTTP‑FLV and built the cross‑platform kg‑player SDK—combining MSE, WASM, and WebGL decoding—to automatically adapt streams, reduce stutter, and support iOS/Android, improving performance and powering hundreds of thousands of daily views.
HJPlayer is a lightweight JavaScript library that enables browsers to play H264/AAC encoded FLV live and VOD streams as well as HLS streams by demuxing them into fragmented MP4 and feeding them through the Media Source Extensions API, offering both ES6 module and script tag integration.
The article outlines Tencent Classroom’s cloud VOD solution, detailing HLS streaming fundamentals, a Mongoose‑based local HTTP proxy with LFU caching and pre‑loading, performance optimizations for latency, buffering, security, and playback reliability, and common transcoding pitfalls with practical fixes, highlighting cloud migration benefits.
This article details how to replace WebRTC‑based multi‑audio streaming with HTTP‑FLV or HLS on the web, covering iOS Safari limitations, demuxing FLV, building ADTS headers, decoding with the Web Audio API, channel merging, and real‑time audio visualization using AnalyserNode.
This article explains the HTTP Live Streaming (HLS) protocol, its standard playlist and segment structure, the latency challenges of traditional HLS, and details Apple’s low‑latency HLS draft with five technical improvements, demo implementation, and a comparison to Periscope’s LHLS approach.
Live streaming platforms increasingly rely on CDN technology to handle sudden traffic spikes, improve latency and stability, and support various streaming protocols such as RTMP, HLS, and FLV, with a detailed workflow that shows how broadcasters, schedulers, and viewers interact through edge nodes.
This article explains why live streaming platforms rely on Content Delivery Networks, describes the CDN architecture and workflow, and compares the main streaming protocols—RTMP, HLS, and FLV—highlighting their characteristics and impact on latency and stability.
This article introduces the fundamentals of web live streaming, covering typical workflows, video compression concepts, key quality metrics, comparisons of RTMP, RTP, HLS, flv.js and WebRTC, and practical implementation details for mini‑programs with code examples.
The Android app’s HLS video produced an electric‑like noise because FFmpeg’s av_find_best_stream mistakenly selected the second audio track in a dual‑stream file, a track lacking 1‑8 kHz frequencies, whereas iOS and PC used the correct first track; fixing requires publishing videos with a single audio track and adding detection tools.