27 - Vmix

“That’s not how VMix routing works,” engineering replied.

“Does it matter? Check the upstream strain gauges.”

“I have. Three times. These feeds are live… just twenty-two hours ahead.” Vmix 27

Mira’s finger hovered over the preview monitor. Input 17 flickered—then resolved into a news desk, wrecked, with a headline crawling across the bottom: “Dam Failure at Dawn – 47,000 Evacuated.” The date matched tomorrow.

Mira Danvers, a veteran technical director, stared at the twenty-seven input tiles on her VMix workstation. Most showed standard feeds: Cam 1 (wide shot), Cam 2 (host), Cam 3 (guest). But Inputs 13 through 20 were black, labeled only with timestamps from the future. Three times

Mira looked at VMix 27, still running on her third monitor. Input 17 had gone black again. But Input 22—which had been dead all night—was now showing a live shot: the same news desk, intact, with a new crawl: “Mystery Alert Saves Thousands – Source Unknown.”

She keyed the intercom. “Control room to engineering—I need a clean ISO feed of Input 17, no metadata, just video.” Mira Danvers, a veteran technical director, stared at

A long pause. “We’re evacuating the lower valley now. How did you know?”

“Neither is watching a disaster before it happens and doing nothing.”

In the control room of Station 7, the big board read “Vmix 27” —not a software version, but the code name for a live broadcast that wasn’t supposed to exist.

And in the system logs of Station 7, under “unusual routing activity,” one line remained: Session Vmix 27 – Duration 00:00:00 – No data.