On Mon, Oct 17, 2016 at 5:20 PM, Moritz Barsnick <barsn...@gmx.net> wrote: > On Mon, Oct 17, 2016 at 17:09:15 +0200, wm4 wrote: >> Does this copy parts of libebur128 to FFmpeg? >> Why? > > There was a long discussion regarding this patch: > > http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2016-April/192668.html > > (in summary: "please don't require yet another small external library, > rather port it to ffmpeg and maintain it") leading to this one: >
The generic idea was not to just copy/paste an external library into internal code, but extend the ebur128 code we already have - at least that way we get code written by one of our maintainers, code he knows and can properly maintain. If you just copy the implementation of a library, you might as well just use that library - thats what it exists for. Why do we want to increase the maintenance burden of our project when other people (ie. the authors of libebur128) are already doing it as well? - Hendrik _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
