On Thu, May 03, 2018 at 03:44:42PM +0200, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> doc/filters.texi| 3 +++
> libavfilter/vf_edgedetect.c | 5 +
> 2 files changed, 8 insertions(+)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index
On 5/4/2018 9:28 PM, wm4 wrote:
---
configure | 5 +
libavformat/Makefile | 1 +
libavformat/allformats.c | 1 +
libavformat/vapoursynth.c | 421 ++
4 files changed, 428 insertions(+)
create mode 100644
On 5/4/2018 12:58 PM, wm4 wrote:
> On Sat, 28 Apr 2018 19:05:29 +0200
> wm4 wrote:
>
>> This can "demux" .vpy files.
>>
>> Some minor code copied from other LGPL parts of FFmpeg.
>>
>> I did not found a good way to test a few of the more obscure features,
>> like VFR
On 5/4/2018 1:51 PM, wm4 wrote:
> On Fri, 4 May 2018 13:30:38 -0300
> James Almer wrote:
>
>> On 5/4/2018 12:58 PM, wm4 wrote:
>>> On Sat, 28 Apr 2018 19:05:29 +0200
>>> wm4 wrote:
>>>
This can "demux" .vpy files.
Some minor code
Fixes: shift exponent 47 is too large for 32-bit type 'int'
Fixes:
7955/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_JPEG2000_fuzzer-6016721977606144
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
On Sat, 28 Apr 2018 19:05:29 +0200
wm4 wrote:
> This can "demux" .vpy files.
>
> Some minor code copied from other LGPL parts of FFmpeg.
>
> I did not found a good way to test a few of the more obscure features,
> like VFR nodes, compat pixel formats, or nodes with
On Fri, 4 May 2018 13:30:38 -0300
James Almer wrote:
> On 5/4/2018 12:58 PM, wm4 wrote:
> > On Sat, 28 Apr 2018 19:05:29 +0200
> > wm4 wrote:
> >
> >> This can "demux" .vpy files.
> >>
> >> Some minor code copied from other LGPL parts of FFmpeg.
> >>
Fixes: signed integer overflow: 65280 * 196032 cannot be represented in type
'int'
Fixes:
7279/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_G2M_fuzzer-5977332473921536
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by:
Fixes: assertion failure
Fixes:
7949/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_JPEG2000_fuzzer-4819602782552064
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
This is large enough for all jpeg2000 files i tested. If some need more then
this
should be changed to dynamic allocation. Dynamic allocation would need to be
done
carefully as these are many relatively small arrays so repeatly reallocating
them
would not be good.
The decrease is a clean and
On Thu, May 03, 2018 at 10:24:49AM -0700, Aman Gupta wrote:
> On Thu, May 3, 2018 at 12:33 AM, Matthieu Bouron
> wrote:
>
> > On Wed, May 02, 2018 at 07:24:58PM -0700, Aman Gupta wrote:
> > > From: Aman Gupta
> > >
> > > The new logic follows a
On Thu, May 03, 2018 at 03:44:43PM +0200, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> doc/filters.texi| 4 +++-
> libavfilter/vf_edgedetect.c | 25 +
> 2 files changed, 28 insertions(+), 1 deletion(-)
>
> diff --git
On Thu, May 03, 2018 at 08:08:03PM +0200, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/vf_lut3d.c | 114
> +++--
> 1 file changed, 111 insertions(+), 3 deletions(-)
>
> diff --git a/libavfilter/vf_lut3d.c
Hi!
Attached patch fixes ticket #6195 for me.
Please comment, Carl Eugen
From 3aaeb2e44972d23d021e4567c9826162beb816f2 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sat, 5 May 2018 02:24:15 +0200
Subject: [PATCH] lavc/qdrw: Read PixMap palette.
Fixes ticket #6195.
On Fri, May 04, 2018 at 09:51:38PM -0300, James Almer wrote:
> On 5/4/2018 9:19 PM, Michael Niedermayer wrote:
> > On Fri, May 04, 2018 at 02:02:02PM -0300, James Almer wrote:
> >> On 5/4/2018 1:51 PM, wm4 wrote:
> >>> On Fri, 4 May 2018 13:30:38 -0300
> >>> James Almer wrote:
From: Aman Gupta
No functional changes.
---
libavcodec/videotoolbox.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/libavcodec/videotoolbox.c b/libavcodec/videotoolbox.c
index 57b6698e1b..1fd4be7135 100644
--- a/libavcodec/videotoolbox.c
+++
On Fri, May 04, 2018 at 02:02:02PM -0300, James Almer wrote:
> On 5/4/2018 1:51 PM, wm4 wrote:
> > On Fri, 4 May 2018 13:30:38 -0300
> > James Almer wrote:
> >
> >> On 5/4/2018 12:58 PM, wm4 wrote:
> >>> On Sat, 28 Apr 2018 19:05:29 +0200
> >>> wm4
2018-05-04 15:00 GMT+02:00, wm4 :
> On Sat, 28 Apr 2018 19:24:21 +0200
> wm4 wrote:
>
>> If the API user doesn't set avg_frame_rate, matroskaenc will write the
>> current timebase as "default duration" for the video track. This makes
>> no sense,
On 5/4/2018 9:19 PM, Michael Niedermayer wrote:
> On Fri, May 04, 2018 at 02:02:02PM -0300, James Almer wrote:
>> On 5/4/2018 1:51 PM, wm4 wrote:
>>> On Fri, 4 May 2018 13:30:38 -0300
>>> James Almer wrote:
>>>
On 5/4/2018 12:58 PM, wm4 wrote:
> On Sat, 28 Apr 2018
From: Aman Gupta
See https://s3.amazonaws.com/tmm1/videotoolbox/germany-hevc-zdf.ts
Although videotoolbox_buffer_create() sets frame->hw_frames_ctx,
by the time videotoolbox_postproc_frame() is called, some frames
randomly have frame->hw_frames_ctx == NULL. I don't really
2018-05-04 10:32 GMT+02:00, Timo Rothenpieler :
> I'm not sure if actual resolution changes are even supported
> by avcodec.
There are better (read: DVB) samples but I can't find them atm:
From: Aman Gupta
Previously the shared callbacks were trying to interpret
avctx->priv_data as H264Context*
---
libavcodec/videotoolbox.c | 43 +--
1 file changed, 33 insertions(+), 10 deletions(-)
diff --git a/libavcodec/videotoolbox.c
From: Aman Gupta
No longer required since 63d875772d. The equivalent hack
for h264 was removed in that commit, but this one was missed.
---
libavcodec/hevc_refs.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/libavcodec/hevc_refs.c b/libavcodec/hevc_refs.c
index
On Thu, May 03, 2018 at 03:44:44PM +0200, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/vf_edgedetect.c | 48
> ++---
> 1 file changed, 28 insertions(+), 20 deletions(-)
>
> diff --git
On Fri, May 4, 2018 at 8:13 AM, Matthieu Bouron
wrote:
> On Thu, May 03, 2018 at 10:24:49AM -0700, Aman Gupta wrote:
> > On Thu, May 3, 2018 at 12:33 AM, Matthieu Bouron <
> matthieu.bou...@gmail.com>
> > wrote:
> >
> > > On Wed, May 02, 2018 at 07:24:58PM -0700, Aman
applied
smime.p7s
Description: S/MIME Cryptographic Signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hello Ruiling,
On Fri, 4 May 2018 15:32:58 +0800, Ruiling Song wrote:
> It basically does hdr to sdr conversion with tonemapping.
>
> Signed-off-by: Ruiling Song
> ---
> This patch tries to add a filter to do hdr to sdr conversion with
On Thu, May 03, 2018 at 17:10:20 -0400, Ronak wrote:
> Are these issues being tracked somewhere already?
Bug reports are handled at https://trac.ffmpeg.org/ . You have a better
chance to get visibility there (though no guarantee).
> I'm happy to send pull requests, but I'll also have to get
applied
smime.p7s
Description: S/MIME Cryptographic Signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 5/3/2018 8:38 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Thu, May 3, 2018 at 4:41 AM, Kevin Wheatley
> wrote:
>
>> Following up my own email with another question or so:
>>
>> Could somebody point me at a suitable method of testing this within
>> the Fate framework?
> for dynamic resolution, maybe add a check ?
>
> ctx->support_dyn_res = nvenc_check_cap(avctx,
> NV_ENC_CAPS_SUPPORT_DYN_RES_CHANGE);
>
> and:
> if (dw != ctx->init_encode_params.darWidth || dh !=
> ctx->init_encode_params.darHeight)
>
> ==>
> if ( (dw != ctx->init_encode_params.darWidth || dh
WHAT!?
This LGTM was for the bit mask *only*
ALL OTHER POINTS STAND
Jan
On Fri, May 4, 2018, 06:04 Steven Liu wrote:
>
>
> > On 4 May 2018, at 02:00, Jan Ekström wrote:
> >
> > On Thu, May 3, 2018 at 8:58 PM, Jan Ekström wrote:
> >>
Signed-off-by: Paul B Mahol
---
libavfilter/af_amerge.c | 144 ++--
1 file changed, 67 insertions(+), 77 deletions(-)
diff --git a/libavfilter/af_amerge.c b/libavfilter/af_amerge.c
index 09c660ef49..8b71b3ce49 100644
---
On 8/26/17, Nicolas George wrote:
> L'octidi 8 fructidor, an CCXXV, Paul B Mahol a ecrit :
>> Prevents hang.
>>
>> Signed-off-by: Paul B Mahol
>> ---
>> libavfilter/af_join.c | 12 +---
>> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> Probably
> On 4 May 2018, at 17:20, Jan Ekström wrote:
>
> WHAT!?
>
> This LGTM was for the bit mask *only*
>
> ALL OTHER POINTS STAND
Don’t worry , all LGTM too, this could fix the resend sequence header timestamp
problem, all should be ok.
>
> Jan
Thanks
Steven
On 5/3/18 10:11 PM, Jan Ekström wrote:
> On Fri, Apr 27, 2018 at 3:51 AM, Jan Ekström wrote:
>> Personally I would be for removal of the WebM muxing feature in dashenc
>> altogether, since the dashenc feature has never seemingly worked, and
>> since there is a whole separate
On Fri, May 04, 2018 at 11:03:20AM +0800, Steven Liu wrote:
>
>
> > On 4 May 2018, at 02:00, Jan Ekström wrote:
> >
> > On Thu, May 3, 2018 at 8:58 PM, Jan Ekström wrote:
> >> On Thu, May 3, 2018 at 7:50 PM, Alex Converse
> >>
On Fri, 4 May 2018 17:31:52 +0800
Steven Liu wrote:
> > On 4 May 2018, at 17:20, Jan Ekström wrote:
> >
> > WHAT!?
> >
> > This LGTM was for the bit mask *only*
> >
> > ALL OTHER POINTS STAND
>
> Don’t worry , all LGTM too, this could fix the resend
On 5/4/18, Compn wrote:
> On Thu, 3 May 2018 17:26:38 -0300, James Almer
> wrote:
>> Create a new table with all non standard codecids from ff_codec_bmp_tags
>> and use it exclusively in avidec, then remove them from
>> ff_codec_bmp_tags, adapting other
On Thu, 3 May 2018 17:26:38 -0300, James Almer
wrote:
> Create a new table with all non standard codecids from ff_codec_bmp_tags
> and use it exclusively in avidec, then remove them from
> ff_codec_bmp_tags, adapting other de/muxers if needed (like ivf).
>
> And then add this
On Thu, 2018-05-03 at 22:43 +0100, Mark Thompson wrote:
> On 03/05/18 04:07, Haihao Xiang wrote:
> > '-sei xxx' is added to control SEI insertion, so far only mastering
> > display colour colume is available for testing.
>
> Typo: "colume" (also in the commit title).
>
Thanks for catching the
> On 4 May 2018, at 12:26, Michael Niedermayer wrote:
>
>> On Fri, May 04, 2018 at 11:03:20AM +0800, Steven Liu wrote:
>>
>>
>>> On 4 May 2018, at 02:00, Jan Ekström wrote:
>>>
>>> On Thu, May 3, 2018 at 8:58 PM, Jan Ekström
On Fri, 4 May 2018 08:19:27 -0400, Compn wrote:
> my idea would be to create a whitelist of codec ids we can encode to,
> instead of splitting up the decode fourcc list amongst formats.
that would also be a nightmare to maintain and users would ask for
support for "xxx codec"
On 5/4/18, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/af_amerge.c | 144
> ++--
> 1 file changed, 67 insertions(+), 77 deletions(-)
>
Fixes #6318.
On Fri, 4 May 2018 14:36:03 +0200, wm4 wrote:
> FourCC are already split up for avi and mov. Apparently it got
> sabotaged at some point.
i think mkv re-uses riff list from avi on purpose, as it was meant as a
replacement to avi (and has all the vfw codec tags in the
On Sat, 28 Apr 2018 19:24:21 +0200
wm4 wrote:
> If the API user doesn't set avg_frame_rate, matroskaenc will write the
> current timebase as "default duration" for the video track. This makes
> no sense, because the "default duration" implies the framerate of the
> video.
On Fri, 4 May 2018 08:56:18 -0400
Compn wrote:
> On Fri, 4 May 2018 14:36:03 +0200, wm4 wrote:
>
> > FourCC are already split up for avi and mov. Apparently it got
> > sabotaged at some point.
>
> i think mkv re-uses riff list from avi on purpose, as
On Fri, 4 May 2018 08:19:27 -0400
Compn wrote:
> On Thu, 3 May 2018 17:26:38 -0300, James Almer
> wrote:
> > Create a new table with all non standard codecids from ff_codec_bmp_tags
> > and use it exclusively in avidec, then remove them from
> >
On Sun, 29 Apr 2018 14:23:17 +0200
Clément Bœsch wrote:
> On Sat, Apr 28, 2018 at 08:37:06PM +0200, wm4 wrote:
> > This code will print a warning if any user agent is set - even if the
> > API user used the proper non-deprecated "user_agent" option.
> >
> > This change should not
>-Original Message-
>From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
>Mark Thompson
>Sent: Friday, May 4, 2018 5:49 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH 4/4] vaapi_encode_h265: Insert content
>light level information
>
>On 03/05/18
2018-05-03 17:58 GMT-03:00 Michael Niedermayer :
> On Thu, May 03, 2018 at 03:17:11PM -0300, Pedro Arthur wrote:
>> 2018-04-10 14:16 GMT-03:00 Sergey Lavrushkin :
>> > 2018-03-29 3:55 GMT+03:00 Michael Niedermayer :
>> >
>> >> On
Otherwise it might use unitialized last_pic in av_assert0(last_pic)
Signed-off-by: Haihao Xiang
---
libavcodec/vaapi_encode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/vaapi_encode.c b/libavcodec/vaapi_encode.c
index
Otherwise va_rt_format might be unitialized
Signed-off-by: Haihao Xiang
---
libavutil/hwcontext_vaapi.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
index 7daaa951cc..e59042487d 100644
---
The structure has reserved bytes, it is required to set the reserved
bytes to 0 for future use.
Signed-off-by: Haihao Xiang
---
libavcodec/vaapi_encode_vp8.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavcodec/vaapi_encode_vp8.c
From: Karthick Jeyapal
Right now segment file format is chosen to be either mp4 or webm based on the
codec format.
This patch makes that choice configurable by the user, instead of being decided
by the muxer.
---
doc/muxers.texi | 8
libavformat/dashenc.c
From: Karthick Jeyapal
Applicable only to webm output format.
By default all the segment filenames end with .m4s extension.
When someone chooses webm output format, we recommend they also override the
relevant segment name options to end with .webm extension. This patch
It basically does hdr to sdr conversion with tonemapping.
Signed-off-by: Ruiling Song
---
This patch tries to add a filter to do hdr to sdr conversion with tonemapping.
The filter does all the job of tonemapping in one pass, which is quite
different from the vf_tonemap.c
Not convenient if using numerals to set MFE mode. It is ambiguous
and misleading (e.g: user may misunderstand setting mfmode to 1 is to
enable MFE but actually it is to disable MFE, and set it to be 5 or above is
meaningless).
Signed-off-by: Zhong Li
---
Maximum number of frames to be used for combining.
Each encoder in joined sessions has to be initialized with the same value.
Signed-off-by: Zhong Li
---
libavcodec/qsvenc.c | 1 +
libavcodec/qsvenc.h | 1 +
libavcodec/qsvenc_h264.c | 2 ++
3 files changed, 4
59 matches
Mail list logo