3 ms·
Can anyone clarify the licensing requirements of large scale ffmpeg deployments? In what cases are fees required?
by keepamovin 3y ago
Can anyone clarify the licensing requirements of large scale ffmpeg deployments? In what cases are fees required?
- hutzlibu 3y ago"FFmpeg is licensed under the GNU Lesser General Public License (LGPL) version 2.1 or later. However, FFmpeg incorporates several optional parts and optimizations that are covered by the GNU General Public License (GPL) version 2 or later. If those parts get used the GPL applies to all of FFmpeg. " http://ffmpeg.org/legal.html http://ffmpeg.org/legal.html Meaning it is free, but if you use some modules, you might have problems mixing it with proprietary code.
- bsenftner 3y agoThe general use case for ffmpeg inside proprietary software is the version of ffmpeg used needs to be statically compiled and linked into the software's executable, or it needs to be a separate executable called by the proprietary software.
- keepamovin 3y agoThanks. We're doing the second but I heard that at a certain scale you might need to pay fees anyway?
- bsenftner 3y agoI used to work at an FR video security company, where our product was in a significant percentage of the world's airports and high traffic hubs. Statically linked ffmpeg for the win.
- Daemon404 3y agoYou have that backwards - it must be dynamically linked. Static linking without providing your source would violate the LGPL.
- keepamovin 3y agoCan you drill down a bit more into this? I would consider static linking to be including unmodified ffmpeg with my application bundle and calling it from my code (either as a pre-built binary from ffmpeg official or compiled by us for whatever reason, and called either via a code interface or from a child process using a command line interface). Seems bsenftner's comment roughly confirms this, tho their original comment does make the distinction between the two modes. What's someone to do?
- Daemon404 3y agoIt is widely known and accepted that you need to dynamically link to satisfy the LGPL (you can static link if you are willing to provide your object files on request). There is a tl;dr here that isn't bad: https://fossa.com/blog/open-source-software-licenses-101-lgpl-license/ https://fossa.com/blog/open-source-software-licenses-101-lgp... But, speciically the bit in the LGPL that matters, is secton 5: https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html#SEC3 https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html#S... - particularily paragraph 2. As always, IANAL, but I also have worked with a lot of FOSS via lawyers. Also, this is and always has been the view of upstream FFmpeg. (Source: I work on upstream FFmpeg.)
- bsenftner 3y agoIf one statically links ffmpeg into a larger proprietary application, the only source files one needs to supply are your ffmpeg sources, modified or not. The rest of the application's source does not have to be released. In my (now ex) employer's case, only the low level av_read_frame() function was modified. The entire ffmpeg version used, plus a notice about that being the only modification, is in the software as well as the employer's web site in multiple places. They're a US DOD contractor, so their legal team is pretty serious.
- spider-mario 3y agoSection 6: “Also, you must do one of these things: a) […] if the work is an executable linked with the Library, [accompany the work] with the complete machine-readable ‘work that uses the Library’, as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. […] b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. […]”