On 1/19/2019 7:54 PM, Michael Niedermayer wrote:
> On Sat, Jan 19, 2019 at 04:11:07PM -0300, James Almer wrote:
>> On 1/19/2019 4:08 PM, Michael Niedermayer wrote:
>>> On Sat, Jan 19, 2019 at 03:53:55PM -0300, James Almer wrote:
On 1/19/2019 3:50 PM, Michael Niedermayer wrote:
> Signed-off
On Fri, Jan 18, 2019 at 02:42:20PM +0800, Shiyou Yin wrote:
> Optimize put_hevc_pel_bi_pixels_8 with mmi in the case width=8/16/24/32/48/64.
> This optimization improved HEVC decoding performance 2%(1.77x to 1.81x,
> tested on loongson 3A3000).
> ---
> libavcodec/mips/Makefile| 1 +
On Fri, Jan 18, 2019 at 02:50:29PM -0600, Rodger Combs wrote:
>
>
> > On Jan 18, 2019, at 05:41, Carl Eugen Hoyos wrote:
> >
> > 2019-01-18 9:46 GMT+01:00, Rodger Combs :
> >> All other TLS wrappers now have a mechanism to load a system trust store
> >> by default, without setting the cafile op
On Sat, Jan 19, 2019 at 11:48:39PM +0100, Marton Balint wrote:
> Signed-off-by: Marton Balint
> ---
> libavcodec/motion_est.c | 4 +--
> libavcodec/motion_est_template.c | 62
> +---
> 2 files changed, 3 insertions(+), 63 deletions(-)
please check i
On Wed, Jan 02, 2019 at 06:12:08PM -0300, James Almer wrote:
> On 1/2/2019 3:53 PM, Paul B Mahol wrote:
> > +static int hcom_decode(AVCodecContext *avctx, void *data,
> > + int *got_frame, AVPacket *pkt)
> > +{
> > +HCOMContext *s = avctx->priv_data;
> > +AVFrame *fram
On Sat, Jan 19, 2019 at 04:11:07PM -0300, James Almer wrote:
> On 1/19/2019 4:08 PM, Michael Niedermayer wrote:
> > On Sat, Jan 19, 2019 at 03:53:55PM -0300, James Almer wrote:
> >> On 1/19/2019 3:50 PM, Michael Niedermayer wrote:
> >>> Signed-off-by: Michael Niedermayer
> >>> ---
> >>> libavform
Signed-off-by: Marton Balint
---
libavcodec/motion_est.c | 4 +--
libavcodec/motion_est_template.c | 62 +---
2 files changed, 3 insertions(+), 63 deletions(-)
diff --git a/libavcodec/motion_est.c b/libavcodec/motion_est.c
index 8b5ce2117a..759eea479
On Tue, 25 Dec 2018 at 09:35, Tomas Härdin wrote:
> lör 2018-12-22 klockan 15:32 + skrev Matthew Fearnley:
> > > > >
> > > > Note that bw,bh aren't guaranteed to equal ZMBV_BLOCK, so
> `histogram[0] ==
> > > > bw*bh` would have to be used to guard against those (literal) edge
> cases.
> > >
>
On Fri, 4 Jan 2019, Marton Balint wrote:
On Fri, 4 Jan 2019, Nicolas George wrote:
Marton Balint (12018-12-30):
This allows the underlying files to change their duration on subsequent
avformat context opens.
An example use case where this matters:
ffconcat version 1.0
file dummy.mxf
fil
On Fri, Jan 18, 2019 at 12:38:20PM +0100, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch tries to improve the ROI documentation wording, C
> structs cannot return errors.
>
> Please comment, Carl Eugen
> frame.h |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 888a2470d43113b0
On Wed, Jan 16, 2019 at 11:54:42 -0800, Mohammad Izadi wrote:
> Subject: Support HDR dynamic metdata (HDR10+) in HEVC decoder.
^ Nit no. 1: metadata
Nit no. 2: Preferred format:
avcodec/hevcdec: add support for HDR dynamic metadata (HDR10+)
> +if (((row
> Subject: flush segments to guarantuee atomic single file hls
^ nit no. 1: guarantee
Nit no. 2: Please use a commit line something like:
avformat/hlsenc: flush segments to guarantee atomic single file hls
(I'm not sure I agree with the wording, but I'm no HLS expert
On 1/19/2019 4:08 PM, Michael Niedermayer wrote:
> On Sat, Jan 19, 2019 at 03:53:55PM -0300, James Almer wrote:
>> On 1/19/2019 3:50 PM, Michael Niedermayer wrote:
>>> Signed-off-by: Michael Niedermayer
>>> ---
>>> libavformat/hcom.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>
On Sat, Jan 19, 2019 at 03:53:55PM -0300, James Almer wrote:
> On 1/19/2019 3:50 PM, Michael Niedermayer wrote:
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavformat/hcom.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libavformat/hcom.c b/libavformat/hc
On 1/19/2019 3:50 PM, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavformat/hcom.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/hcom.c b/libavformat/hcom.c
> index 35515cc5b2..6d3d726fa5 100644
> --- a/libavformat/hcom.c
> +++
Signed-off-by: Michael Niedermayer
---
libavformat/hcom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/hcom.c b/libavformat/hcom.c
index 35515cc5b2..6d3d726fa5 100644
--- a/libavformat/hcom.c
+++ b/libavformat/hcom.c
@@ -38,7 +38,7 @@ static int hcom_probe(AVPro
On 19-01-2019 06:21 PM, Carl Eugen Hoyos wrote:
At present, 16-bit auto-scaled format results in incorrect alpha
extraction.
Does that mean that there is an unreported bug in the colour
space conversion?
Forcing a manual conversion to the same output format as the auto-scaler
avoids the err
2019-01-18 15:24 GMT+01:00, Derek Buitenhuis :
> To that end, I've opened a bug with oss-fuzz for some guidance:
>
> https://github.com/google/oss-fuzz/issues/2095
You are late to this party...
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@
2019-01-17 10:47 GMT+01:00, Gyan :
> Fixes alpha extraction for sample at
>
> https://08488297638989341201.googlegroups.com/attach/85d30cd6b8095/Circle%20Ink%20Bleed_10.mov
>
> as seen in
>
> ffplay -i in -vf alphaextract
> At present, 16-bit auto-scaled format results in incorrect alpha
> ex
19 matches
Mail list logo
