When ProPresenter’s NDI output stops working, it can disrupt an entire live production in seconds. Slides fail to appear on the stream, lower thirds don’t reach the switcher, or the video feed simply vanishes without warning. For churches, event teams, and live stream operators who rely on ProPresenter and NDI as the backbone of their workflow, this kind of failure isn’t just annoying—it’s stressful and costly.
NDI has become a cornerstone of modern video production because it eliminates the need for complex cabling and expensive hardware. ProPresenter’s ability to send video over the network makes multi-computer setups more flexible than ever. But with that flexibility comes complexity. When something breaks, the cause isn’t always obvious. This guide explains why ProPresenter NDI stops working, how to diagnose the real problem, and how to restore a stable, professional setup that you can trust during live events.
Understanding ProPresenter and NDI at a Practical Level
ProPresenter is widely used for lyric projection, sermon slides, lower thirds, and live video playback. NDI, short for Network Device Interface, allows ProPresenter to send its video output across a local network to other software or hardware that supports NDI. This includes platforms such as OBS, vMix, TriCaster, and many modern broadcast tools.
Instead of relying on HDMI or SDI cables, ProPresenter encodes its output into a network stream. Other devices on the same network detect that stream and display it in real time. When everything works as expected, the setup feels almost magical. When it fails, the issue can come from the network, the operating system, the software configuration, or even performance limitations of the hardware itself.
Understanding that NDI is not “just software” but a real-time video transport system is essential. It behaves more like live broadcast infrastructure than a typical app feature, and it needs to be treated with the same level of care.
Why ProPresenter NDI Stops Working in Real-World Setups
Most NDI problems are not caused by ProPresenter itself but by the environment it operates in. Networks that were never designed for live video, computers overloaded with background tasks, and security settings that silently block traffic are all common culprits.
Another frequent cause is change. A system that worked perfectly last week may suddenly fail after a software update, network change, or hardware swap. NDI is sensitive to version mismatches and network behavior, so even small changes can have unintended consequences.
It’s also important to recognize that “NDI not working” can mean different things. Sometimes the NDI source does not appear at all. Other times it appears but shows a black screen, frozen frame, or missing audio. In some cases, the feed works briefly and then drops out during the service. Each symptom points to a different underlying issue.
Checking the Network Foundation First
Before opening ProPresenter or changing software settings, it’s critical to look at the network itself. NDI relies on fast, stable network communication. Wired Ethernet connections are strongly preferred because Wi-Fi introduces interference, packet loss, and unpredictable latency that can easily break video streams.
All devices involved must be on the same local network and, more importantly, the same subnet. If one computer is on a different VLAN or isolated network segment, NDI discovery will fail even if basic internet access works fine. This is a common issue in venues with managed switches or complex IT infrastructure.
Network speed matters more than many people expect. A single high-quality NDI stream can consume a significant amount of bandwidth. Older switches, 100-megabit ports, or overloaded routers may simply not be able to keep up, leading to dropped frames or complete failure.
Ensuring NDI Is Properly Installed and Compatible
ProPresenter does not operate NDI in isolation. It relies on NDI runtime libraries installed on the operating system. If these components are missing, outdated, or mismatched between machines, NDI will fail silently.
Installing the latest official NDI Tools package ensures that the necessary services are running correctly. Restarting the computer after installation is essential, even if it feels unnecessary. Many NDI-related services do not initialize properly until a full reboot.
Compatibility also matters between machines. If ProPresenter is running a newer NDI version than the receiving software supports, discovery or decoding may fail. Keeping all production machines aligned on current versions reduces these risks significantly.
Verifying ProPresenter’s NDI Configuration
Inside ProPresenter, NDI must be explicitly enabled. This seems obvious, but it is surprisingly easy for this setting to be disabled after updates or profile changes. The output selection must also match the display you intend to send over NDI. Sending the wrong output often results in a black or empty feed even though NDI appears active.
Resolution and frame rate settings play a major role here. If ProPresenter is configured to output a very high resolution or frame rate, the network or receiving software may struggle to keep up. Matching the output settings to the rest of your production pipeline improves stability and reduces troubleshooting complexity.
It’s also important to ensure that ProPresenter is actually rendering content to the selected output. If slides or videos are not assigned to that output, the NDI feed may technically exist but contain no visible content.
Using NDI Studio Monitor as a Diagnostic Tool
NDI Studio Monitor is one of the most effective ways to determine whether ProPresenter is broadcasting an NDI signal at all. Because it is lightweight and purpose-built, it removes many variables from the troubleshooting process.
If Studio Monitor can see and display the ProPresenter feed, the issue is almost certainly on the receiving side, such as OBS or vMix. If Studio Monitor cannot see the feed, the problem lies with ProPresenter, the network, or system-level NDI services.
Testing from multiple machines on the same network can also reveal whether discovery is inconsistent. If one computer sees the feed and another does not, the issue is usually related to network segmentation or firewall rules.
Firewalls and Security Software as Hidden Blockers
Modern operating systems are aggressive about network security, and for good reason. Unfortunately, NDI traffic often looks suspicious to firewalls because it uses dynamic ports and continuous data streams.
Both Windows and macOS firewalls must allow ProPresenter and NDI-related services to communicate freely on the local network. Third-party antivirus or endpoint protection software can interfere even more aggressively, sometimes blocking traffic without clear warnings.
Temporarily disabling firewalls for testing can help confirm whether security software is the cause. Once confirmed, creating proper application exceptions is far safer than leaving protections disabled permanently.
How Network Hardware Can Break NDI Without Warning
Managed switches and enterprise-grade routers introduce features that can interfere with NDI, even when everything appears to be connected correctly. Multicast handling, traffic shaping, and energy-saving features can disrupt real-time video streams.
Some switches attempt to optimize traffic by limiting broadcast and multicast packets. Since NDI relies on these mechanisms for discovery, this optimization can effectively make NDI invisible across the network.
In many production environments, using simple unmanaged switches dedicated to AV traffic results in fewer problems. While they lack advanced controls, they also avoid many of the behaviors that break NDI unexpectedly.
Performance Limitations on the ProPresenter Computer
Even with a perfect network, ProPresenter still needs enough system resources to encode video in real time. CPU overload, GPU limitations, or background processes can cause NDI output to fail or degrade.
Live video playback, motion backgrounds, and high-resolution outputs all increase system load. If the computer is already near its limits, NDI encoding may be the first thing to suffer.
Monitoring system performance during a rehearsal or test session provides valuable insight. If CPU or GPU usage spikes when NDI is enabled, reducing output resolution or simplifying content may be necessary.
Receiving Software Matters More Than You Think
Applications like OBS and vMix handle NDI decoding differently. OBS requires an additional NDI plugin, and mismatches between plugin versions and NDI runtimes can cause instability.
Frame rate mismatches between ProPresenter and the receiving software can lead to jitter, latency, or dropped frames. Aligning settings across the entire workflow minimizes these issues and improves reliability.
It’s also worth remembering that receiving software consumes its own system resources. A machine that is already encoding a live stream may struggle to decode multiple NDI sources simultaneously.
Diagnosing Complex Issues with Advanced Tools
When basic troubleshooting fails, deeper inspection becomes necessary. Network analysis tools can reveal whether NDI packets are actually reaching their destination. If packets leave the ProPresenter machine but never arrive at the receiver, the network is the problem.
Testing in a simplified environment often provides clarity. Connecting both machines directly through a basic switch removes variables and helps isolate whether the issue is software-related or network-related.
Keeping drivers and firmware updated is equally important. Network adapter drivers, GPU drivers, and even motherboard firmware can affect real-time data handling in subtle but significant ways.
Building a Stable Long-Term ProPresenter NDI Workflow
Once NDI is working, the focus should shift to keeping it that way. Stability comes from consistency. Using a dedicated production network, standardizing resolutions and frame rates, and documenting configurations all reduce the risk of future failures.
Avoiding unnecessary updates right before important events is another best practice. Testing changes during the week rather than minutes before a service can prevent last-minute surprises.
Clear labeling of NDI sources also helps operators quickly identify the correct feeds under pressure. Confusion during a live event can be just as damaging as a technical failure.
When Professional Support Is the Right Choice
Some NDI issues stem from complex network environments that require professional expertise. Large venues, campuses, or shared IT infrastructure often impose constraints that are difficult to overcome without coordination.
Renewed Vision’s support team can assist with ProPresenter-specific problems, while community forums often contain valuable real-world insights from users who have faced similar challenges.
In critical production environments, consulting an AV professional can save time, reduce stress, and prevent repeated failures during live events.
Conclusion
When ProPresenter NDI is not working, the problem is rarely random. It is almost always the result of network limitations, configuration mismatches, or system performance constraints. By understanding how NDI actually operates and approaching troubleshooting methodically, most issues can be resolved without panic. A reliable NDI setup transforms ProPresenter into a powerful, flexible broadcast tool. It enables cleaner workflows, fewer cables, and greater creative freedom. With the right foundation and best practices in place, NDI becomes an asset rather than a source of stress.
