|author||wm4 <wm4@nowhere>||2014-03-13 00:29:17 +0100|
|committer||wm4 <wm4@nowhere>||2014-03-13 00:29:17 +0100|
af_lavfi: beat it into working with Libav
The main incompatibility was that Libav didn't have av_opt_set_int_list. But since that function is excessively ugly and idiotic (look how it handles types), I'm not missing it much. Use an aformat filter instead to handle the functionality that was indirectly provided by it. This is similar to how vf_lavfi works. The other incompatibility was channel handling. Libav consistently uses channel layouts only, why ffmpeg still requires messing with channel counts to some degree. Get rid of most channel count uses (and hope channel layouts are "exact" enough). Only in one case FFmpeg fails with a runtime check if we feed it AVFrames with channel count unset. Another issue were AVFrame accessor functions. FFmpeg introduced these for ABI compatibility with Libav. I refuse to use them, and it's not my problem if FFmpeg doesn't manage to provide a stable ABI for fields provided both by FFmpeg and Libav.
Diffstat (limited to 'old-configure')
1 files changed, 1 insertions, 11 deletions
diff --git a/old-configure b/old-configure
index 42897f3c15..06f9ee16e1 100755
@@ -2831,21 +2831,11 @@ fi
-echocheck "libavutil av_opt_set_int_list() API"
-statement_check libavutil/opt.h 'av_opt_set_int_list(0,0,(int*)0,0,0)' && _avutil_has_opt_set_int_list=yes
echocheck "using libavfilter through af_lavfi"
if test "$af_lavfi" = auto ; then
if test "$libavfilter" = yes ; then
- if test "$_avutil_has_opt_set_int_list" = no ; then
- res_comment="libavutil too old"
if test "$af_lavfi" = yes ; then