Vincent Bain wrote:
Perhaps I should downgrade (force older version) ffmpeg, to get in the
first case of the if loop.
Here's the result of ffmpeg --version on my box:ffmpeg version 0.7.15, Copyright (c) 2000-2013 the FFmpeg
developers
built on Feb 22 2013 07:18:58 with gcc 4.4.5
configuration: --enable-libdc1394 --prefix=/usr
--extra-cflags='-Wall -g ' --cc='ccache cc' --enable-shared
--enable-libmp3lame --enable-gpl --enable-libvorbis
--enable-pthreads --enable-libfaac --enable-libxvid
--enable-postproc --enable-x11grab --enable-libgsm
--enable-libtheora --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-libx264 --enable-libspeex
--enable-nonfree --disable-stripping --enable-avfilter
--enable-libdirac --disable-decoder=libdirac
--enable-libfreetype --enable-libschroedinger
--disable-encoder=libschroedinger --enable-version3
--enable-libopenjpeg --enable-libvpx --enable-librtmp
--extra-libs=-lgcrypt --disable-altivec --disable-armv5te
--disable-armv6 --disable-vis
libavutil 50. 43. 0 / 50. 43. 0
libavcodec 52.123. 0 / 52.123. 0
libavformat 52.111. 0 / 52.111. 0
libavdevice 52. 5. 0 / 52. 5. 0
libavfilter 1. 80. 0 / 1. 80. 0
libswscale 0. 14. 1 / 0. 14. 1
libpostproc 51. 2. 0 / 51. 2. 0
It gets better; between URL_WRONLY and AVIO_FLAG_WRITE, there was also
AVIO_WRONLY.
https://github.com/FFmpeg/FFmpeg/commit/59d96941f0285a501989d5f2c9b69be0a1393ed5
To grass-dev: given the consistent instability of the ffmpeg API, we
might want to consider generating a warning if --with-ffmpeg is used.
Amongst the few users who actually need that flag, there might be
someone willing to put in the effort to figure out which version
corresponds to which API.
--
Glynn Clements <glynn@gclements.plus.com>