[FFmpeg-devel] [PATCH] configure: enable libavresample by default
Michael Niedermayer
michaelni at gmx.at
Mon Oct 21 20:34:49 CEST 2013
On Sun, Oct 20, 2013 at 07:23:23PM +0200, wm4 wrote:
> ---
> There are several reasons why we should do this:
> - It makes it easier to migrate from Libav to FFmpeg.
> - Reduces differences between Libav and FFmpeg, increases
> interoperability, and reduces the change that software becomes
> Libav or FFmpeg only (the latter would not be bad for FFmpeg, but
> the latter definitely is - so interoperability is better for FFmpeg
> as well).
> - Makes resampling and mixing behavior (performance and quality)
> more predictable for software that has to run with both FFmpeg
> and Libav.
> - Makes some Libav-only software run on FFmpeg (assuming there
> is software which relies on libavresample being present).
> - Easier to maintain than a hypothetical API compatibility wrapper
> around libswresample to make it look like libavresample.
> - Some audio filters in lavfi depend on it. They are disabled if
> libavresample is disabled.
> - You shouldn't cause pain to your users just because you think
> that libswresample is unambiguously better than libavresample.
> - It's in the source tree, so why not enable it?
Thats a long list, but i think for discussing the change of
avresamples default build status, theres one keypoint missing
and that is who would maintain it ?
maintain = (like always, review patches on ffmpeg-devel, fix
regressions and security issues posted to trac)
also one could go on and argue when avresample why not gstreamer
and libc or maybe gnu make.
though i guess this direction of argumentation doesnt lead anywhere
i find your "inflicting pain" and politics chatter a bit lame
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
You can kill me, but you cannot change the truth.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20131021/bc0becaa/attachment.asc>
More information about the ffmpeg-devel
mailing list