JobCannon
全部技能

Adaptive Bitrate Streaming

⬢ 層級 2技術
高
薪資影響
4 個月
學習時長
困難
難度
—
職業
一覽

Adaptive Bitrate (ABR) streaming automatically switches video quality based on available bandwidth and device capabilities. Formats: HLS (Apple standard, HTTP Live Streaming), DASH (MPEG-DASH, open). Core: split video into segments (2–10 sec), encode at multiple bitrates (240p–4K), manifest file lists variants, player measures throughput → requests optimal quality segment. Why it matters: Netflix/YouTube/TikTok all use ABR (enables 1B+ concurrent streams, <5 second start-up time, playback never stalls). Salary: video engineers at Mux, Wistia, Vimeo, YouTube earn $170k–$280k. Learning path: 2 weeks theory (codec, streaming protocols), 2 weeks hands-on (encode video, build HLS/DASH manifest), 1 month player integration.

什麼是 Adaptive Bitrate Streaming

Adaptive Bitrate (ABR) streaming automatically adjusts video quality based on network speed and device capability. Video file encoded once at 10+ bitrates (240p–4K). Player measures available bandwidth, requests optimal quality segment. As network changes, player switches quality seamlessly (usually imperceptible). Enables: Netflix serves 200M+ simultaneous streams, YouTube 1B+ hours watched/day, TikTok billions of videos. Without ABR, most streams would buffer/stall.

🔧 工具與生態
FFmpeg video encodingMediaConvert (AWS)HLS.js (JavaScript player)DASH.jsWidevine DRM (content protection)Video.js

💰 各地區薪資

地區初級中級高級
USA$110,000$160,000$240,000
UK£65,000£95,000£145,000
EU€70,000€100,000€150,000
CANADACA$115,000CA$155,000CA$230,000

❓ 常見問題

What's the difference between HLS and DASH?
HLS (HTTP Live Streaming): Apple standard, widely supported, simpler. DASH (MPEG-DASH): open standard, more flexible, TV/broadcast standard. Both achieve same thing: ABR streaming. HLS + DASH together = maximum compatibility (web + mobile + TV).
Why not just use one bitrate (e.g., stream at average quality)?
Users have varying bandwidth: 3G (1 Mbps), 4G (10 Mbps), WiFi (50+ Mbps). Single bitrate: either buffers on slow networks or wastes bandwidth on fast. ABR adapts, optimizing quality/playback.
How many bitrate variants should I encode?
Typical: 6–10 variants (240p, 360p, 480p, 720p, 1080p, 2K, 4K). Each doubles storage/processing. Sweet spot: 6 variants (240p→4K) serving 95% use cases. Streaming services use 10+ (optimize for each region/device).
What's the tradeoff between segment duration and startup time?
Shorter segments (2–4 sec): faster startup, more requests. Longer segments (10 sec): slower startup, fewer requests. Typical: 6–10 sec segment = 3–5 sec startup time, manageable request load.
How does DRM (content protection) work with ABR?
DRM (Widevine, FairPlay, PlayReady) encrypts each segment. Player decrypts before playback. Overhead: licensing key + DRM license acquisition (~100ms). Most platforms use DRM for licensed content (Netflix, Disney+).
What's a manifest file and why do players need it?
Manifest: XML/JSON listing all available bitrate variants + segment URLs. Player reads manifest: 'I can play 240p, 360p, 720p variants. Based on bandwidth, request 720p.' Manifest = player's guide to available content.
Can I build my own ABR player or use third-party?
Third-party (HLS.js, DASH.js, Video.js): easier, proven code. Custom: more control, longer dev time. Most use third-party (reduces risk), customize ABR algorithm (bandwidth estimation, quality selection logic).

不確定這項技能適不適合你？

做一下職業匹配，我們會推薦合適的方向。

找到最適合我的技能 →

找到理想的職業方向

在 2,521 個職業中進行技能匹配。免費。

免費做職業匹配 →