A detective reviewing traffic cam footage for a missing persons case discovers the video codec isn’t just glitching—it’s editing out moments of violence in real time.

The last file was timestamped for tonight—2:14 a.m., same intersection. Leah parked her unmarked car two blocks away, a portable recorder running raw H.264 (no codec tricks). At 2:14:03, the white sedan appeared. At 2:14:05, it slowed.

“Someone’s rewriting the compression history,” her tech analyst, Milo, whispered over the phone at 1 a.m. “libvpx uses VP9. It’s open source. Which means anyone with root access to the city’s transcoding server can inject a filter—a real-time eraser.”

At 02:14:03, a woman in a gray hoodie crossed the intersection at Harbor and Third. At 02:14:05, a white sedan slowed beside her. At 02:14:06—green pixel mush. Codec corruption, she’d assumed. But the audio track kept running. A thud. A drag. Then silence.

Back at the station, Milo disassembled the binary. “It’s beautiful, in a terrifying way,” he said. “Uses optical flow to detect ‘high-motion violence’—punches, falls, door slams. Then it backfills the GOP with predicted frames. No I-frames. No evidence. Just smooth, watchable nothing.”

Here’s a short story draft inspired by the tone, technical title, and thematic elements you might associate with The Bay S02E03 and “libvpx” (a video codec often linked to digital surveillance, glitches, or fragmented recordings). Frame Drop