Using FFmpeg with NDI

We often receive questions about whether we can provide a pre-compiled version of FFmpeg with NDI support. While this seems like a straightforward request, the answer is more nuanced. Below we’ve outlined the key considerations, legal constraints, and your available options.

Why don’t you provide FFmpeg compiled with NDI?

Due to legal and licensing reasons, we cannot distribute FFmpeg pre-compiled with NDI support. This is not a technical limitation but rather a licensing one. Certain codecs within FFmpeg (such as H.264, H.265, and AAC) require patent licensing and royalty payments, which we cannot bundle or distribute on the client's behalf.

What are my options?

1. Using the Standard SDK

You will need to rely on FFmpeg to decode H.264, H.265, and AAC streams. A standard FFmpeg distribution should already be capable of handling this decoding without additional changes. You are responsible for compiling FFmpeg with NDI support if you wish to use it in your workflow.

2. Using the Advanced SDK

The Advanced SDK allows decoding of H.264/H.265 directly within the SDK. However, if you choose to use FFmpeg’s video codecs instead, you are responsible for ensuring proper licensing and royalty payments, particularly to MPEG LA.

The FFmpeg library is not included with the Advanced SDK by default. You will need to manage compilation and integration.

What support can you expect from us?

We are happy to assist with NDI-related issues and provide guidance on using our SDKs. However, we cannot provide support for FFmpeg itself, nor can we advise on codec licensing obligations. For FFmpeg usage, licensing, or codec-specific concerns, you must consult the appropriate legal/licensing bodies.