This tool tests audio/video sync (lip sync) — the alignment between what's heard and what's seen. A frame-accurate animation paired with a corresponding audio beep gives an unambiguous reference point: any drift between the two is immediately visible and measurable, in frames or milliseconds, rather than left to the eye and ear to guess at. Sync errors are common wherever audio and video travel through different paths — separate encoders, wireless links, streaming pipelines, or multi-stage broadcast chains — and they tend to compound at each conversion or transmission stage. This tool isolates that drift at the source, making it possible to catch and correct sync issues before they reach air or a live audience.

⚠️ Download the .mov file for accurate playback — Google Drive's built-in player won't render it properly.

This tool uses fast-motion video rather than a static test image because real signal problems live in the transitions between frames, not in a single frame. Motion reveals pixel response time and ghosting, stresses codec performance under inter-frame compression, demands the sustained bandwidth that high-motion content actually requires, and exposes judder, interpolation artifacts, and sync tearing — issues a still image will never surface. It's the difference between checking that a signal chain looks right and confirming it holds up under real broadcast conditions.

⚠️ Download the .mov file for accurate playback — Google Drive's built-in player won't render it properly.

A pathological test pattern is a deliberately worst-case signal used to stress a system’s weakest points, rather than mimic real content. In SDI video, SMPTE RP 178 defines two such patterns: one stresses the cable equalizer with long runs of identical bits, the other stresses clock recovery (the PLL) with extreme transition density. Technicians run them through cables, routers, converters, and capture cards to validate margin, qualify equipment, and reproduce intermittent dropouts on demand. If a link locks cleanly under the pattern, it will handle real programming reliably. Failures usually point to marginal connectors, overlong runs, or out-of-spec gear, especially at 3G, 6G, and 12G rates.