On Sat, Apr 8, 2017 at 9:56 AM, Muhammad Faiz wrote:
> Signed-off-by: Muhammad Faiz
> ---
> doc/filters.texi | 5 +
> libavfilter/avf_showcqt.c | 39 ---
> libavfilter/avf_showcqt.h | 3 +++
> libavfilter/version.h | 2 +-
> 4 files changed
Hi all,
I find that the latest ffmpeg could not handle timestamp propertly for some
inputs.
After some digging, I finally catch first exception in commit 8f6f232. The
problem
was introduced by applying the new decode API -- avcodec_send_packet() and
avcodec_receive_frame().
Since the new d
Fixes valgrind warnings about "Use of uninitialised value of size 8"
Signed-off-by: James Almer
---
This probably just silences a bunch of false possitives.
libavcodec/svq1dec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/svq1dec.c b/libavcodec/svq1dec.c
i
ffmpeg need a dash demuxer for demux the dash formats
base on
https://github.com/samsamsam-iptvplayer/exteplayer3/blob/master/tmp/ffmpeg/patches/3.2.2/01_add_dash_demux.patch
TODO:
1. support multi bitrate dash
v2 fixed:
1. from autodetect to disabled
2. from camelCase code style to ffmpeg co
On Sun, 9 Apr 2017 at 14:57 James Almer wrote:
> Fixes valgrind warnings about "Use of uninitialised value of size 8"
>
> Signed-off-by: James Almer
> ---
> This probably just silences a bunch of false possitives.
>
> libavcodec/svq1dec.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions
Signed-off-by: Paul B Mahol
---
libavfilter/vf_dctdnoiz.c | 85 +++
1 file changed, 71 insertions(+), 14 deletions(-)
diff --git a/libavfilter/vf_dctdnoiz.c b/libavfilter/vf_dctdnoiz.c
index 62763bf..69e67c2 100644
--- a/libavfilter/vf_dctdnoiz.c
+++ b
Signed-off-by: Paul B Mahol
---
libavfilter/Makefile| 1 +
libavfilter/allfilters.c| 1 +
libavfilter/vf_rangescope.c | 287
3 files changed, 289 insertions(+)
create mode 100644 libavfilter/vf_rangescope.c
diff --git a/libavfilter/Ma
On Sun, Apr 09, 2017 at 05:40:13PM +0200, Paul B Mahol wrote:
[...]
> +static av_always_inline void color_decorrelation_gbrp(float **dst, int
> dst_linesize,
> + const uint8_t **src,
> int src_linesize,
> +
On 4/9/17, Clement Boesch wrote:
> On Sun, Apr 09, 2017 at 05:40:13PM +0200, Paul B Mahol wrote:
> [...]
>> +static av_always_inline void color_decorrelation_gbrp(float **dst, int
>> dst_linesize,
>> + const uint8_t
>> **src, int src_linesize,
>
On 4/9/2017 11:51 AM, Kieran Kunhya wrote:
> On Sun, 9 Apr 2017 at 14:57 James Almer wrote:
>
>> Fixes valgrind warnings about "Use of uninitialised value of size 8"
>>
>> Signed-off-by: James Almer
>> ---
>> This probably just silences a bunch of false possitives.
>>
>> libavcodec/svq1dec.c |
Toolchains which target debugging are meaningless with stripping and
toolchains which target memory tracking are meaningless with memory
pollution.
---
configure | 8
1 file changed, 8 insertions(+)
diff --git a/configure b/configure
index 539a126656..f27ede94d9 100755
--- a/configure
++
Setting --valgrind implies the valgrind-memcheck toolchain. Before this
commit, the toolchain handling was overriding the target exec with an
arbitrary "valgrind" setting not taking into account the user setting.
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configu
On 4/5/2017 6:53 PM, Hendrik Leppkes wrote:
> On Wed, Apr 5, 2017 at 11:40 PM, James Almer wrote:
>> On 4/3/2017 10:46 AM, James Almer wrote:
>>> On 4/3/2017 7:00 AM, Michael Niedermayer wrote:
On Sun, Apr 02, 2017 at 10:45:41PM -0300, James Almer wrote:
> Signed-off-by: James Almer
On Wed, 5 Apr 2017, Marton Balint wrote:
The custom callback can cause significant CPU usage on Windows for some large
files with many index entries for some reason.
Will push this soon to master and 3.3.
Regards,
Marton
Signed-off-by: Marton Balint
---
ffprobe.c | 3 ++-
1 file changed, 2
Signed-off-by: Paul B Mahol
---
libavfilter/af_amix.c | 19 +++
libavutil/float_dsp.c | 9 +
libavutil/float_dsp.h | 16
3 files changed, 40 insertions(+), 4 deletions(-)
diff --git a/libavfilter/af_amix.c b/libavfilter/af_amix.c
index a4d1389..2dacb22 1
Le septidi 17 germinal, an CCXXV, Michael Niedermayer a écrit :
> Its in no release, and there seems consensus that it shouldnt be
> in a release at this point, so id say remove it from release/3.3 branch
I think we can say that enough time has passed, and ideally it should be
removed before the a
2017-04-10 4:39 GMT+08:00 Nicolas George :
> Le septidi 17 germinal, an CCXXV, Michael Niedermayer a écrit :
> > Its in no release, and there seems consensus that it shouldnt be
> > in a release at this point, so id say remove it from release/3.3 branch
>
> I think we can say that enough time has
On Mon, 10 Apr 2017, Steven Liu wrote:
2017-04-10 4:39 GMT+08:00 Nicolas George :
Le septidi 17 germinal, an CCXXV, Michael Niedermayer a écrit :
> Its in no release, and there seems consensus that it shouldnt be
> in a release at this point, so id say remove it from release/3.3 branch
I th
Fixes: out of array read
Fixes: 1072/clusterfuzz-testcase-6456688074817536
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/targets/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/aacdec_template.c | 14 --
1 file changed, 12 insertions(+)
2017-04-10 7:09 GMT+08:00 Marton Balint :
>
>
> On Mon, 10 Apr 2017, Steven Liu wrote:
>
> 2017-04-10 4:39 GMT+08:00 Nicolas George :
>>
>> Le septidi 17 germinal, an CCXXV, Michael Niedermayer a écrit :
>>> > Its in no release, and there seems consensus that it shouldnt be
>>> > in a release at t
On Sun, Apr 09, 2017 at 07:51:10AM -0300, James Almer wrote:
> Fixes valgrind warnings about "Use of uninitialised value of size 8"
how can this be reproduced ?
is this a regression ?
>
> Signed-off-by: James Almer
> ---
> This probably just silences a bunch of false possitives.
if thats the
On Sun, Apr 09, 2017 at 06:46:51PM +0200, Clément Bœsch wrote:
> Toolchains which target debugging are meaningless with stripping and
> toolchains which target memory tracking are meaningless with memory
> pollution.
> ---
> configure | 8
> 1 file changed, 8 insertions(+)
memory_poisoni
On 4/9/2017 10:46 PM, Michael Niedermayer wrote:
> On Sun, Apr 09, 2017 at 07:51:10AM -0300, James Almer wrote:
>> Fixes valgrind warnings about "Use of uninitialised value of size 8"
>
> how can this be reproduced ?
fate-svq1, fate-svq1-headerswap and fate-vsynth{1,2,3,_lena}-svq1 when
configure
Experimental VP9 support was added to the muxer recently.
---
libavformat/movenc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index a54aa879e9..9280dc8d23 100644
--- a/libavformat/movenc.c
+++ b/libavformat/movenc.c
@@ -6352,6 +6352,8 @@ stati
On Mon, Apr 10, 2017 at 03:51:40AM +0200, Michael Niedermayer wrote:
> On Sun, Apr 09, 2017 at 06:46:51PM +0200, Clément Bœsch wrote:
> > Toolchains which target debugging are meaningless with stripping and
> > toolchains which target memory tracking are meaningless with memory
> > pollution.
> > -
On Sun, Apr 09, 2017 at 11:10:16PM -0300, James Almer wrote:
[...]
> > is this a regression ?
>
> Fate didn't always complain about this, so it's either something
> introduced by a change in our tree, or a valgrind bug introduced in a
> relatively recent version.
>
> The reports in
> http://fate
On Mon, 10 Apr 2017 07:54:41 +0200
Clément Bœsch wrote:
> On Mon, Apr 10, 2017 at 03:51:40AM +0200, Michael Niedermayer wrote:
> > On Sun, Apr 09, 2017 at 06:46:51PM +0200, Clément Bœsch wrote:
> > > Toolchains which target debugging are meaningless with stripping and
> > > toolchains which tar
27 matches
Mail list logo
