Adaptive Bitrate Streaming Simulator

Network

Base bandwidth 4.0 Mbps

Network jitter 30%

ABR Algorithm

Buffer cushion target 20 s

Live Player Stats

Buffer level

0.0 s

Playing quality

—

Est. throughput

0.0 Mbps

Rebuffer stalls

Total stall time

0.0 s

How it works

A real player (ExoPlayer, AVPlayer, hls.js) downloads video in short segments (here, 4 s each) and must pick a bitrate before each segment starts, using only what it knows so far: current buffer occupancy and recently observed throughput.

Buffer-based (BBA-style) rule: map the buffer level directly to a target rate between a reservoir and a cushion:

if  B ≤ reservoir:        rate = min
if  B ≥ cushion:          rate = max
else:                      rate = min + (max-min)·(B-reservoir)/(cushion-reservoir)

A shrinking buffer is itself the congestion signal — no throughput measurement needed.

Throughput-based rule: keep an exponentially-weighted moving average of measured segment download rates, then pick the highest bitrate that stays under it with a safety margin:

T̂ ← w·T̂ + (1-w)·T_measured   (w = 0.5)
target = 0.8 · T̂
pick highest level with bitrate ≤ target

Download time for a segment is size/throughput: Δt = (bitrate·segDur) / throughput. If the buffer empties before the next segment finishes, playback stalls (a rebuffer event) until at least one full segment (4 s) is buffered again.

Base bandwidth / jitter — sets the simulated network capacity and how much it fluctuates second to second.
Network drop — cuts bandwidth to ~15% for 5 seconds, the classic case that separates the two algorithms.
Buffer-based vs Throughput-based — switch the controller live and watch how each reacts to the same network trace.
Buffer cushion target — how much buffer the buffer-based controller needs before it's willing to play the top bitrate.

⏸ REBUFFERING

CDN origin Buffered segments (color = quality) Player

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.