> On Oct 26, 2016, at 4:44 PM, d...@dericed.com wrote: > > >> On Oct 26, 2016, at 3:29 PM, Michael Niedermayer <mich...@niedermayer.cc >> <mailto:mich...@niedermayer.cc>> wrote: >> >> On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote: >>> Hi all >>> >>> Its long since FFmpeg 3.1, so its time to make 3.2 >>> ill branch release/3.2 off master and make 3.2 in maybe about a week or >>> 2 unless something delays it >> >> release/3.2 branched >> >> ill make the 3.2 release tomorrow from release/3.2 >> so if anyone wants to backport something, you have till then > > Maybe too late, but it is possible to include > https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/eabbc64728c2fdb74f565aededec2ab023d20699 > > <https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/eabbc64728c2fdb74f565aededec2ab023d20699> > in 3.2. It resolves a regression added just before 3.2.
Sorry about this. I see James referenced the same issue in http://ffmpeg.org/pipermail/ffmpeg-devel/2016-October/201831.html <http://ffmpeg.org/pipermail/ffmpeg-devel/2016-October/201831.html>. Dave Rice _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
