Streaming

NDI source not showing up? How to fix it

You set up an NDI source — a camera, a graphics PC, or a scripture feed — and it's just… not there in the drop-down. Blank list, no source, no clue why. Don't panic: NDI "invisible source" problems come from a short list of causes, and each has a clear fix. Let's walk through them.

How NDI finds sources (the 10-second version)

NDI sends video over your local network, and devices discover each other automatically — as long as they're on the same network and nothing is blocking them. When a source doesn't appear, it's almost always because that discovery is being blocked, or the two devices aren't really on the same network. New to this? Start with NDI for churches.

The quick troubleshooting table

Fix 1: Confirm NDI is installed and on

In OBS, NDI needs the NDI plugin and runtime installed — it's not built in. If your NDI source menu is missing entirely, that's the cause. Install both, restart OBS, and check again. Full steps in add an NDI source in OBS. In vMix, NDI is built in — see add an NDI source in vMix.

Fix 2: Let it through the firewall

The Windows firewall loves to silently block NDI's discovery. On both the sending and receiving computers, allow the app (OBS, vMix, or the source program) through the firewall for private networks. This fixes a huge share of "I can't see the source" cases.

Fix 3: Make sure they're on the same network

NDI discovery only works when both devices share the same network. Common traps:

• One device is on Wi-Fi, the other on wired — and they're on different subnets.
• A guest network is isolating devices from each other.
• A managed switch or VLAN is separating them.

Put both machines on the same wired network, avoid guest Wi-Fi, and they should find each other.

Fix 4: Go wired

Wi-Fi is unreliable for NDI — discovery drops, video stutters, sources flicker in and out. Use wired gigabit ethernet for anything NDI. This is the single best thing you can do for a stable NDI setup.

Fix 5: Check the source is really sending

It's easy to forget to actually turn NDI output on in the sending program. Open the source app and confirm its NDI output is enabled and named. If it's a scripture feed like TajiCast, confirm the NDI output is switched on in its settings — then it appears in your switcher's source list like any camera.

Work through it in order

1. Confirm NDI is installedRuntime + plugin (OBS); built-in (vMix).
2. Allow it through the firewallOn both the sending and receiving PCs.
3. Put both on the same wired networkNo guest Wi-Fi, no separate subnets.
4. Check the source is outputting NDIAnd has a unique name.

Once discovery works, your scripture feed shows up right beside your cameras — and TajiCast's verse overlay drops into OBS or vMix as cleanly as any other NDI source.