As I understand, there shouldn't be any licensing issues if one uses
ffmpeg via the ffmpeg DLL's. As provided by Zeranoe in the
ffmpeg-win32-shared builds http://ffmpeg.zeranoe.com/builds/
Nav
On 3/27/2013 9:55 AM, Clément Boesch wrote:
On Tue, Mar 26, 2013 at 09:19:57PM -0700, Brad O'Hearne wrote:
On Mar 26, 2013, at 9:04 PM, Clément Boesch<[email protected]> wrote:
Thanks for the reply, Clement!
The h264 decoder is under LGPL.
I need not only the decoder, but the encoder as well. I read the link sent...I
wasn't clear on it -- is the encoder under GPL? If so, do you have any idea
what other commercial outfits are using the h.264 encoding? Surely they aren't
all rolling their own h.264 codec...
There is no native h264 encoder in FFmpeg. A long time ago there was an
experimental one but it was dropped because libx264 was maintained and by
far superior.
The x264 project offers some special licencing, you might want to ask them
directly.
Note: the project is FFmpeg, not Libav.
Apologies, between the project history someone posted a week ago, documentation, library naming
conventions, the mailing list names, and that Googling info is nearly always most useful searching
on "Libav" rather than "FFmpeg", (not to mention having looked at code for WAY
too long in the past several days), I mixed them up. My heart was in the right place though...sorry
about that.
The fork took a confusing name on purpose. Basically, anything @ffmpeg.org
is FFmpeg.
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user
