Re: [FFmpeg-devel] FFmpeg 3.2

[Andreas Cadhalpun]

On 27.10.2016 20:07, Michael Niedermayer wrote:
> i didnt see this before making the release

Bad timing, can happen.

(I guess I should have checked this earlier, or rather FATE should have...)

> but 3.2.1 is planed in a week or 2

Let's get it fixed in that release.

Best regards,
Andreas

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Andreas Cadhalpun]

On 27.10.2016 18:44, James Almer wrote:
> Could you do a bisect and trac ticket for these? HLS got a lot of commits in 
> the past
> few months.
> apng didn't, so that one is weird.

I've found the commits causing the problems:
 * commit 5ef19590802f000299e418143fc2301e3f43affe causes the apng issue
 * commit 04964ac311abe670fb3b60290a330f2067544b13 causes the hls issues

I'll skip trac and send patches partly reverting those commits.

Best regards,
Andreas

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Thu, Oct 27, 2016 at 06:15:52PM +0200, Andreas Cadhalpun wrote:
> Hi,
> 
> On 26.10.2016 21:29, Michael Niedermayer wrote:
> > On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote:
> >> 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
> 
> The following regressions from 3.1 should be fixed before releasing 3.2:
> (They were detected by the Debian autopkgtest.)

i didnt see this before making the release

but 3.2.1 is planed in a week or 2

[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

It is what and why we do it that matters, not just one of them.


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[James Almer]

On 10/27/2016 1:15 PM, Andreas Cadhalpun wrote:
> Hi,
> 
> On 26.10.2016 21:29, Michael Niedermayer wrote:
>> On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote:
>>> 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
> 
> The following regressions from 3.1 should be fixed before releasing 3.2:
> (They were detected by the Debian autopkgtest.)
> 
>  * apng creation is broken:
> $ ./ffmpeg -f lavfi -i testsrc=s=32x32:d=0.1 -c:v apng -f apng apng.apng -y 
> &> /dev/null
> $ ./ffprobe ./apng.apng
> ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
> developers
>   built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
>   configuration: --disable-optimizations
>   libavutil  55. 34.100 / 55. 34.100
>   libavcodec 57. 64.100 / 57. 64.100
>   libavformat57. 56.100 / 57. 56.100
>   libavdevice57.  1.100 / 57.  1.100
>   libavfilter 6. 65.100 /  6. 65.100
>   libswscale  4.  2.100 /  4.  2.100
>   libswresample   2.  3.100 /  2.  3.100
> [png @ 0x29b02c0] IDAT without IHDR
> [png_pipe @ 0x29ae7e0] decoding for stream 0 failed
> [png_pipe @ 0x29ae7e0] Could not find codec parameters for stream 0 (Video: 
> png, none(pc)): unspecified size
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> Input #0, png_pipe, from './apng.apng':
>   Duration: N/A, bitrate: N/A
> Stream #0:0: Video: png, none(pc), 25 tbr, 25 tbn, 25 tbc
> 
>  * Probing of hls containing dts/eac3 doesn't work anymore:
> $ ./ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a dca -f hls dca.hls -y &> 
> /dev/null
> $ ./ffprobe dca.hls
> ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
> developers
>   built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
>   configuration: --disable-optimizations
>   libavutil  55. 34.100 / 55. 34.100
>   libavcodec 57. 64.100 / 57. 64.100
>   libavformat57. 56.100 / 57. 56.100
>   libavdevice57.  1.100 / 57.  1.100
>   libavfilter 6. 65.100 /  6. 65.100
>   libswscale  4.  2.100 /  4.  2.100
>   libswresample   2.  3.100 /  2.  3.100
> [hls,applehttp @ 0x3dfd7e0] Could not find codec parameters for stream 0 
> (Unknown: none ([130][0][0][0] / 0x0082)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> Input #0, hls,applehttp, from 'dca.hls':
>   Duration: 00:00:00.09, start: 1.40, bitrate: 9 kb/s
>   Program 0 
> Metadata:
>   variant_bitrate : 0
> Stream #0:0: Unknown: none ([130][0][0][0] / 0x0082)
> Metadata:
>   variant_bitrate : 0
> Unsupported codec with id 0 for input stream 0
> 
> $ ./ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a eac3 -f hls eac3.hls -y &> 
> /dev/null
> $ ./ffprobe eac3.hls 
> ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
> developers
>   built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
>   configuration: --disable-optimizations
>   libavutil  55. 34.100 / 55. 34.100
>   libavcodec 57. 64.100 / 57. 64.100
>   libavformat57. 56.100 / 57. 56.100
>   libavdevice57.  1.100 / 57.  1.100
>   libavfilter 6. 65.100 /  6. 65.100
>   libswscale  4.  2.100 /  4.  2.100
>   libswresample   2.  3.100 /  2.  3.100
> Format mpegts detected only with low score of 2, misdetection possible!
> [hls,applehttp @ 0x2d297e0] Could not find codec parameters for stream 0 
> (Unknown: none ([135][0][0][0] / 0x0087)): unknown codec
> Consider increasing the value for the 'analyzeduration' and 'probesize' 
> options
> Input #0, hls,applehttp, from 'eac3.hls':
>   Duration: 00:00:00.07, start: 1.40, bitrate: 13 kb/s
>   Program 0 
> Metadata:
>   variant_bitrate : 0
> Stream #0:0: Unknown: none ([135][0][0][0] / 0x0087)
> Metadata:
>   variant_bitrate : 0
> Unsupported codec with id 0 for input stream 0
> 
>  * Probing of hls containing mp2 detects mp3:
> $ ./ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a mp2 -f hls mp2.hls -y &> 
> /dev/null
> $ ./ffprobe mp2.hls 
> ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
> developers
>   built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
>   configuration: --disable-optimizations
>   libavutil  55. 34.100 / 55. 34.100
>   libavcodec 57. 64.100 / 57. 64.100
>   libavformat57. 56.100 / 57. 56.100
>   libavdevice57.  1.100 / 57.  1.100
>   libavfilter 6. 65.100 /  6. 65.100
>   libswscale  4.  2.100 /  4.  2.100
>   libswresample   2.  3.100 /  2.  3.100
> Input #0, hls,applehttp, from 'mp2.hls':
>   Duration: 00:00:00.08, start: 1.40, bitrate: 11 kb/s
>   Program 0 
> Metadata:
>   variant_bitrate : 0
> Stream #0:0: Audio: mp3 ([3][0][0][0] / 0x0003), 44100 Hz, mono, s16p, 
> 384 kb/s
> 

Re: [FFmpeg-devel] FFmpeg 3.2

[Andreas Cadhalpun]

Hi,

On 26.10.2016 21:29, Michael Niedermayer wrote:
> On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote:
>> 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

The following regressions from 3.1 should be fixed before releasing 3.2:
(They were detected by the Debian autopkgtest.)

 * apng creation is broken:
$ ./ffmpeg -f lavfi -i testsrc=s=32x32:d=0.1 -c:v apng -f apng apng.apng -y &> 
/dev/null
$ ./ffprobe ./apng.apng
ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
developers
  built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
  configuration: --disable-optimizations
  libavutil  55. 34.100 / 55. 34.100
  libavcodec 57. 64.100 / 57. 64.100
  libavformat57. 56.100 / 57. 56.100
  libavdevice57.  1.100 / 57.  1.100
  libavfilter 6. 65.100 /  6. 65.100
  libswscale  4.  2.100 /  4.  2.100
  libswresample   2.  3.100 /  2.  3.100
[png @ 0x29b02c0] IDAT without IHDR
[png_pipe @ 0x29ae7e0] decoding for stream 0 failed
[png_pipe @ 0x29ae7e0] Could not find codec parameters for stream 0 (Video: 
png, none(pc)): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Input #0, png_pipe, from './apng.apng':
  Duration: N/A, bitrate: N/A
Stream #0:0: Video: png, none(pc), 25 tbr, 25 tbn, 25 tbc

 * Probing of hls containing dts/eac3 doesn't work anymore:
$ ./ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a dca -f hls dca.hls -y &> 
/dev/null
$ ./ffprobe dca.hls
ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
developers
  built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
  configuration: --disable-optimizations
  libavutil  55. 34.100 / 55. 34.100
  libavcodec 57. 64.100 / 57. 64.100
  libavformat57. 56.100 / 57. 56.100
  libavdevice57.  1.100 / 57.  1.100
  libavfilter 6. 65.100 /  6. 65.100
  libswscale  4.  2.100 /  4.  2.100
  libswresample   2.  3.100 /  2.  3.100
[hls,applehttp @ 0x3dfd7e0] Could not find codec parameters for stream 0 
(Unknown: none ([130][0][0][0] / 0x0082)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Input #0, hls,applehttp, from 'dca.hls':
  Duration: 00:00:00.09, start: 1.40, bitrate: 9 kb/s
  Program 0 
Metadata:
  variant_bitrate : 0
Stream #0:0: Unknown: none ([130][0][0][0] / 0x0082)
Metadata:
  variant_bitrate : 0
Unsupported codec with id 0 for input stream 0

$ ./ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a eac3 -f hls eac3.hls -y &> 
/dev/null
$ ./ffprobe eac3.hls 
ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
developers
  built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
  configuration: --disable-optimizations
  libavutil  55. 34.100 / 55. 34.100
  libavcodec 57. 64.100 / 57. 64.100
  libavformat57. 56.100 / 57. 56.100
  libavdevice57.  1.100 / 57.  1.100
  libavfilter 6. 65.100 /  6. 65.100
  libswscale  4.  2.100 /  4.  2.100
  libswresample   2.  3.100 /  2.  3.100
Format mpegts detected only with low score of 2, misdetection possible!
[hls,applehttp @ 0x2d297e0] Could not find codec parameters for stream 0 
(Unknown: none ([135][0][0][0] / 0x0087)): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Input #0, hls,applehttp, from 'eac3.hls':
  Duration: 00:00:00.07, start: 1.40, bitrate: 13 kb/s
  Program 0 
Metadata:
  variant_bitrate : 0
Stream #0:0: Unknown: none ([135][0][0][0] / 0x0087)
Metadata:
  variant_bitrate : 0
Unsupported codec with id 0 for input stream 0

 * Probing of hls containing mp2 detects mp3:
$ ./ffmpeg -f lavfi -i sine=d=0.1 -strict -2 -c:a mp2 -f hls mp2.hls -y &> 
/dev/null
$ ./ffprobe mp2.hls 
ffprobe version n3.2-dev-1377-gebf8ec5 Copyright (c) 2007-2016 the FFmpeg 
developers
  built with gcc 6.2.0 (Debian 6.2.0-6) 20161010
  configuration: --disable-optimizations
  libavutil  55. 34.100 / 55. 34.100
  libavcodec 57. 64.100 / 57. 64.100
  libavformat57. 56.100 / 57. 56.100
  libavdevice57.  1.100 / 57.  1.100
  libavfilter 6. 65.100 /  6. 65.100
  libswscale  4.  2.100 /  4.  2.100
  libswresample   2.  3.100 /  2.  3.100
Input #0, hls,applehttp, from 'mp2.hls':
  Duration: 00:00:00.08, start: 1.40, bitrate: 11 kb/s
  Program 0 
Metadata:
  variant_bitrate : 0
Stream #0:0: Audio: mp3 ([3][0][0][0] / 0x0003), 44100 Hz, mono, s16p, 384 
kb/s
Metadata:
  variant_bitrate : 0

Best regards,
Andreas
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Stephen Hutchinson]

On 10/26/2016 10:45 PM, Michael Niedermayer wrote:

applied

you are maintainer of that file, you can send me your public ssh key
to get git write access, that would simplify your work maintaining
that file as you can push changes yourself



For something that would/will be so rarely changed and not changed
all that dramatically when it is, I really don't need (or want) to
have git write access.

Also, I've been having issues with the encryption protocols not
being set up correctly on my dev machine, so whether I'd even be
able to connect correctly is something I'd rather not worry about.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Wed, Oct 26, 2016 at 06:12:22PM -0400, Stephen Hutchinson wrote:
> On 10/26/2016 3:29 PM, Michael Niedermayer 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
> >
> >thx
> >[...]
> >
> >
> >
> >___
> >ffmpeg-devel mailing list
> >ffmpeg-devel@ffmpeg.org
> >http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >
> 
> I'd mentioned that https://patchwork.ffmpeg.org/patch/344/
> really needed to be committed before 3.2 was branched off,
> but if it goes in now it also needs to be backported.

applied

you are maintainer of that file, you can send me your public ssh key
to get git write access, that would simplify your work maintaining
that file as you can push changes yourself

thx

[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Stephen Hutchinson]

On 10/26/2016 3:29 PM, Michael Niedermayer 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

thx
[...]



___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel



I'd mentioned that https://patchwork.ffmpeg.org/patch/344/
really needed to be committed before 3.2 was branched off,
but if it goes in now it also needs to be backported.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

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

thx
[...]

-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

While the State exists there can be no freedom; when there is freedom there
will be no State. -- Vladimir Lenin


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[James Almer]

On 10/26/2016 5:44 PM, d...@dericed.com wrote:
> 
>> On Oct 26, 2016, at 3:29 PM, Michael Niedermayer  
>> 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
>  
> 
>  in 3.2. It resolves a regression added just before 3.2.
> Dave

I already cherry picked that commit for the 3.2 branch.
Pushed it to master and release/3.2 at the same time.

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[dave]

> On Oct 26, 2016, at 4:44 PM, d...@dericed.com wrote:
> 
> 
>> On Oct 26, 2016, at 3:29 PM, Michael Niedermayer > > 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
>  
> 
>  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 
.
Dave Rice

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[dave]

> On Oct 26, 2016, at 3:29 PM, Michael Niedermayer  
> 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
 

 in 3.2. It resolves a regression added just before 3.2.
Dave
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Helmut K. C. Tessarek]

On 2016-10-26 15:29, Michael Niedermayer wrote:
> 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

ffserver is still in that branch. I thought it would be removed from the
repo and the configure script. Or am I missing something?

Cheers,
  K. C.

-- 
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D

/*
   Thou shalt not follow the NULL pointer for chaos and madness
   await thee at its end.
*/
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Wed, Oct 26, 2016 at 05:07:44PM +0200, Carl Eugen Hoyos wrote:
> 2016-10-26 1:32 GMT+02:00 Michael Niedermayer :
> > On Wed, Sep 28, 2016 at 05:11:23PM +0200, Carl Eugen Hoyos wrote:
> >> 2016-09-27 15:30 GMT+02:00 Michael Niedermayer :
> >>
> >> > Its long since FFmpeg 3.1, so its time to make 3.2
> >>
> >> The configure option --enable-incompatible-libav-abi was intentionally
> >> broken some time ago, if it cannot get removed it should at least be
> >> removed from the help output.
> >
> > feel free to remove it, i dont have any references at hand to explain
> > it in the commit message
> 
> 655b6dcb, I had not remembered your review...

thx


[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Carl Eugen Hoyos]

2016-10-26 1:32 GMT+02:00 Michael Niedermayer :
> On Wed, Sep 28, 2016 at 05:11:23PM +0200, Carl Eugen Hoyos wrote:
>> 2016-09-27 15:30 GMT+02:00 Michael Niedermayer :
>>
>> > Its long since FFmpeg 3.1, so its time to make 3.2
>>
>> The configure option --enable-incompatible-libav-abi was intentionally
>> broken some time ago, if it cannot get removed it should at least be
>> removed from the help output.
>
> feel free to remove it, i dont have any references at hand to explain
> it in the commit message

655b6dcb, I had not remembered your review...

Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Wed, Sep 28, 2016 at 05:11:23PM +0200, Carl Eugen Hoyos wrote:
> 2016-09-27 15:30 GMT+02:00 Michael Niedermayer :
> 
> > Its long since FFmpeg 3.1, so its time to make 3.2
> 
> The configure option --enable-incompatible-libav-abi was intentionally
> broken some time ago, if it cannot get removed it should at least be
> removed from the help output.

feel free to remove it, i dont have any references at hand to explain
it in the commit message

thx

[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I am the wisest man alive, for I know one thing, and that is that I know
nothing. -- Socrates


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Carl Eugen Hoyos]

2016-10-17 0:01 GMT+02:00 Helmut K. C. Tessarek :
> On 2016-09-27 09:30, Michael Niedermayer wrote:
>> 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
>
> What happened to 3.2?

I believe developers still work on musl patches.

Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Mon, Oct 17, 2016 at 04:12:26PM +0200, Hendrik Leppkes wrote:
> On Mon, Oct 17, 2016 at 3:47 PM, Michael Niedermayer
>  wrote:
> > On Mon, Oct 17, 2016 at 12:01:56PM +0200, wm4 wrote:
> >> On Mon, 17 Oct 2016 04:24:40 +0200
> >> Michael Niedermayer  wrote:
> >>
> >> > On Sun, Oct 16, 2016 at 06:01:54PM -0400, Helmut K. C. Tessarek wrote:
> >> > > On 2016-09-27 09:30, Michael Niedermayer wrote:
> >> > > > 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
> >> > >
> >> > > What happened to 3.2?
> >> >
> >> > the AVFrame.pts field has been changed in master redefining ABI/API
> >> > without soname bump.
> >> >
> >> > this complicates the 3.2 release.
> >> > ATM we have 3.0 and 3.1 releases with the same sonames as git master
> >> > but they are not fully compatible due to the AVFrame.pts change
> >> > (on top of that i was a bit more busy with random stuff than i
> >> >  expected)
> >> >
> >> > the obvious solution is to bump major version of all libs. (this is
> >> > not wanted i belive though)
> >> >
> >> > the alternative is to remove the (useless) use of AVFrame.pts from
> >> > 3.0 and 3.1 and make new releases
> >> > then document in release notes that the 3.2 release cannot co-exist
> >> > with 3.0 or 3.1 prior to the last release and assume no other
> >> > application use AVFrame.pts
> >> >
> >> > Ill look at making the 3.0 and 3.1 release without AVFrame.pts use in
> >> > ffmpeg ASAP. These wont do any harm either way
> >> >
> >> > Maybe someone can write the release notes ?
> >> >
> >> > [...]
> >> >
> >>
> >> The change was backwards-compatible, as nobody should have used the pts
> >> field for decoding before.
> >
> > The field was a normal public and documented field
> > Documented in our public doxygen for 3.0 and 3.1
> > http://ffmpeg.org/doxygen/3.0/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
> > http://ffmpeg.org/doxygen/3.1/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
> >
> > The AVFrame.pts doxy links to examples, which use the field:
> > http://ffmpeg.org/doxygen/3.0/demuxing_decoding_8c-example.html#a41
> > http://ffmpeg.org/doxygen/3.1/demuxing_decoding_8c-example.html#a41
> >
> >
> 
> The documentation is hardly very enlightining on any level. Which
> time_base does it refer to, even? AVFrames can come from various
> sources, and there is various time_bases involved.

AVFrame was in libavcodec, there was just one timebase in libavcodec
when AVFrame was moved to libavutil the ambiguity of "what timebase"
was introduced


> Or why does it not
> document that its basically unused for decoding, and only used for
> encoding and filtering?
> Not to mention that the field was 99% of the time unset during
> decoding, and when it was set (by like 2 video decoders that didnt
> know any better), it was actually using the pkt timebase (ie. a clone
> of pkt_pts).

[...]

-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have often repented speaking, but never of holding my tongue.
-- Xenocrates


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Mon, Oct 17, 2016 at 03:56:37PM +0200, wm4 wrote:
> On Mon, 17 Oct 2016 15:47:06 +0200
> Michael Niedermayer  wrote:
> 
> > On Mon, Oct 17, 2016 at 12:01:56PM +0200, wm4 wrote:
> > > On Mon, 17 Oct 2016 04:24:40 +0200
> > > Michael Niedermayer  wrote:
> > >   
> > > > On Sun, Oct 16, 2016 at 06:01:54PM -0400, Helmut K. C. Tessarek wrote:  
> > > > > On 2016-09-27 09:30, Michael Niedermayer wrote:
> > > > > > 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
> > > > > 
> > > > > What happened to 3.2?
> > > > 
> > > > the AVFrame.pts field has been changed in master redefining ABI/API
> > > > without soname bump.
> > > > 
> > > > this complicates the 3.2 release.
> > > > ATM we have 3.0 and 3.1 releases with the same sonames as git master
> > > > but they are not fully compatible due to the AVFrame.pts change
> > > > (on top of that i was a bit more busy with random stuff than i
> > > >  expected)
> > > > 
> > > > the obvious solution is to bump major version of all libs. (this is
> > > > not wanted i belive though)
> > > > 
> > > > the alternative is to remove the (useless) use of AVFrame.pts from
> > > > 3.0 and 3.1 and make new releases
> > > > then document in release notes that the 3.2 release cannot co-exist
> > > > with 3.0 or 3.1 prior to the last release and assume no other
> > > > application use AVFrame.pts
> > > > 
> > > > Ill look at making the 3.0 and 3.1 release without AVFrame.pts use in
> > > > ffmpeg ASAP. These wont do any harm either way
> > > > 
> > > > Maybe someone can write the release notes ?
> > > > 
> > > > [...]
> > > >   
> > > 
> > > The change was backwards-compatible, as nobody should have used the pts
> > > field for decoding before.  
> > 
> > The field was a normal public and documented field
> > Documented in our public doxygen for 3.0 and 3.1
> > http://ffmpeg.org/doxygen/3.0/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
> > http://ffmpeg.org/doxygen/3.1/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
> > 
> > The AVFrame.pts doxy links to examples, which use the field:
> > http://ffmpeg.org/doxygen/3.0/demuxing_decoding_8c-example.html#a41
> > http://ffmpeg.org/doxygen/3.1/demuxing_decoding_8c-example.html#a41
> > 
> > 
> > > The fact that ffmpeg.c couldn't use its own
> > > API correctly is not of matter.  
> > 
> > 
> > [...]
> 
> This doesn't change anything about what I said. The example merely
> dumps some garbage values.
> 

> How do you expect downstream code to break with the change, and which
> actual downstream projects do break?

I hope none break, what might happen though is
the way ffmpeg.c breaks if i put the AVFrame.pts code back and
run "make fate"

This is the one specific breakage i know of.


[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have often repented speaking, but never of holding my tongue.
-- Xenocrates


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Hendrik Leppkes]

On Mon, Oct 17, 2016 at 3:47 PM, Michael Niedermayer
 wrote:
> On Mon, Oct 17, 2016 at 12:01:56PM +0200, wm4 wrote:
>> On Mon, 17 Oct 2016 04:24:40 +0200
>> Michael Niedermayer  wrote:
>>
>> > On Sun, Oct 16, 2016 at 06:01:54PM -0400, Helmut K. C. Tessarek wrote:
>> > > On 2016-09-27 09:30, Michael Niedermayer wrote:
>> > > > 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
>> > >
>> > > What happened to 3.2?
>> >
>> > the AVFrame.pts field has been changed in master redefining ABI/API
>> > without soname bump.
>> >
>> > this complicates the 3.2 release.
>> > ATM we have 3.0 and 3.1 releases with the same sonames as git master
>> > but they are not fully compatible due to the AVFrame.pts change
>> > (on top of that i was a bit more busy with random stuff than i
>> >  expected)
>> >
>> > the obvious solution is to bump major version of all libs. (this is
>> > not wanted i belive though)
>> >
>> > the alternative is to remove the (useless) use of AVFrame.pts from
>> > 3.0 and 3.1 and make new releases
>> > then document in release notes that the 3.2 release cannot co-exist
>> > with 3.0 or 3.1 prior to the last release and assume no other
>> > application use AVFrame.pts
>> >
>> > Ill look at making the 3.0 and 3.1 release without AVFrame.pts use in
>> > ffmpeg ASAP. These wont do any harm either way
>> >
>> > Maybe someone can write the release notes ?
>> >
>> > [...]
>> >
>>
>> The change was backwards-compatible, as nobody should have used the pts
>> field for decoding before.
>
> The field was a normal public and documented field
> Documented in our public doxygen for 3.0 and 3.1
> http://ffmpeg.org/doxygen/3.0/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
> http://ffmpeg.org/doxygen/3.1/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
>
> The AVFrame.pts doxy links to examples, which use the field:
> http://ffmpeg.org/doxygen/3.0/demuxing_decoding_8c-example.html#a41
> http://ffmpeg.org/doxygen/3.1/demuxing_decoding_8c-example.html#a41
>
>

The documentation is hardly very enlightining on any level. Which
time_base does it refer to, even? AVFrames can come from various
sources, and there is various time_bases involved. Or why does it not
document that its basically unused for decoding, and only used for
encoding and filtering?
Not to mention that the field was 99% of the time unset during
decoding, and when it was set (by like 2 video decoders that didnt
know any better), it was actually using the pkt timebase (ie. a clone
of pkt_pts).

- Hendrik
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[wm4]

On Mon, 17 Oct 2016 15:47:06 +0200
Michael Niedermayer  wrote:

> On Mon, Oct 17, 2016 at 12:01:56PM +0200, wm4 wrote:
> > On Mon, 17 Oct 2016 04:24:40 +0200
> > Michael Niedermayer  wrote:
> >   
> > > On Sun, Oct 16, 2016 at 06:01:54PM -0400, Helmut K. C. Tessarek wrote:  
> > > > On 2016-09-27 09:30, Michael Niedermayer wrote:
> > > > > 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
> > > > 
> > > > What happened to 3.2?
> > > 
> > > the AVFrame.pts field has been changed in master redefining ABI/API
> > > without soname bump.
> > > 
> > > this complicates the 3.2 release.
> > > ATM we have 3.0 and 3.1 releases with the same sonames as git master
> > > but they are not fully compatible due to the AVFrame.pts change
> > > (on top of that i was a bit more busy with random stuff than i
> > >  expected)
> > > 
> > > the obvious solution is to bump major version of all libs. (this is
> > > not wanted i belive though)
> > > 
> > > the alternative is to remove the (useless) use of AVFrame.pts from
> > > 3.0 and 3.1 and make new releases
> > > then document in release notes that the 3.2 release cannot co-exist
> > > with 3.0 or 3.1 prior to the last release and assume no other
> > > application use AVFrame.pts
> > > 
> > > Ill look at making the 3.0 and 3.1 release without AVFrame.pts use in
> > > ffmpeg ASAP. These wont do any harm either way
> > > 
> > > Maybe someone can write the release notes ?
> > > 
> > > [...]
> > >   
> > 
> > The change was backwards-compatible, as nobody should have used the pts
> > field for decoding before.  
> 
> The field was a normal public and documented field
> Documented in our public doxygen for 3.0 and 3.1
> http://ffmpeg.org/doxygen/3.0/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
> http://ffmpeg.org/doxygen/3.1/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
> 
> The AVFrame.pts doxy links to examples, which use the field:
> http://ffmpeg.org/doxygen/3.0/demuxing_decoding_8c-example.html#a41
> http://ffmpeg.org/doxygen/3.1/demuxing_decoding_8c-example.html#a41
> 
> 
> > The fact that ffmpeg.c couldn't use its own
> > API correctly is not of matter.  
> 
> 
> [...]

This doesn't change anything about what I said. The example merely
dumps some garbage values.

How do you expect downstream code to break with the change, and which
actual downstream projects do break?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Mon, Oct 17, 2016 at 12:01:56PM +0200, wm4 wrote:
> On Mon, 17 Oct 2016 04:24:40 +0200
> Michael Niedermayer  wrote:
> 
> > On Sun, Oct 16, 2016 at 06:01:54PM -0400, Helmut K. C. Tessarek wrote:
> > > On 2016-09-27 09:30, Michael Niedermayer wrote:  
> > > > 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  
> > > 
> > > What happened to 3.2?  
> > 
> > the AVFrame.pts field has been changed in master redefining ABI/API
> > without soname bump.
> > 
> > this complicates the 3.2 release.
> > ATM we have 3.0 and 3.1 releases with the same sonames as git master
> > but they are not fully compatible due to the AVFrame.pts change
> > (on top of that i was a bit more busy with random stuff than i
> >  expected)
> > 
> > the obvious solution is to bump major version of all libs. (this is
> > not wanted i belive though)
> > 
> > the alternative is to remove the (useless) use of AVFrame.pts from
> > 3.0 and 3.1 and make new releases
> > then document in release notes that the 3.2 release cannot co-exist
> > with 3.0 or 3.1 prior to the last release and assume no other
> > application use AVFrame.pts
> > 
> > Ill look at making the 3.0 and 3.1 release without AVFrame.pts use in
> > ffmpeg ASAP. These wont do any harm either way
> > 
> > Maybe someone can write the release notes ?
> > 
> > [...]
> > 
> 
> The change was backwards-compatible, as nobody should have used the pts
> field for decoding before.

The field was a normal public and documented field
Documented in our public doxygen for 3.0 and 3.1
http://ffmpeg.org/doxygen/3.0/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4
http://ffmpeg.org/doxygen/3.1/structAVFrame.html#a0452833e3ab6ddd7acbf82817a7818a4

The AVFrame.pts doxy links to examples, which use the field:
http://ffmpeg.org/doxygen/3.0/demuxing_decoding_8c-example.html#a41
http://ffmpeg.org/doxygen/3.1/demuxing_decoding_8c-example.html#a41


> The fact that ffmpeg.c couldn't use its own
> API correctly is not of matter.


[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Concerning the gods, I have no means of knowing whether they exist or not
or of what sort they may be, because of the obscurity of the subject, and
the brevity of human life -- Protagoras


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[wm4]

On Mon, 17 Oct 2016 04:24:40 +0200
Michael Niedermayer  wrote:

> On Sun, Oct 16, 2016 at 06:01:54PM -0400, Helmut K. C. Tessarek wrote:
> > On 2016-09-27 09:30, Michael Niedermayer wrote:  
> > > 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  
> > 
> > What happened to 3.2?  
> 
> the AVFrame.pts field has been changed in master redefining ABI/API
> without soname bump.
> 
> this complicates the 3.2 release.
> ATM we have 3.0 and 3.1 releases with the same sonames as git master
> but they are not fully compatible due to the AVFrame.pts change
> (on top of that i was a bit more busy with random stuff than i
>  expected)
> 
> the obvious solution is to bump major version of all libs. (this is
> not wanted i belive though)
> 
> the alternative is to remove the (useless) use of AVFrame.pts from
> 3.0 and 3.1 and make new releases
> then document in release notes that the 3.2 release cannot co-exist
> with 3.0 or 3.1 prior to the last release and assume no other
> application use AVFrame.pts
> 
> Ill look at making the 3.0 and 3.1 release without AVFrame.pts use in
> ffmpeg ASAP. These wont do any harm either way
> 
> Maybe someone can write the release notes ?
> 
> [...]
> 

The change was backwards-compatible, as nobody should have used the pts
field for decoding before. The fact that ffmpeg.c couldn't use its own
API correctly is not of matter.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

On Sun, Oct 16, 2016 at 06:01:54PM -0400, Helmut K. C. Tessarek wrote:
> On 2016-09-27 09:30, Michael Niedermayer wrote:
> > 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
> 
> What happened to 3.2?

the AVFrame.pts field has been changed in master redefining ABI/API
without soname bump.

this complicates the 3.2 release.
ATM we have 3.0 and 3.1 releases with the same sonames as git master
but they are not fully compatible due to the AVFrame.pts change
(on top of that i was a bit more busy with random stuff than i
 expected)

the obvious solution is to bump major version of all libs. (this is
not wanted i belive though)

the alternative is to remove the (useless) use of AVFrame.pts from
3.0 and 3.1 and make new releases
then document in release notes that the 3.2 release cannot co-exist
with 3.0 or 3.1 prior to the last release and assume no other
application use AVFrame.pts

Ill look at making the 3.0 and 3.1 release without AVFrame.pts use in
ffmpeg ASAP. These wont do any harm either way

Maybe someone can write the release notes ?

[...]

-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

You can kill me, but you cannot change the truth.


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Helmut K. C. Tessarek]

On 2016-09-27 09:30, Michael Niedermayer wrote:
> 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

What happened to 3.2?

Cheers,
  K. C.

-- 
regards Helmut K. C. Tessarek
lookup http://sks.pkqs.net for KeyID 0xC11F128D

/*
   Thou shalt not follow the NULL pointer for chaos and madness
   await thee at its end.
*/




signature.asc
Description: OpenPGP digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Helmut K. C. Tessarek]

binp92P_YWvzj.bin
Description: PGP/MIME version identification


encrypted.asc
Description: OpenPGP encrypted message
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Carl Eugen Hoyos]

2016-09-27 15:30 GMT+02:00 Michael Niedermayer :

> Its long since FFmpeg 3.1, so its time to make 3.2

The configure option --enable-incompatible-libav-abi was intentionally
broken some time ago, if it cannot get removed it should at least be
removed from the help output.

Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Timo Rothenpieler]

Am 27.09.2016 um 15:30 schrieb Michael Niedermayer:
> 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

Should ffserver be deprecated for 3.2, or will it be resurrected now?
I'm all for deprecating it. Can always un-deprecate it if something
happens about it, nobody going to complain about that.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Lou Logan]

On Tue, 27 Sep 2016 15:30:03 +0200, Michael Niedermayer wrote:

> also a name needs to be choosen

Plenty of suggestions from the previous release:


I think Kyle had a good suggestion:


Perhaps it's time for a Release Name Suggestions wiki page.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] FFmpeg 3.2

[Sven C. Dack]

On 27/09/16 14:30, 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

also a name needs to be choosen

Thanks


I narrowed it down for myself to Trump, Clinton and Fourier.

Hope this helps.

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] FFmpeg 3.2

[Michael Niedermayer]

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

also a name needs to be choosen

Thanks
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Democracy is the form of government in which you can choose your dictator


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel