Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-04-13 Thread Michael Niedermayer
On Sun, Apr 02, 2017 at 09:15:00PM +0200, Michael Niedermayer wrote: > On Sat, Apr 01, 2017 at 09:17:00PM +0200, Marton Balint wrote: > > > > On Fri, 31 Mar 2017, James Almer wrote: > > > > >Now, regarding merges, we're like 10 commits away from the massive > > >bitstream reader batch, which is m

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-04-03 Thread Carl Eugen Hoyos
2017-04-02 21:15 GMT+02:00 Michael Niedermayer : > i intend to make 3.3 from this branch within a few days Please wait for a resolution for the decklink license issue: Either the library is free (as explained here) or non-free as was claimed on the Debian bugtracker. Carl Eugen _

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-04-02 Thread Michael Niedermayer
On Sat, Apr 01, 2017 at 09:17:00PM +0200, Marton Balint wrote: > > On Fri, 31 Mar 2017, James Almer wrote: > > >Now, regarding merges, we're like 10 commits away from the massive > >bitstream reader batch, which is more or less the only thing committed > >to libav for a whole week. So how about w

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-04-01 Thread Marton Balint
On Fri, 31 Mar 2017, James Almer wrote: Now, regarding merges, we're like 10 commits away from the massive bitstream reader batch, which is more or less the only thing committed to libav for a whole week. So how about we re-cut from master (should be a matter of merging master into release/3.3,

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Michael Niedermayer
On Fri, Mar 31, 2017 at 08:04:46PM -0300, James Almer wrote: > On 3/31/2017 6:42 PM, James Almer wrote: > > On 3/31/2017 3:19 PM, Michael Niedermayer wrote: > >> On Fri, Mar 31, 2017 at 03:07:15PM +0200, Michael Niedermayer wrote: > >>> On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread James Almer
On 3/31/2017 6:42 PM, James Almer wrote: > On 3/31/2017 3:19 PM, Michael Niedermayer wrote: >> On Fri, Mar 31, 2017 at 03:07:15PM +0200, Michael Niedermayer wrote: >>> On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote: On Tue, Mar 14, 2017 at 12:29:52PM +0100, Michael Niederm

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread James Almer
On 3/31/2017 3:19 PM, Michael Niedermayer wrote: > On Fri, Mar 31, 2017 at 03:07:15PM +0200, Michael Niedermayer wrote: >> On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote: >>> On Tue, Mar 14, 2017 at 12:29:52PM +0100, Michael Niedermayer wrote: Hi all are there an

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Michael Niedermayer
On Fri, Mar 31, 2017 at 03:07:15PM +0200, Michael Niedermayer wrote: > On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote: > > 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 ? > > >

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Kieran Kunhya
> > also what exactly is broken with teh current tree that will be better > in a month and was better 3 weeks ago ? > Is that known ? or is it just "there were lots of chnages, things may > be broken" ? > > all just some randdom comments so myself and also others better > understand what the issue

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Reto Kromer
Steven Liu wrote: >> should we make a 3.3 release from >>0bab78f7e729a76ea7a8cbec7f1de033c52494e8 >> that is 3 weeks ago with backports ? >> >I think this point maybe better, and stable than another >two. +1 ___ ffmpeg-devel mailing list ffmpeg-devel@f

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Michael Niedermayer
On Fri, Mar 31, 2017 at 03:19:01PM +0200, Clément Bœsch wrote: > On Fri, Mar 31, 2017 at 03:07:15PM +0200, Michael Niedermayer wrote: > > On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote: > > > On Tue, Mar 14, 2017 at 12:29:52PM +0100, Michael Niedermayer wrote: > > > > Hi all >

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Clément Bœsch
On Fri, Mar 31, 2017 at 03:07:15PM +0200, Michael Niedermayer wrote: > On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote: > > 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 ? > > >

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Steven Liu
2017-03-31 21:07 GMT+08:00 Michael Niedermayer : > On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote: > > 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

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

2017-03-31 Thread Michael Niedermayer
On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote: > 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 b