Obs-ndi-4.11.1-windows-x64-installer.exe

Then, a soft ding . "Installation Complete."

"Wait, how is your overlay tracking your movement without a green screen?" "What’s your lag?? It looks like you're on one PC!"

She clicked on the latest release. There it was. A single, blue-highlighted line of text:

She switched back to the gaming PC’s OBS. In the NDI Source properties, she clicked "Source Name." A dropdown populated. A single name appeared, glowing like a lighthouse beam through fog: obs-ndi-4.11.1-windows-x64-installer.exe

She pressed it.

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.

The Bridge Across the Lag

She smiled. She didn't answer. She just leaned back, watching her streaming PC’s CPU usage hover at 12%—down from 45% with the HDMI capture card. The network switch in the corner glowed with gentle green pulses, each one a packet of pure, uncompressed creativity.

She opened a browser tab. Her fingers, stained with coffee and mechanical pencil lead, typed the familiar path: github.com/Palakis/obs-ndi .

“I need a bridge,” she whispered, rubbing her eyes. “Not a leash.” Then, a soft ding

On the streaming PC, she went to Tools > NDI Output Settings. A small panel appeared. She clicked "Main Output" and gave it a name: MAYA_GAMING_RIG .

She double-clicked it.

Her heart beat faster.

Maya rebooted OBS on both machines. On her gaming PC, she added a new source. She scrolled past "Display Capture," "Game Capture," "Window Capture." There, nestled between "Media Source" and "VLC Video Source," was a new entry: .

MAYA_GAMING_RIG (OBS)