Bitrail

Home/Streams

Stream catalogue

Four sources, each built to make a different class of failure visible. Filter by what you are trying to break.

4 streams

Timecode and colour bars

Frame counter over SMPTE-style bars. The number on screen is the frame index, so a dropped frame or an audio offset is visible without tooling.

A/V syncdropped framesseek accuracy

30 fps · 60s · 360p, 720p, 1080p · HLS + progressive

Open →

Smooth gradients

Slow four-colour gradients with almost no high-frequency detail. Banding introduced by an over-aggressive transcode shows up as visible steps.

bandingbit depthchroma subsampling

30 fps · 60s · 360p, 720p, 1080p · HLS + progressive

Open →

High motion, 60 fps

Continuous movement at 60 fps with a constrained bitrate. Encoders that cannot keep up produce blocking here long before they do on ordinary footage.

encoder stressframe pacingABR switching

60 fps · 60s · 360p, 720p, 1080p · HLS + progressive

Open →

Sustained download

Five minutes at 1080p in a single progressive file. Short clips finish inside the initial congestion window and tell you nothing about steady-state throughput; this one does not.

throughputcache fillrange requests

30 fps · 300s · 1080p · progressive only

Open →

Rendition ladder

Every multi-rendition source uses the same ladder, so a comparison across sources is not also a comparison across bitrates.

RenditionResolutionVideoAudio
360p640×360800 kbit/s96 kbit/s
720p1280×7202500 kbit/s128 kbit/s
1080p1920×10805000 kbit/s128 kbit/s

Bitrates are capped rather than averaged: -maxrate equals the target and the buffer is twice that. A rendition therefore stays inside its announced bandwidth, which is what an ABR player assumes and what many test files get wrong.