PLAY: Resolving stuttering and freezing during NDI decode

PLAY: Resolving stuttering and freezing during NDI decode


If your BirdDog PLAY is producing a stuttering or frozen image when decoding an NDI source, work through the steps below in order. Most issues trace back to one of five root causes: NDI version mismatch, network bandwidth saturation, inadequate power, a problematic source, or outdated firmware.


1. Confirm firmware is up to date

Before any other troubleshooting, verify the PLAY is running the latest firmware version published on the BirdDog website. Outdated firmware can introduce compatibility issues with newer NDI versions and known performance bugs that have since been resolved.


2. Verify NDI source compatibility

The PLAY supports decoding High Bandwidth NDI up to 1080p60. Check the tech specs for the full list of supported NDI versions and resolutions.

  • The PLAY can receive a 4K (2160p) High Bandwidth NDI stream, but performance will degrade — this is expected behaviour and not a fault.
  • If you are using NDI|HX2 or NDI|HX3, confirm that both the source encoder and the PLAY firmware support the same profile.
  • Mismatched NDI versions between the source and the PLAY are a common cause of intermittent stuttering.

3. Test the NDI source independently

Rule out the source before assuming the issue is with the PLAY. Open the NDI source in NDI Studio Monitor (or another NDI viewer on a separate machine) while the problem is occurring.

  • If the source stutters in Studio Monitor too, the issue is upstream — investigate the source machine's CPU/GPU load, encoder settings, or network output.
  • If the source looks clean in Studio Monitor but stutters on the PLAY, continue to the steps below.

4. Check power delivery

USB ports on TVs, monitors, and laptops typically do not supply consistent or sufficient power for the PLAY. Inadequate power is one of the most frequently overlooked causes of intermittent performance issues.

  • Use a dedicated USB wall adapter (5V/2A or higher) connected directly to a mains outlet.
  • Alternatively, a third-party PoE splitter can provide reliable power over the same Ethernet connection. Ensure that the spliter is a female RJ45 to USB-C and male RJ45.
  • Avoid USB hubs or multi-port chargers under heavy load.

5. Enable multicast when decoding a source multiple times

If the same NDI source is being decoded by more than one device simultaneously, multicast should be enabled on your network.

  • Without multicast, each decoder (UDP, TCP, or RUDP) requests its own independent copy of the stream. This multiplies the outbound bandwidth demand on the source device's network interface, which can cause the source port to become saturated and unable to keep up — producing stuttering across all decoders.
  • With multicast, the source sends a single stream that all decoders receive simultaneously, using only one instance of network bandwidth regardless of how many devices are listening.
  • Enable multicast in the NDI Access Manager or via your managed switch's IGMP snooping settings.

Note: Multicast requires a managed switch with IGMP snooping enabled. Unmanaged switches will flood multicast traffic to all ports, which can cause different network performance issues.


6. Assess your network infrastructure

Network quality has a direct impact on NDI performance. Check the following:

  • Switch type: A managed switch is strongly recommended for NDI workflows. Managed switches allow you to configure multicast (IGMP snooping), Quality of Service (QoS), and VLANs to prioritise video traffic. Unmanaged switches offer no such control.
  • Gigabit minimum: Ensure the switch, all patch cables, and every device's network port are operating at Gigabit (1Gbps) or higher. 100Mbps links are insufficient for High Bandwidth NDI.
  • Cable quality: Use Cat5e, Cat6, or Cat6a cabling. Damaged, poorly terminated, or excessively long cables can introduce packet loss that presents as stuttering.
  • Switch capacity: Confirm the switch's total backplane bandwidth can handle the aggregate NDI traffic on the network.

7. Check source machine performance

Even if the NDI stream looks clean in Studio Monitor, a source machine under high CPU or GPU load may produce inconsistent frame timing that only becomes visible under decode latency.

  • Monitor CPU and GPU usage on the source machine during the issue. NDI encoding is CPU-intensive; sustained usage above ~85% can cause dropped or delayed frames.
  • Check that the source machine's network interface card (NIC) is not throttled by power management settings — set the NIC power mode to maximum performance in the OS network adapter settings.
  • Ensure no other bandwidth-heavy applications are competing on the same network interface as the NDI output.

8. Factory image the PLAY

If all other steps have been checked and the issue persists, applying a factory image will restore the unit to a clean state and rule out any corrupted configuration or software as the cause. Follow the full instructions in the dedicated guide below.

PLAY factory image process →

Note: If the issue continues after a factory image, contact BirdDog support with details of your network setup, firmware version, and NDI source configuration. help@birddog.tv

    • Related Articles

    • PLAY Firmware Release Notes

      PLAY Firmware Release Notes 04/04/25 Firmware 1.34 -------------------------------------------------- This release contains the following new features: Auto-reconnect feature: PLAY will app restart if a source issue is detected. Dashboard UI now ...
    • PLAY – Factory Image Process

      PLAY: Factory Image Process The following is the complete factory re-image process for the PLAY. For the PLAY Pro, please review our separate article for a reimage process unique to that unit: PLAY Pro Factory Image Process Please read and follow the ...
    • Technical Bulletin for Fanned PLAY

      SEPTEMBER 2023 SUMMARY BirdDog has recently begun shipping a new revision of the BirdDog PLAY. This revision has been developed to address important performance issues encountered by some users. These issues occur under specific workloads in ...
    • Play Pro: Factory Image Process

      PLAY Pro: Factory Image Process The following is the complete factory re-image process for the PLAY Pro. For factory image instructions for the original PLAY, please review the following article instead, as the process and image files are unique to ...
    • PLAY API and Companion App

      Attached is the PDF doc for API integration with the BirdDog PLAY and additional information about integration with the Companion app by BitFocus