[FFmpeg-devel] Vid.stab video stabilization ready for libavfilter
ubitux at gmail.com
Wed Feb 20 23:27:56 CET 2013
On Wed, Feb 20, 2013 at 11:06:22PM +0100, Georg Martius wrote:
> Dear ffmpeg developers,
> I am the author of the vid.stab  video stabilization library that is used
> in transcode so far.
> Now I have implemented filters for libavfilter which work great.
> The code-base was completely restructured and is now independent of transcode
> and available as a library. The code is on github .
> How can it become part of ffmpeg?
> a) the library becomes part of ffmpeg (a subdir in the tree)
> b) the library stays stand-alone and only the two filter files go into the
> libavfilter directory.
> I would like to keep the implementation of the lib independent of ffmpeg to be
> able to integrate it into other tools.
> What is your opinion?
I've come across your project in the past already, I'm really happy to see
you interested in contributing to FFmpeg... Especially since our current
deshake filter isn't perfect in various scenario¹. I'm also curious how it
compares to the one proposed on Youtube².
Now for you question about the integration in FFmpeg:
I don't think the FFmpeg project will distribute an extra library along
with the current ones (libavformat, libavcodecs, libswscale, libavfilter,
etc) given that it has a very specific usage. Also, it's the purpose of
libavfilter to propose such thing. Of course, your API could be integrated
to libavfilter somehow, but would likely be exposed to the user only
through the usage of the filter. Doing this would mean you would have to
maintain that code in FFmpeg (given that you would be the maintainer of
that code, you would just ask for regular merges from your github).
The other solution of just adding the simple filters and link them with
your library as extra party will require a proper packaging of your
library in various distributions, otherwise it's likely to be never used
(while having the whole code maintained in FFmpeg will provide you instant
users). Also, it will require some discussions with the packagers to get
FFmpeg linked with it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 490 bytes
Desc: not available
More information about the ffmpeg-devel