2017-02-15 12:00 GMT+01:00 wm4 :
> On Wed, 15 Feb 2017 11:48:36 +0100
> Carl Eugen Hoyos wrote:
>
>> 2017-02-14 14:08 GMT+01:00 Michael Niedermayer :
>> > My concern are the growing number of regressions
>>
>> > (which implies more get added than fixed).
>>
>> From a purely quantitative pov this i
On Wed, 15 Feb 2017 11:48:36 +0100
Carl Eugen Hoyos wrote:
> 2017-02-14 14:08 GMT+01:00 Michael Niedermayer :
> > My concern are the growing number of regressions
>
> > (which implies more get added than fixed).
>
> From a purely quantitative pov this is correct.
Do you propose we should r
2017-02-14 14:08 GMT+01:00 Michael Niedermayer :
> My concern are the growing number of regressions
> (which implies more get added than fixed).
From a purely quantitative pov this is correct.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpe
On Mon, Feb 13, 2017 at 06:27:50AM +0100, wm4 wrote:
> On Fri, 10 Feb 2017 22:43:26 +0100
> Michael Niedermayer wrote:
>
> > On Fri, Feb 10, 2017 at 01:35:34PM +0100, wm4 wrote:
> > > From: Anton Khirnov
> > >
> > > This will be useful in the following commit, after which the muxer
> > > timeba
On Fri, 10 Feb 2017 22:43:26 +0100
Michael Niedermayer wrote:
> On Fri, Feb 10, 2017 at 01:35:34PM +0100, wm4 wrote:
> > From: Anton Khirnov
> >
> > This will be useful in the following commit, after which the muxer
> > timebase is not always available when encoding.
> >
> > This merges Libav
On Fri, Feb 10, 2017 at 01:35:34PM +0100, wm4 wrote:
> From: Anton Khirnov
>
> This will be useful in the following commit, after which the muxer
> timebase is not always available when encoding.
>
> This merges Libav commit 3e265ca. It was previously skipped.
>
> There is a minor change with s
From: Anton Khirnov
This will be useful in the following commit, after which the muxer
timebase is not always available when encoding.
This merges Libav commit 3e265ca. It was previously skipped.
There is a minor change with setting the mux_timebase field only after
the muxer's write_header fun
