Re: [FFmpeg-devel] FFmpeg 3.3

2017-04-05 Thread Nicolas George
Le sextidi 16 germinal, an CCXXV, James Almer a écrit : > Apparently, av_strreplace didn't even get a version bump or an > APIChanges line. This whole situation has been was overall pretty > sloppy. I do not see the point of throwing even more blame around; what is done is done. > I don't know

Re: [FFmpeg-devel] FFmpeg 3.3

2017-04-05 Thread James Almer
On 4/5/2017 2:18 PM, Nicolas George wrote: > Le quartidi 24 ventôse, an CCXXV, Michael Niedermayer a écrit : >> are there any issues/tickets that block making 3.3 ? > > There is the issue of av_strreplace() / av_strireplace() that needs to > be decided and then possibly backported. > > Regardss,

Re: [FFmpeg-devel] FFmpeg 3.3

2017-04-05 Thread Nicolas George
Le quartidi 24 ventôse, an CCXXV, Michael Niedermayer a écrit : > are there any issues/tickets that block making 3.3 ? There is the issue of av_strreplace() / av_strireplace() that needs to be decided and then possibly backported. Regardss, -- Nicolas George

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-31 Thread Carl Eugen Hoyos
2017-04-01 0:51 GMT+02:00 Hendrik Leppkes : > On Sat, Apr 1, 2017 at 12:39 AM, Carl Eugen Hoyos wrote: >> 2017-03-14 12:29 GMT+01:00 Michael Niedermayer : >> >>> are there any issues/tickets that block making 3.3 ? >> >> What is the

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-31 Thread Hendrik Leppkes
On Sat, Apr 1, 2017 at 12:39 AM, Carl Eugen Hoyos wrote: > 2017-03-14 12:29 GMT+01:00 Michael Niedermayer : > >> are there any issues/tickets that block making 3.3 ? > > What is the license of avisynth / avxsynth? > If it is GPL (as I suspect) or less

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-31 Thread Carl Eugen Hoyos
2017-03-14 12:29 GMT+01:00 Michael Niedermayer : > are there any issues/tickets that block making 3.3 ? What is the license of avisynth / avxsynth? If it is GPL (as I suspect) or less permissive we should not immediately make a release imo. Carl Eugen

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-31 Thread Michael Niedermayer
On Tue, Mar 14, 2017 at 12:29:52PM +0100, Michael Niedermayer wrote: > Hi all > > are there any issues/tickets that block making 3.3 ? > > What about the spherical API size_t / uint32_t issue ? > we can change it before the release but not after it Ive finally branched release/3.3 off feel free

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-15 Thread wm4
On Tue, 14 Mar 2017 12:29:52 +0100 Michael Niedermayer wrote: > Hi all > > are there any issues/tickets that block making 3.3 ? > > What about the spherical API size_t / uint32_t issue ? > we can change it before the release but not after it > I will insist that

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread Hendrik Leppkes
On Tue, Mar 14, 2017 at 6:18 PM, wm4 wrote: > >> Now back to the current issue. >> >> Do you agree with the fact that uint32_t is a better technical choice? >> (I think the main argument is that it's a pain to have proper FATE >> coverage if you don't?) > > We've already

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread wm4
On Tue, 14 Mar 2017 17:59:38 +0100 Clément Bœsch wrote: > On Tue, Mar 14, 2017 at 05:33:41PM +0100, wm4 wrote: > > On Tue, 14 Mar 2017 17:02:34 +0100 > > Hendrik Leppkes wrote: > > > > > On Tue, Mar 14, 2017 at 4:49 PM, wm4 wrote: >

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread wm4
On Tue, 14 Mar 2017 13:50:53 -0300 James Almer wrote: > On 3/14/2017 1:33 PM, wm4 wrote: > > On Tue, 14 Mar 2017 17:02:34 +0100 > > Hendrik Leppkes wrote: > > > >> On Tue, Mar 14, 2017 at 4:49 PM, wm4 wrote: > >>> On Tue, 14

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread Clément Bœsch
On Tue, Mar 14, 2017 at 05:33:41PM +0100, wm4 wrote: > On Tue, 14 Mar 2017 17:02:34 +0100 > Hendrik Leppkes wrote: > > > On Tue, Mar 14, 2017 at 4:49 PM, wm4 wrote: > > > On Tue, 14 Mar 2017 14:19:24 + > > > Rostislav Pehlivanov

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread James Almer
On 3/14/2017 1:33 PM, wm4 wrote: > On Tue, 14 Mar 2017 17:02:34 +0100 > Hendrik Leppkes wrote: > >> On Tue, Mar 14, 2017 at 4:49 PM, wm4 wrote: >>> On Tue, 14 Mar 2017 14:19:24 + >>> Rostislav Pehlivanov wrote: >>> On

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread wm4
On Tue, 14 Mar 2017 17:02:34 +0100 Hendrik Leppkes wrote: > On Tue, Mar 14, 2017 at 4:49 PM, wm4 wrote: > > On Tue, 14 Mar 2017 14:19:24 + > > Rostislav Pehlivanov wrote: > > > >> On 14 March 2017 at 13:38, wm4

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread wm4
On Tue, 14 Mar 2017 14:19:24 + Rostislav Pehlivanov wrote: > On 14 March 2017 at 13:38, wm4 wrote: > > > On Tue, 14 Mar 2017 10:24:10 -0300 > > James Almer wrote: > > > > > On 3/14/2017 9:31 AM, Rostislav Pehlivanov wrote:

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread Rostislav Pehlivanov
On 14 March 2017 at 13:38, wm4 wrote: > On Tue, 14 Mar 2017 10:24:10 -0300 > James Almer wrote: > > > On 3/14/2017 9:31 AM, Rostislav Pehlivanov wrote: > > > On 14 March 2017 at 11:29, Michael Niedermayer > > > > wrote: > > > >

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread wm4
On Tue, 14 Mar 2017 10:24:10 -0300 James Almer wrote: > On 3/14/2017 9:31 AM, Rostislav Pehlivanov wrote: > > On 14 March 2017 at 11:29, Michael Niedermayer > > wrote: > > > >> > >> What about the spherical API size_t / uint32_t issue ? > >> we can

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread James Almer
On 3/14/2017 9:31 AM, Rostislav Pehlivanov wrote: > On 14 March 2017 at 11:29, Michael Niedermayer > wrote: > >> >> What about the spherical API size_t / uint32_t issue ? >> we can change it before the release but not after it >> >> > IMO its better to have the same type

