Signed-off-by: Paul B Mahol
---
libavfilter/avf_showspectrum.c | 121 ++---
1 file changed, 66 insertions(+), 55 deletions(-)
diff --git a/libavfilter/avf_showspectrum.c b/libavfilter/avf_showspectrum.c
index f5e8561713..30238e0c3f 100644
--- a/libavfilter/avf_showspe
Signed-off-by: Paul B Mahol
---
libavfilter/avf_showspectrum.c | 31 +++
1 file changed, 23 insertions(+), 8 deletions(-)
diff --git a/libavfilter/avf_showspectrum.c b/libavfilter/avf_showspectrum.c
index 30238e0c3f..9e268f9d33 100644
--- a/libavfilter/avf_showspectru
> Is it intended that this doesnt list a human name ?
> (its no problem but jb tends to be unhappy if there are no names in the
log
> so i try to ask people if they really intend to not list their name or if
> its a unintended mistake)
It's the nick/mail I use in github and other places, it's corr
> This will/would require several fate tests to be updated
> at least these apparently:
> make: *** [fate-wmav1-encode] Error 1
> make: *** [fate-wmav2-encode] Error 1
> make: *** [fate-flcl1905] Error 1
I'm not sure if I can and how to modify those, somebody could lend a hand?
I can run the tests
On 05/10/18 00:39, James Almer wrote:
> On 10/4/2018 8:09 PM, Mark Thompson wrote:
>> ---
>> libavcodec/trace_headers_bsf.c | 14 --
>> 1 file changed, 4 insertions(+), 10 deletions(-)
>>
>> diff --git a/libavcodec/trace_headers_bsf.c b/libavcodec/trace_headers_bsf.c
>> index 94a3ef72a
---
On 05/10/18 00:53, James Almer wrote:
> On 10/4/2018 8:09 PM, Mark Thompson wrote:
>> ---
>> configure | 10 +++---
>> 1 file changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/configure b/configure
>> index 85d5dd5962..cbd52e641b 100755
>> --- a/configure
>> +++ b/configure
>> @@
On 05/10/18 21:45, Alex Sukhanov wrote:
> On Mon, Oct 1, 2018 at 11:01 AM wrote:
>
>> From: Alex Sukhanov
>>
>> ---
>> libavformat/ivfenc.c | 50 +---
>> 1 file changed, 38 insertions(+), 12 deletions(-)
>>
>> diff --git a/libavformat/ivfenc.c b/libavform
On 10/6/2018 2:30 PM, Mark Thompson wrote:
> ---
> On 05/10/18 00:53, James Almer wrote:
>> On 10/4/2018 8:09 PM, Mark Thompson wrote:
>>> ---
>>> configure | 10 +++---
>>> 1 file changed, 7 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/configure b/configure
>>> index 85d5dd5962..cbd52e6
On Sat, Oct 06, 2018 at 04:53:31PM +0200, Banana M. wrote:
> > Is it intended that this doesnt list a human name ?
> > (its no problem but jb tends to be unhappy if there are no names in the
> log
> > so i try to ask people if they really intend to not list their name or if
> > its a unintended mis
On Sat, Oct 06, 2018 at 05:00:13PM +0200, Banana M. wrote:
> > This will/would require several fate tests to be updated
> > at least these apparently:
> > make: *** [fate-wmav1-encode] Error 1
> > make: *** [fate-wmav2-encode] Error 1
> > make: *** [fate-flcl1905] Error 1
>
> I'm not sure if I can
On Sat, Sep 22, 2018 at 03:18:17PM +0200, Michael Niedermayer wrote:
> Found-by: kierank
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/unary.h | 15 ++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
will apply
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730B
On Wed, Sep 19, 2018 at 06:05:23PM +0200, Michael Niedermayer wrote:
> This was the only case in the source that uses a hexadecimal shift value.
> The change removed a special case in respect to greping
>
> Signed-off-by: Michael Niedermayer
> ---
> libavformat/ty.c | 2 +-
> 1 file changed, 1 i
On Wed, Sep 26, 2018 at 07:15:36PM -0300, James Almer wrote:
> On 9/26/2018 7:00 PM, Michael Niedermayer wrote:
> > This avoids surprising developers. Its bad to surprise developers with
> > such unexpected things.
> >
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavformat/utils.c | 42 +
On Wed, Sep 26, 2018 at 07:12:13PM -0300, James Almer wrote:
> On 9/26/2018 7:00 PM, Michael Niedermayer wrote:
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavformat/utils.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/libavformat/utils.c b/libavform
The latest generation video decoder on the Turing chips supports
decoding HEVC 4:4:4. Supporting this is relatively straight-forward;
we need to account for the different chroma format and pick the
right output and sw formats at the right times.
There was one bug which was the hard-coded assumptio
15 matches
Mail list logo