v150 · WebRTC · Media
Frame Budget Calculator
Each frame from a MediaStreamTrack arrives on a schedule. If your transform takes longer than the frame interval, the queue fills up and frames are dropped — which is exactly what discardedFrames counts. This calculator shows the frame budget, how much of it your transform consumes, and whether drops are inevitable.
Key insight:
discardedFrames / totalFrames is your pipeline health ratio. If it grows non-zero, your transform is too slow for the source rate. Use this calculator to size your transform budget before shipping.
Parameters
Results
—
frame budget (ms)
—
budget used
—
predicted discards
—
totalFrames
—
discardedFrames
—
health %
Frame budget = 1000 ms ÷ source_fps
Utilization = transform_ms ÷ frame_budget
Drop prediction: if transform_ms > frame_budget, queue grows at rate (transform_ms − budget) per frame until buffer_size is exceeded; then frames are discarded.
discardedFrames ÷ totalFrames = health ratio (0% = perfect, >20% = action needed).
Utilization = transform_ms ÷ frame_budget
Drop prediction: if transform_ms > frame_budget, queue grows at rate (transform_ms − budget) per frame until buffer_size is exceeded; then frames are discarded.
discardedFrames ÷ totalFrames = health ratio (0% = perfect, >20% = action needed).
—
Frame timeline — 10-frame window
Budget remaining
Transform time
Discarded
see also
- Pipeline Meter — live readout of totalFrames and discardedFrames
- Diagnostic Overlay — HUD over a camera feed
- Pipeline Health Monitor — live chart with consumer-rate slider
- ChromeStatus entry
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