Re: [FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread Rostislav Pehlivanov
On 14 March 2017 at 11:29, Michael Niedermayer wrote: > > What about the spherical API size_t / uint32_t issue ? > we can change it before the release but not after it > > IMO its better to have the same type on all platforms. It also doesn't make sense to use size_t for

[FFmpeg-devel] FFmpeg 3.3

2017-03-14 Thread Michael Niedermayer
Hi all are there any issues/tickets that block making 3.3 ? What about the spherical API size_t / uint32_t issue ? we can change it before the release but not after it Thanks -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I am the wisest man alive, for I know one

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-25 Thread Bodecs Bela
2017.01.25. 9:40 keltezéssel, Tobias Rapp írta: On 23.01.2017 02:11, Michael Niedermayer wrote: Its a while since the last relase so ill make 3.3 within the next week(s) Name suggestions needed like always What about "Hilbert", named after David Hilbert? +1 vote I also intend to make

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-25 Thread Carl Eugen Hoyos
2017-01-25 12:09 GMT+01:00 Tobias Rapp : > Not sure about your definition of "regression". An issue that was not reproducible with earlier versions (of FFmpeg). > The given scenario works for FFmpeg <= 2.6 but fails with > versions between 2.7 and 3.2. Then the patch

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-25 Thread Tobias Rapp
On 25.01.2017 11:59, Carl Eugen Hoyos wrote: 2017-01-25 11:47 GMT+01:00 Tobias Rapp : On 25.01.2017 11:23, Carl Eugen Hoyos wrote: 2017-01-25 9:40 GMT+01:00 Tobias Rapp : If not already done, please backport commit

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-25 Thread Carl Eugen Hoyos
2017-01-25 11:47 GMT+01:00 Tobias Rapp : > On 25.01.2017 11:23, Carl Eugen Hoyos wrote: >> >> 2017-01-25 9:40 GMT+01:00 Tobias Rapp : >> >>> If not already done, please backport commit >>> http://git.videolan.org/?p=ffmpeg.git;a=commit;h=6d579d7c >>

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-25 Thread Tobias Rapp
On 25.01.2017 11:23, Carl Eugen Hoyos wrote: 2017-01-25 9:40 GMT+01:00 Tobias Rapp : If not already done, please backport commit http://git.videolan.org/?p=ffmpeg.git;a=commit;h=6d579d7c This doesn't look as if it fixes a regression, does it? It fixes the scenario

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-25 Thread Carl Eugen Hoyos
2017-01-25 9:40 GMT+01:00 Tobias Rapp : > If not already done, please backport commit > http://git.videolan.org/?p=ffmpeg.git;a=commit;h=6d579d7c This doesn't look as if it fixes a regression, does it? Carl Eugen ___

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-25 Thread Tobias Rapp
On 23.01.2017 02:11, Michael Niedermayer wrote: Its a while since the last relase so ill make 3.3 within the next week(s) Name suggestions needed like always What about "Hilbert", named after David Hilbert? I also intend to make some new point releases from the currently maintained branches

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-23 Thread Michael Niedermayer
On Mon, Jan 23, 2017 at 07:07:55AM +0100, Reto Kromer wrote: > Michael Niedermayer wrote: > > >Its a while since the last relase so ill make 3.3 within > >the next week(s) > > Thank you, Michael! > > >I also intend to make some new point releases from the > >currently maintained branches if

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-22 Thread Jörn Heusipp
On 01/23/2017 02:11 AM, Michael Niedermayer wrote: I also intend to make some new point releases from the currently maintained branches if someone wants to backport something https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/367cac7827870054ae3bd6d4517e7b13f4f3f72c needs to be applied to the

Re: [FFmpeg-devel] FFmpeg 3.3

2017-01-22 Thread Reto Kromer
Michael Niedermayer wrote: >Its a while since the last relase so ill make 3.3 within >the next week(s) Thank you, Michael! >I also intend to make some new point releases from the >currently maintained branches if someone wants to backport >something I suggest to switch "Nash" 2.7.7 to the old

[FFmpeg-devel] FFmpeg 3.3

2017-01-22 Thread Michael Niedermayer
Hi all Its a while since the last relase so ill make 3.3 within the next week(s) Name suggestions needed like always I also intend to make some new point releases from the currently maintained branches if someone wants to backport something thx -- Michael GnuPG fingerprint: