> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: Wednesday, March 13, 2019 08:18
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH v2 5/6] vaapi_encode: Add ROI support
>
> ---
> libavcodec/vaapi_encode.c
Signed-off-by: Steven Liu
---
tests/ref/fate/hls-segment-size | 772
1 file changed, 772 insertions(+)
create mode 100644 tests/ref/fate/hls-segment-size
diff --git a/tests/ref/fate/hls-segment-size b/tests/ref/fate/hls-segment-size
new file mode 100644
> 在 2019年4月18日，09:35，Carl Eugen Hoyos 写道：
>
> 2019-04-17 10:11 GMT+02:00, Steven Liu :
>> ffmpeg | branch: master | Steven Liu | Sun Apr 14
>> 21:22:22 2019 +0800| [2a50f1d9e414bdf3d97c6aa649769d17793f2991] | committer:
>> Steven Liu
>>
>> tests/fate: add fate-hls-segment-size for hls_segment
On 4/17/2019 10:35 PM, Carl Eugen Hoyos wrote:
> 2019-04-17 10:11 GMT+02:00, Steven Liu :
>> ffmpeg | branch: master | Steven Liu | Sun Apr 14
>> 21:22:22 2019 +0800| [2a50f1d9e414bdf3d97c6aa649769d17793f2991] | committer:
>> Steven Liu
>>
>> tests/fate: add fate-hls-segment-size for hls_segment_s
Hi!
Attached patch fixes fate on Windows subsystem for Linux here.
Please comment, Carl Eugen
From 5f7ffdc2968bdc6f37fdeb3870ccb8135e91048a Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Thu, 18 Apr 2019 03:24:35 +0200
Subject: [PATCH] tests: Add EXESUF to program calls.
Fixes fate in Wi
2019-04-17 10:11 GMT+02:00, Steven Liu :
> ffmpeg | branch: master | Steven Liu | Sun Apr 14
> 21:22:22 2019 +0800| [2a50f1d9e414bdf3d97c6aa649769d17793f2991] | committer:
> Steven Liu
>
> tests/fate: add fate-hls-segment-size for hls_segment_size test
I believe this commit broke fate.
Carl Euge
2019-04-18 2:02 GMT+02:00, Jun Li :
> On Wed, Apr 17, 2019 at 3:11 PM Carl Eugen Hoyos wrote:
>
>> 2019-04-15 8:43 GMT+02:00, Jun Li :
>> > Currently the strftime option generate timestamp based on generation
>> > time. The new option would calcualte timestamp from source's
>> > start_realtime and
On 4/16/2019 11:56 PM, James Almer wrote:
> @@ -164,9 +164,9 @@ static int FUNC(profile_tier_level)(CodedBitstreamContext
> *ctx, RWContext *rw,
>
> for (i = 0; i < max_num_sub_layers_minus1; i++) {
> if (current->sub_layer_profile_present_flag[i]) {
> -us(2, sub_layer_
On Wed, Apr 17, 2019 at 3:11 PM Carl Eugen Hoyos wrote:
> 2019-04-15 8:43 GMT+02:00, Jun Li :
> > Currently the strftime option generate timestamp based on generation
> > time. The new option would calcualte timestamp from source's
> > start_realtime and pkt->pts, try to generate a timestamp matc
On Thu, Apr 18, 2019 at 01:19:58AM +0200, Michael Niedermayer wrote:
> On Wed, Apr 17, 2019 at 06:16:39PM +0200, Paul B Mahol wrote:
> > Signed-off-by: Paul B Mahol
> > ---
> > libavcodec/dvdec.c | 19 ++-
> > 1 file changed, 10 insertions(+), 9 deletions(-)
>
> Is this intended
On Wed, Apr 17, 2019 at 06:16:39PM +0200, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavcodec/dvdec.c | 19 ++-
> 1 file changed, 10 insertions(+), 9 deletions(-)
Is this intended to be 100% same output ?
I have a few cases that produce differences. Dont have a
Hi!
Attached patch fixes ticket #7853.
Please comment, Carl Eugen
From 55851640fa9e4d23c6c32bf33a46927815544040 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Thu, 18 Apr 2019 00:50:48 +0200
Subject: [PATCH] lavf/vc1dec: Reduce probe score for streams with invalid
frames.
Fixes ticket 7
2019-04-17 22:28 GMT+02:00, Andreas Håkon via ffmpeg-devel
:
> This patch solves the initialization of the inputs when using filters (a
> graph filter) with the mpegts muxer.
>
> This bug seems to be generated by a simple forgetting to copy. The same code
> is repeated two times, but only in one ca
2019-04-15 8:43 GMT+02:00, Jun Li :
> Currently the strftime option generate timestamp based on generation
> time. The new option would calcualte timestamp from source's
> start_realtime and pkt->pts, try to generate a timestamp matches the
> source starting time.
> diff --git a/libavformat/rtsp.c
On Sun, Apr 14, 2019 at 11:43 PM Jun Li wrote:
> Currently the strftime option generate timestamp based on generation
> time. The new option would calcualte timestamp from source's
> start_realtime and pkt->pts, try to generate a timestamp matches the
> source starting time.
> ---
> doc/muxers.t
---
src/security | 49 +
1 file changed, 49 insertions(+)
diff --git a/src/security b/src/security
index b6239bf..9175aba 100644
--- a/src/security
+++ b/src/security
@@ -12,6 +12,14 @@ CVE-2019-9718, cc5361ed18ab0f69cfbead7afc88fb81ed4b36ae /
1f00
Signed-off-by: Michael Niedermayer
---
src/security | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/security b/src/security
index 8615685..b6239bf 100644
--- a/src/security
+++ b/src/security
@@ -33,7 +33,7 @@ CVE-2018-15822, 6b67d7f05918f7a1ee8fc6ff21355d7e8736aa10
This patch solves the initialization of the inputs when using filters (a graph
filter) with the mpegts muxer.
This bug seems to be generated by a simple forgetting to copy. The same code is
repeated two times, but only in one case the variable “inputs_done” is
initialized. Compare the two block
On 18-04-2019 12:33 AM, Sam John via ffmpeg-devel wrote:
Hi,
Is there anything to be done for this patch ?
Just a tiny bit of formatting, which I'll do and push.
Thanks,
Gyan
On Tue, Apr 9, 2019 at 5:55 PM Sam John wrote:
---
doc/encoders.texi | 47 ++
Hi,
Is there anything to be done for this patch ?
Thanks
Sam John
On Tue, Apr 9, 2019 at 5:55 PM Sam John wrote:
> ---
> doc/encoders.texi | 47 +++
> 1 file changed, 47 insertions(+)
>
> diff --git a/doc/encoders.texi b/doc/encoders.texi
> index 94
On 17-04-2019 11:14 PM, Vittorio Giovara wrote:
On Tue, Apr 16, 2019 at 3:42 AM Gyan wrote:
Patch revised as per
http://www.ffmpeg.org/pipermail/ffmpeg-devel/2019-April/242591.html
Gyan
sorry if i'm late to the party but why are these new fields in
avcodeccontext?
they seem to be perfect
On 17-04-2019 11:11 PM, Vittorio Giovara wrote:
On Wed, Apr 17, 2019 at 12:26 AM Gyan wrote:
On 13-04-2019 05:23 PM, Gyan wrote:
Will be helpful for correct result in filters that paint like
fillborders/drawbox or those using drawutils.
Ping.
these seem to only work for 8 bit content, i
On Tue, Apr 16, 2019 at 3:42 AM Gyan wrote:
> Patch revised as per
> http://www.ffmpeg.org/pipermail/ffmpeg-devel/2019-April/242591.html
>
> Gyan
>
sorry if i'm late to the party but why are these new fields in
avcodeccontext?
they seem to be perfect candidates for side data, or am i missing som
On Wed, Apr 17, 2019 at 12:26 AM Gyan wrote:
>
>
> On 13-04-2019 05:23 PM, Gyan wrote:
> > Will be helpful for correct result in filters that paint like
> > fillborders/drawbox or those using drawutils.
>
> Ping.
>
these seem to only work for 8 bit content, is that their only intended
usecase?
i
Signed-off-by: Paul B Mahol
---
libavcodec/dvdec.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/libavcodec/dvdec.c b/libavcodec/dvdec.c
index 7b16787e27..89864f2edc 100644
--- a/libavcodec/dvdec.c
+++ b/libavcodec/dvdec.c
@@ -49,6 +49,7 @@
#include "in
Also infer the value time_offset_length as 0 when it's not present.
Signed-off-by: James Almer
---
Fun thing, this metadata OBU is clearly based on the H264/5 timecode SEI, yet
time_offset_length is unsigned here :p
libavcodec/cbs_av1_syntax_template.c | 14 --
1 file changed, 8 ins
Hello all
Just a reminder for this patch
On Mon, Apr 1, 2019 at 4:45 PM Olivier Maignial
wrote:
> RFC-4566 do not give any limit of size on interger parameters given in
> fmtp line.
> By reading some more RFCs it is possible to find examples where some
> integers parameters are greater than 32 (
I've changed the allocation functions and attached the output of `git
format-patch` to this e-mail.
Thanks,
Jonathan Gilbert
On Tue, Apr 16, 2019 at 5:50 PM Carl Eugen Hoyos wrote:
> 2019-04-16 19:14 GMT+02:00, Jonathan Gilbert :
> > Hello :-)
> >
> > I had a project recently where I wanted to
28 matches
Mail list logo
