> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Mark Thompson
> Sent: Tuesday, June 04, 2019 7:19 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v3 3/5] libx265: Update ROI behaviour to match
> documentation
>
> Equival
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Mark Thompson
> Sent: Tuesday, June 04, 2019 7:19 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v3 2/5] libx264: Update ROI behaviour to match
> documentation
>
> Fix the
> 在 2019年6月4日，下午1:38，Jun Zhao 写道：
>
> From: Jun Zhao
>
> Pass correct pointer to av_log() and update some error/warning message,
> it's will help the debugging
>
> Signed-off-by: Jun Zhao
> ---
> libavformat/hls.c | 22 ++
> 1 files changed, 14 insertions(+), 8 deletion
On 04.06.2019, at 00:21, Antonin Gouzer wrote:
> ---
> Some codecs editors had miss interpreted the H264 standart and
> have coded a wrong size in the SEI data.
> size = SEI size + 1.
> The SEI data is detected as "truncated"
> Ex:
> https://drive.google.com/file/d/1cNtLwnfPnyJnYqE7OYhU3SCoLRt
From: Jun Zhao
fix ffmpeg -h full can't display webvtt muxer
Signed-off-by: Jun Zhao
---
libavformat/webvttenc.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/libavformat/webvttenc.c b/libavformat/webvttenc.c
index 61b7f54..b4e8a61 100644
--- a/libavform
From: Jun Zhao
fix ffmpeg -h full can't display webvtt decoder
Signed-off-by: Jun Zhao
---
libavcodec/webvttdec.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/libavcodec/webvttdec.c b/libavcodec/webvttdec.c
index 7b2d175..28113f6 100644
--- a/libavcodec
From: Jun Zhao
Pass correct pointer to av_log() and update some error/warning message,
it's will help the debugging
Signed-off-by: Jun Zhao
---
libavformat/hls.c | 22 ++
1 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/libavformat/hls.c b/libavformat/hls.c
From: Jun Zhao
fix ffmpeg -h full can't display webvtt encoder
Signed-off-by: Jun Zhao
---
libavcodec/webvttenc.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/libavcodec/webvttenc.c b/libavcodec/webvttenc.c
index c84bbf4..c19040d 100644
--- a/libavcodec
From: Jun Zhao
fix ffmpeg -h demuxer=webvtt can't dump options
Signed-off-by: Jun Zhao
---
libavformat/webvttdec.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/libavformat/webvttdec.c b/libavformat/webvttdec.c
index e435de3..52579c5 100644
--- a/libavformat
On Fri, May 31, 2019 at 6:15 PM Jun Li wrote:
>
> On Thu, May 30, 2019 at 5:29 PM Jun Li wrote:
>
>> Add exif orientation support and expose an option.
>> ---
>> libavfilter/hflip.h| 2 +
>> libavfilter/transpose.h| 14
>> libavfilter/vf_hflip.c | 40 ++---
>> libav
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Mark Thompson
> Sent: Tuesday, June 04, 2019 7:19 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v3 1/5] lavu/frame: Improve ROI
> documentation
>
> Clarify and add exampl
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of James
Almer
Sent: Monday, June 3, 2019 9:55 PM
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v1 1/1] vaapi_encode: replace av_new_packet
with ff_alloc_packet2
> I can't find this
Fix the quantisation offset - use the whole range, and don't change the
offset size based on bit depth.
Iterate the list in reverse order. The first region in the list is the one
that applies in the case of overlapping regions.
---
libavcodec/libx264.c | 53 +-
Equivalent to the previous patch for libx264.
---
libavcodec/libx265.c | 44 +++-
1 file changed, 23 insertions(+), 21 deletions(-)
diff --git a/libavcodec/libx265.c b/libavcodec/libx265.c
index f56def53d5..665b780643 100644
--- a/libavcodec/libx265.c
+++ b
Clarify and add examples for the behaviour of the quantisation offset,
and define how multiple ranges should be handled.
---
libavutil/frame.h | 59 ++-
1 file changed, 43 insertions(+), 16 deletions(-)
diff --git a/libavutil/frame.h b/libavutil/frame.h
This can be used to add region of interest side data to video frames.
---
doc/filters.texi | 44 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/vf_addroi.c | 268 +++
4 files changed, 314 insertions(+)
create m
---
For example:
$ ./ffmpeg_g -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
-hwaccel_output_format vaapi -i in.mp4 -an -vf
'scale_vaapi=96:96,addroi=iw/3:ih/3:iw/3:ih/3:-1/2' -c:v h264_vaapi -rc_mode
CQP -global_quality 44 -frames:v 1 test.264
...
$ ldecod.exe
...
$ cat trace_dec.txt | gre
Michael Niedermayer:
> On Sun, Jun 02, 2019 at 12:47:18AM +0200, Andreas Rheinhardt wrote:
>> Until now the function ff_startcode_find_candidate_c did not really
>> search for startcodes (the startcode 0x00 0x00 0x01 (used in
>> MPEG-1/2/4, VC-1 and H.264/5) is the only startcode meant here). Inste
Michael Niedermayer:
> On Sun, Jun 02, 2019 at 12:47:17AM +0200, Andreas Rheinhardt wrote:
>> Up until now ff_startcode_find_candidate_c could overread; it relied on
>> zero-padding after the buffer in order to function correctly. This has
>> been changed: No overreads occur any more.
>> The ultima
Michael Niedermayer:
> On Sun, Jun 02, 2019 at 12:47:15AM +0200, Andreas Rheinhardt wrote:
>> The reasons are cosmetics and preparation for future patches that will
>> have even more cases.
>>
>> Signed-off-by: Andreas Rheinhardt
>> ---
>> libavcodec/startcode.c | 37 +++--
On 6/2/2019 1:38 PM, Mark Thompson wrote:
> On 26/05/2019 19:40, James Almer wrote:
>> Signed-off-by: James Almer
>> ---
>> libavcodec/cbs_h264.h | 6 ++
>> libavcodec/cbs_h2645.c| 1 +
>> libavcodec/cbs_h264_syntax_template.c | 17 +
>> 3 fil
---
Some codecs editors had miss interpreted the H264 standart and
have coded a wrong size in the SEI data.
size = SEI size + 1.
The SEI data is detected as "truncated"
Ex:
https://drive.google.com/file/d/1cNtLwnfPnyJnYqE7OYhU3SCoLRtuXIUM/view?usp=sharing
Command:
ffprobe -strict experimental -pri
Reimar Döffinger:
> On 03.06.2019, at 14:07, Andreas Rheinhardt
> wrote:
>
>> Reimar Döffinger:
>>> On 03.06.2019, at 00:37, Andreas Rheinhardt
>>> wrote:
>>>
Up until now, a temporary variable was used and initialized every time a
value was read in CBS; if reading turned out to be s
On Sun, Jun 02, 2019 at 12:47:15AM +0200, Andreas Rheinhardt wrote:
> The reasons are cosmetics and preparation for future patches that will
> have even more cases.
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/startcode.c | 37 +++--
> 1 file changed,
On Sun, Jun 02, 2019 at 12:47:18AM +0200, Andreas Rheinhardt wrote:
> Until now the function ff_startcode_find_candidate_c did not really
> search for startcodes (the startcode 0x00 0x00 0x01 (used in
> MPEG-1/2/4, VC-1 and H.264/5) is the only startcode meant here). Instead
> it searched for zero
On Sun, Jun 02, 2019 at 12:47:17AM +0200, Andreas Rheinhardt wrote:
> Up until now ff_startcode_find_candidate_c could overread; it relied on
> zero-padding after the buffer in order to function correctly. This has
> been changed: No overreads occur any more.
> The ultimate goal behind all this is
On 09/05/2019 03:46, Fu, Linjie wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of Mark Thompson
>> Sent: Monday, May 6, 2019 23:21
>> To: FFmpeg development discussions and patches > de...@ffmpeg.org>
>> Subject: [FFmpeg-devel] [PATC
On 03.06.2019, at 14:07, Andreas Rheinhardt
wrote:
> Reimar Döffinger:
>> On 03.06.2019, at 00:37, Andreas Rheinhardt
>> wrote:
>>
>>> Up until now, a temporary variable was used and initialized every time a
>>> value was read in CBS; if reading turned out to be successfull, this
>>> value wa
On 6/3/2019 3:39 AM, Sun, Jing A wrote:
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> James Almer
> Sent: Saturday, June 1, 2019 3:06 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v1 1/1] vaapi_encode: replace
> a
Reimar Döffinger:
> On 03.06.2019, at 00:37, Andreas Rheinhardt
> wrote:
>
>> Up until now, a temporary variable was used and initialized every time a
>> value was read in CBS; if reading turned out to be successfull, this
>> value was overwritten (without having ever been looked at) with the
>>
Fixes: Various anomalies
Fixes:
14493/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_DXV_fuzzer-5071018000908288
Fixes:
14630/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_DXV_fuzzer-5714888963391488
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/proj
Signed-off-by: Steven Liu
---
libavformat/dashdec.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavformat/dashdec.c b/libavformat/dashdec.c
index 2c50f23c06..315dcae651 100644
--- a/libavformat/dashdec.c
+++ b/libavformat/dashdec.c
@@ -1834,7 +1834,9 @@ end:
static i
On 6/2/19, Michael Niedermayer wrote:
> Fixes: Timeout (15sec -> 0.5sec)
> Fixes:
> 14846/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_FMVC_fuzzer-5068322120400896
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by: Michae
On 5/30/19, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/avf_showwaves.c | 30 +++---
> 1 file changed, 27 insertions(+), 3 deletions(-)
>
Will apply soon.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffm
Signed-off-by: Steven Liu
---
libavformat/dashdec.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavformat/dashdec.c b/libavformat/dashdec.c
index 2c50f23c06..315dcae651 100644
--- a/libavformat/dashdec.c
+++ b/libavformat/dashdec.c
@@ -1834,7 +1834,9 @@ end:
static i
> -Original Message-
> From: Fu, Linjie
> Sent: Monday, June 3, 2019 3:10 PM
> To: Li, Zhong ; FFmpeg development discussions and
> patches
> Subject: RE: [FFmpeg-devel] [PATCH, v2 1/2] lavf/qsvvpp: allocate
> continuous memory
>
>
>
> > -Original Message-
> > From: Li, Zhong
> -Original Message-
> From: Li, Zhong
> Sent: Monday, June 3, 2019 13:28
> To: Fu, Linjie ; FFmpeg development discussions and
> patches
> Subject: RE: [FFmpeg-devel] [PATCH, v2 1/2] lavf/qsvvpp: allocate
> continuous memory
>
>
>
> > -Original Message-
> > From: Fu, Linjie
>
37 matches
Mail list logo
