A1: The monitor does not support 10bit HDR.

Some monitors may not fully support 10bit HDR signals. If the monitor’s hardware or software does not fully support the HDR protocol, it may result in a black screen. Try using a different monitor to troubleshoot.

A2: Video settings issue.

It could be a settings problem with the NDI decoder or the computer, causing incorrect output of the 10bit HDR signal. Check the settings of the decoder and display device to ensure they support the correct color depth and color format. If the decoding parameters module does not show a dynamically changing bitrate, it indicates abnormal device decoding.

A3: Signal transmission issue.

In high-bandwidth video signal transmission, the quality of the HDMI cable is also a factor. A poor-quality cable might not handle the required bandwidth, leading to signal loss and a black screen. Try replacing the peripheral cable.

A4: Compatibility issue with other devices.

If you are using receiving equipment (e.g., receivers, TVs, monitors) or video processors, compatibility between them can also affect the correct display of the signal, causing a black screen. Try testing with other equipment to see if the problem lies with a specific device.

A1: Manually add the video source IP address.

1）lick the “+” in the upper right corner of the scan list to enter the source configuration page.

2）Enter the IP address of the NDI source, then click the “+” on the right to add it.

3）By default, the NDI source will enter the default group [Public Group]. If it needs to be in a custom group, edit the [Group] field.

A2：Using NDI Discovery Service.

1）Download and install NDI Tools software: NDI Discovery Service is usually provided with the NDI SDK. Ensure the Visual Studio 2017 C++ runtime required for NDI is installed on the computer running the discovery server.

2）Run the discovery service:Find and run NDI Discovery Service.exein the NDI SDK installation directory (e.g., it might be in Bin\Utilities\x64). In this demonstration, it’s located in D:\NDI 6 Tools\Discovery. This application will run a server on your computer to manage the registration and discovery of NDI sources.Double-click to start the NDI discovery server. The NDI discovery server’s IP address is 192.168.22.2.

3）Configure the NDI discovery server on the codec terminal.After starting the discovery server, we need to register all devices with it. Here, the encoder N50’s IP is 192.168.43.185, and the decoder N30’s IP is 192.168.28.118.

The configuration on N30 is as follows:

The configuration on N50 is as follows:

4）After completing this step, theoretically, the decoder’s NDI source list should automatically scan the IP addresses of other NDI encoders on the same NDI discovery server. Please ensure the encoder and decoder are in the same group; otherwise, automatic discovery will not work.

A1: Improve NDI encoder settings.

HB mode allows for a higher bitrate, typically resulting in a clearer picture than standard NDI.

Increasing the bitrate reduces compression loss, making the image sharper. However, it also demands higher network bandwidth.

In the NDI encoder, the “Encoding Quality” setting can increase the encoding bitrate, up to a maximum of 200%. Higher bitrates require better networks; it’s advised not to set it to the maximum unnecessarily.

*Note: This bitrate configuration feature is only available in N3/N4/N30/N40/N50/N60 models. N5/N6 models in the current version do not have this configuration.

Using YUV 4:2:2 10bit is better than 4:2:0 8bit.

10bit color depth preserves more color information and reduces color banding.

A2: Network optimization.

NDI|HB has very high network requirements; insufficient bandwidth directly affects picture quality:

1）Ensure sufficient bandwidth: HB mode for 1080p60 requires about 100-150 Mbps/stream, 4K30 requires even more.Use Gigabit Ethernet (1 Gbps) or better, preferably 10GbE for multi-stream transmission.

3）Reduce network interference:Use a dedicated switch or VLAN to isolate NDI traffic and avoid network congestion.

3）Network latency optimization:Enable QoS (Quality of Service) to prioritize NDI traffic

A3: Decoder-side optimization.

Even if the encoder-side quality is high, insufficient processing power on the decoder side can affect the picture:

1）Hardware decoding: Use devices that support NDI|HB hardware decoding, such as NDI Studio Monitor with a high-performance graphics card.

2）Avoid excessive scaling: Try to match the decoder output resolution to the original resolution to avoid blurring from software scaling.

3）Update drivers and software: Keep graphics card drivers and NDI decoders up to date to improve performance and compatibility.

A4: HDR/Color optimization.

If using 10bit HDR, ensure the monitor supports 10bit HDR. Match the output color space to the display device (e.g., BT.709). Avoid automatic color compression or excessive brightness/contrast adjustments.

A1: Incorrect firmware name.

Downloading the same firmware package multiple times might cause the name to append (1), etc., leading to firmware recognition failure. The upgrade might appear complete but the device remains on the original version. Try restarting the device and re-uploading the firmware package. If it still fails, contact [email protected] assistance.

A2: Firmware upload failure.

If the device’s internal storage is full, uploading the firmware may fail with an “Insufficient device space” error. Contact [email protected] assistance.

A3: Firmware model mismatch.

Confirm the firmware package is intended for this specific model. Customized versions cannot be directly upgraded using the official website release. Contact [email protected] obtain the correct firmware package.

A1: Set a special group.

Configure this NDI stream to a non-public group. You can set a special group for this NDI stream. This way, decoders cannot automatically discover it, but the network connection remains intact and does not affect decoding output.

A2: Network isolation.

Isolate the corresponding NDI stream using VLANs on network equipment. It is recommended to seek assistance from a professional network engineer for configuration.

A1: Network bandwidth issue.

Check if the network bandwidth is sufficient. Ensure your network meets Full NDI requirements. Full NDI encoding bitrate is typically under 200 Mbps. It is recommended to use a dedicated Gigabit Ethernet network to ensure smooth transmission.

A2: Network configuration and latency issues.

Check for packet loss or latency in the network. Use tools like ping or traceroute to test network stability. Ensure the network is not congested and minimize interference from other devices. Also, ensure the NDI source and decoder are on the same local area network to avoid routing issues.

A3: NDI version compatibility.

Ensure the NDI encoder and decoder are running compatible NDI versions. If unsure, it is recommended to update the NDI software/firmware on both ends to the latest version to avoid compatibility issues.

A4: NDI stream settings issue (Frame rate/Bitrate).

Check the encoder’s frame rate and bitrate settings. If the stream’s bitrate is too high or the frame rate exceeds the decoder’s processing capability, it may cause buffering, lag, or reduced quality. Reducing the bitrate or frame rate might help.

A5: Hardware issue.

Check for hardware problems. Inspect cables for damage, ensure ports are securely connected, and confirm the decoder hardware is functioning normally. If necessary, test with alternative hardware (e.g., replace the cable).

A6: Encoder-specific settings issue.

The NDI encoder might be using settings incompatible with the decoder, causing the stream transmission method to be unprocessable. Check the encoder’s settings, including codec, resolution, and frame rate. Ensure these settings are within the decoder’s capabilities and adjust them if necessary to match the decoding capacity.

A1: Check the version.

In Net Stream: Starting from version V2.20, the encoding mode added support for HLS, UDP, and RTP protocol streaming. Therefore, please ensure you have upgraded to V2.20 or a later version.

A2: Browser cache.

After completing the upgrade, press Ctrl+F5 to force a browser refresh to avoid any caching issues.

A1: Confirm the RTMP format is correct.

Log in to the device’s web interface and confirm the RTMP streaming address is correct. The format is URL/StreamKey.

For example: If YouTube generates the URL as rtmp://a.rtmp.youtube.com/live2 and the StreamKey as 5r5m-c7y9-bdye-rqdv-f0up, then the streaming address should be: rtmp://a.rtmp.youtube.com/live2/5r5m-c7y9-bdye-rqdv-f0up.

A2: Confirm DNS configuration is correct.

Since live platform addresses use domain names for streaming, ensure the device obtains DNS settings. Click “Settings” -> “Network Settings”.

A1: Our devices (such as N5/N6, N60/N50 series) support the following NDI protocols

Full NDI:Provides lossless/near-lossless video quality, suitable for professional scenarios with extremely high image quality requirements.

NDI|HX2:An optimized encoding protocol that provides high-quality video at lower bandwidths. This is our default supported “HX” version.

NDI|HX3:The latest protocol version, further improving compression efficiency and transmission stability, especially suitable for 4K and high-frame-rate content.

*The term “NDI|HX” mentioned in the products defaults to the HX2 version; HX1 is not supported.

A1: Priority on Image Quality:Choose Full NDI, but ensure sufficient network bandwidth.

Balance Bandwidth and Image Quality:Choose NDI|HX2 (default recommendation).Low Bandwidth/High Frame Rate Needs:Choose NDI|HX3 (requires device support).