The main contact at the media-autobuild_suite said the following:ĭon't put the SDK behind a **** registration wall, put it somewhere publicly and anonymously accessible also, don't put it inside an installer, that's unusable for redistribution and building automationįFmpeg expects ndi.lib or libndi.a, because that's the normal name of a library and is what's available in both macOS and Linux versions of the SDK.
The headers and libs (as opposed to DLLs) need to be licensed in such a way as to allow free redistribution in binaries and as build-able source. "Unless otherwise stated in the SDK, no files within the SDK and the Specific SDK may be distributed." I would guess that in particular this statement: The primary feedback from Zeranoe is that the license terms do not allow free distribution. I've asked on the Zeranoe forum and the media-autobuild_suite about integration into build of FFmpeg.
If there's a recommended way to build a custom version of FFmpeg with NDI builtin using MSVC that would be an alternative for me. This requires libs built with mingw GCC rather than MSVC.ĪFAIK building full versions of FFmpeg with MSVC is quite tricky and poorly supported. In addition I use the Media-AutoBuild_Suite ( ) to actually build my own custom versions of FFmpeg. Where one can download a static, dynamic or developer build with most popular features enabled.ĭo you plan to work with Zeranoe to make this available? At the moment I don't think your SDK includes the correct type of lib/symbol file to support this. I would very much like to make use of these capabilities via FFmpeg both using a Windows build and my own custom build.įor a Windows build I normally source my builds from the very popular Zeranoe web-site ( ). I was pleased to see the announcement that as of the 3.4.1 release of FFmpeg, NDI is built in for both read and write.
0 kommentar(er)
