Re: [libav-devel] [PATCH] vpx: Support color range

2016-07-22 Thread Vittorio Giovara
On Fri, Jul 22, 2016 at 9:33 AM, Luca Barbato wrote: > The range field has been introduced in version 1.6.0 > --- > libavcodec/libvpxdec.c | 10 ++ > libavcodec/libvpxenc.c | 10 ++ > 2 files changed, 20 insertions(+) > > diff --git a/libavcodec/libvpxdec.c

[libav-devel] [PATCH] vpx: Support color range

2016-07-22 Thread Luca Barbato
The range field has been introduced in version 1.6.0 --- libavcodec/libvpxdec.c | 10 ++ libavcodec/libvpxenc.c | 10 ++ 2 files changed, 20 insertions(+) diff --git a/libavcodec/libvpxdec.c b/libavcodec/libvpxdec.c index 28b7733..93a720f 100644 --- a/libavcodec/libvpxdec.c +++

Re: [libav-devel] [PATCH] Revert "avprobe: Zero the allocated avio buffer memory"

2016-07-22 Thread Martin Storsjö
On Fri, 22 Jul 2016, Luca Barbato wrote: On 22/07/16 08:05, Martin Storsjö wrote: Feel free to send patches to valgrind about it, but not here. Reporting at least the bug would be nice, I guess? Yes, that'd be good ofc. // Martin ___ libav-devel

Re: [libav-devel] [PATCH] checkasm: add HEVC test for testing IDCT DC

2016-07-22 Thread Luca Barbato
On 21/07/16 16:32, Alexandra Hájková wrote: > --- > remove unused headers, > reorder the remaining ones > order hevc_idct in checkasm.h properly > > tests/checkasm/Makefile| 2 +- > tests/checkasm/checkasm.c | 1 + > tests/checkasm/checkasm.h | 1 + > tests/checkasm/hevc_idct.c | 73 >

Re: [libav-devel] [PATCH] Revert "avprobe: Zero the allocated avio buffer memory"

2016-07-22 Thread Luca Barbato
On 22/07/16 08:05, Martin Storsjö wrote: > Feel free to send patches to valgrind about it, but not here. Reporting at least the bug would be nice, I guess? lu ___ libav-devel mailing list libav-devel@libav.org

Re: [libav-devel] [PATCH] Revert "avprobe: Zero the allocated avio buffer memory"

2016-07-22 Thread Martin Storsjö
On Fri, 22 Jul 2016, Luca Barbato wrote: On 21/07/16 21:45, Vittorio Giovara wrote: This reverts commit 0e0538aefc75958ded49f5d075c99a81cf6b2bbb. The valgrind warning was a false positive due to OSX implementation of printf (invoking a strlen), while this code is actually fine, since the