NDI. Network Device Interface. It sounded like something from a cyberpunk novel. In reality, it was a protocol that sent video and audio over a standard Ethernet network. No capture cards. No HDMI handshake issues. Just pure, packet-switched sorcery.
For one terrifying second, the preview pane remained black. Doubt crept in. Of course it failed. Networks are unreliable. Should have stuck with HDMI.
She double-clicked it.
obs-ndi-4.11.1-windows-x64-installer.exe . It wasn't just an installer. It was a skeleton key. It had unlocked the cage of physical cables and turned her tangled desk into a wireless studio. It was, she decided, the most beautiful filename she had ever seen.
For three years, she had run a two-PC streaming setup. Gaming on the main rig, encoding and streaming on the secondary. The connection? A simple HDMI cable running from her gaming GPU’s output to a capture card on the streaming PC. It was reliable, like a stubborn mule. But it was also a cage. obs-ndi-4.11.1-windows-x64-installer.exe
Her heart beat faster.
It wasn't just video. It was her video—the crisp, 1440p, 120-fps output of her gaming PC, with zero perceptible lag. The colors were true. The audio was in sync. But more than that, she dragged a browser window over her gameplay on the gaming PC. On the streaming PC’s preview, the browser window was there , alpha channel intact, hovering like a ghost. In reality, it was a protocol that sent
She could layer anything. Anywhere. The network had become a ribbon cable stretching between two worlds.