> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Moritz Barsnick
> Sent: Thursday, November 30, 2017 10:33 PM
> To: FFmpeg development discussions and patches
>
> Subject: Re: [FFmpeg-devel] [PATCH 1/2] vaapi_h264: Add named options for
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Hendrik Leppkes
> Sent: Thursday, November 30, 2017 6:12 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 2/2] vaapi_h265:
2017-12-01 9:19 GMT+08:00 James Almer :
> Signed-off-by: James Almer
> ---
> Pros:
> Removes duplicate arrays and ugly c file including c files
>
> Cons:
> Makes the array in libavutil effectively part of the ABI.
> Might not be worth doing for 256 bytes
>
>
On Thu, Nov 30, 2017 at 12:19:10PM -0800, Dale Curtis wrote:
> On Wed, Nov 29, 2017 at 5:58 PM, Michael Niedermayer > wrote:
>
> >
> > AV_EF_EXPLODE appears to be a possibility, yes
> > in general demuxers should try to extract as much as possible from a
> > file and not
Signed-off-by: James Almer
---
Pros:
Removes duplicate arrays and ugly c file including c files
Cons:
Makes the array in libavutil effectively part of the ABI.
Might not be worth doing for 256 bytes
Something like this was probably sent before, so i guess it
will be rejected
Fix parenthesis in conditional
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
---
fftools/ffplay.c | 21 -
1 file changed, 16 insertions(+), 5 deletions(-)
diff --git a/fftools/ffplay.c b/fftools/ffplay.c
index 10a917194d..152d220cdb 100644
--- a/fftools/ffplay.c
+++ b/fftools/ffplay.c
@@ -198,6 +198,8 @@ typedef struct Decoder {
int64_t next_pts;
Merges ctts_data into mov_index_entries. This allows a considerable
amount of code simplification.
---
libavformat/isom.h | 1 +
libavformat/mov.c | 312 ++---
2 files changed, 130 insertions(+), 183 deletions(-)
diff --git a/libavformat/isom.h
---
libavformat/isom.h | 10 ++
libavformat/mov.c | 92 ++---
libavformat/utils.c | 3 +-
3 files changed, 99 insertions(+), 6 deletions(-)
diff --git a/libavformat/isom.h b/libavformat/isom.h
index 65676fb0f5..646b31ccc7 100644
---
Rebase to resolve conflicts.
These 2 patches should be merged before commit. They are separated to
make reviewing easier. Patch 4 alone does not account for edit list
fix-ups.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
Remove redundant sliceType check. It is only needed if using x265 2.4
or below where sliceType BREF is never set.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Used by movenc to fill sdtp box
---
libavcodec/libx265.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavcodec/libx265.c b/libavcodec/libx265.c
index 4456e300f2..c137fe4ae1 100644
--- a/libavcodec/libx265.c
+++ b/libavcodec/libx265.c
@@ -329,6 +329,9 @@ FF_DISABLE_DEPRECATION_WARNINGS
On Wed, 29 Nov 2017, Mironov, Mikhail wrote:
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
Of Paul B Mahol
Sent: November 29, 2017 10:16 AM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] AMD external header
On
On 11/30/2017 7:58 PM, Jacob Trimble wrote:
> Signed-off-by: Jacob Trimble
> ---
> configure | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/configure b/configure
> index 1fa16e9dba..d05388638d 100755
> --- a/configure
> +++ b/configure
> @@ -2890,6 +2890,7 @@
2017-12-01 0:31 GMT+08:00 Robert Nagy :
> ---
> libavformat/hlsenc.c | 9 +
> 1 file changed, 1 insertion(+), 8 deletions(-)
>
> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
> index cdfbf45823..394c7130ac 100644
> --- a/libavformat/hlsenc.c
> +++
Hi,
Attached patch adds full support for skip_loop_filter (all levels) to
the hevc decoder.
I'm not too sure about the implementation of "nonref", since this email
(http://ffmpeg.org/pipermail/ffmpeg-devel/2015-July/176116.html)
mentions looking at nal_unit_type and temporal_id instead. Some
From b6a6f6d577e562c09c7cc1fc0befd2d73a9c0f32 Mon Sep 17 00:00:00 2001
From: James Courtier-Dutton
Date: Thu, 30 Nov 2017 22:56:04 +
Subject: [PATCH] libavformat/segment: strftime date sub-directories
Automatically create sub-directories if needed based on date.
E.g.
Signed-off-by: Jacob Trimble
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index 1fa16e9dba..d05388638d 100755
--- a/configure
+++ b/configure
@@ -2890,6 +2890,7 @@ trace_headers_bsf_select="cbs_h264 cbs_h265 cbs_mpeg2"
# external
Fixes: 4427/clusterfuzz-testcase-minimized-5106919271301120
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/j2kenc.c | 3 ++-
1 file changed, 2 insertions(+), 1
Fixes: runtime error: left shift of negative value -127
Fixes: 4397/clusterfuzz-testcase-minimized-4779061080489984
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
Reduces memory needed.
Fixes: OOM
Fixes: 4427/clusterfuzz-testcase-minimized-5106919271301120
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/j2kenc.c | 4 +++-
On Sun, Nov 26, 2017 at 07:32:30AM -0800, John Stebbins wrote:
> An invalid file may cause huge alloc. Delay expansion of ctts entries
> until the number of samples is known in mov_build_index.
>
> Found-by: zhao dongzhuo, AD-lab of Venustech
> ---
> libavformat/mov.c | 31
Copied the check from cuviddec.c (*_cuvid decoders) to allow the
capability check to be optional for older drivers.
Signed-off-by: Jacob Trimble
---
libavcodec/nvdec.c | 12
1 file changed, 12 insertions(+)
diff --git a/libavcodec/nvdec.c b/libavcodec/nvdec.c
On Wed, Nov 29, 2017 at 5:58 PM, Michael Niedermayer wrote:
>
> AV_EF_EXPLODE appears to be a possibility, yes
> in general demuxers should try to extract as much as possible from a
> file and not give up if some broken packet is found
>
I don't think this is a good
Didn't notice this one when 9648cc6d was landed.
Signed-off-by: Dale Curtis
From 2f7c0ee007cb28b8f3bf201279d7f17ca671728d Mon Sep 17 00:00:00 2001
From: Dale Curtis
Date: Thu, 30 Nov 2017 12:20:36 -0800
Subject: [PATCH] [vorbis] Fix another 1 <<
On Wed, Nov 29, 2017 at 08:08:40PM -0800, Neil Birkbeck wrote:
> On Wed, Nov 29, 2017 at 7:40 PM, Neil Birkbeck
> wrote:
>
> >
> >>
> >> If you are searching for a case where the patch makes a difference
> >> one is:
> >> ./ffmpeg -i ~/tickets/4493/AVCI100.mov out.nut
>
We've done a bit more testing on this and it looks good here.
On Thu, Nov 30, 2017 at 12:26 PM, Bjorn Roche wrote:
>
>
> On Mon, Nov 27, 2017 at 7:12 PM, Carl Eugen Hoyos
> wrote:
>
>> 2017-11-28 1:07 GMT+01:00 Bjorn Roche :
>> > On Mon,
On Mon, Nov 27, 2017 at 7:12 PM, Carl Eugen Hoyos
wrote:
> 2017-11-28 1:07 GMT+01:00 Bjorn Roche :
> > On Mon, Nov 27, 2017 at 5:41 PM, Carl Eugen Hoyos
> > wrote:
>
> >> >> Does remuxing animated gif with transparency work with your
On Thu, Nov 30, 2017 at 03:18:47PM +0800, tiejun.peng wrote:
> discard corrupted track and good track have chance to play.
>
> Signed-off-by: tiejun.peng
> ---
> libavformat/mov.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git
On Thu, Nov 30, 2017 at 10:15:48AM +0100, Felix Matouschek wrote:
> Sorry, my mail client swallowed the attachment, sent it again.
>
> Changelog|1
> MAINTAINERS |1
> configure|6
> doc/indevs.texi | 40 ++
>
On Wed, 2017-11-29 at 20:18 -0800, Mark Reid wrote:
> On Wed, Nov 29, 2017 at 1:36 AM, Tomas Härdin
> wrote:
>
> > On 2017-11-29 05:11, Mark Reid wrote:
> >
> > > @@ -980,7 +980,7 @@ static void
> > > mxf_write_structural_component(AVFormatContext
> > > *s, AVStream *st, MXF
On 11/30/17, Moritz Barsnick wrote:
> On Wed, Nov 29, 2017 at 20:16:16 +0100, Paul B Mahol wrote:
>> +@item mode
>> +Set fill mode.
>> +
>> +It accepts the following values:
>> +@table @samp
>> +@item smear
>> +fill pixels using outermost pixels
>> +
>> +@item mirror
>> +fill
On 11/30/17, Nicolas George wrote:
> Moritz Barsnick (2017-11-30):
>> Wouldn't
>>tile->first_frame = 0;
>> be faster and easier? Or did you mean to use different variables in the
>> check and the assignment?
>
> Or even clearing the option after is has been used.
On Thu, 30 Nov 2017 15:44:19 +0100
Hendrik Leppkes wrote:
> On Thu, Nov 30, 2017 at 3:29 PM, Hendrik Leppkes wrote:
> > On Thu, Nov 30, 2017 at 3:17 PM, Michael Niedermayer
> > wrote:
> >> On Thu, Nov 30, 2017 at 11:55:03AM
>On 11/30/17, 5:31 PM, "Steven Liu" wrote:
>
>2017-11-30 19:32 GMT+08:00 :
>> From: Vishwanath Dixit
>>
>>---
>> libavformat/Makefile | 2 +-
>> libavformat/dashenc.c | 2 +-
>>
On Thu, Nov 30, 2017 at 05:29:45PM +0100, Felix Matouschek wrote:
> Am 30.11.2017 14:48, schrieb Michael Niedermayer:
> >>You mean avg_frame_rate and r_frame_rate?
> >>The framerate can vary between the values in framerate_range[0]
> >>(min) and framerate_range[1] (max).
> >>Ideally both values
---
libavformat/hlsenc.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index cdfbf45823..394c7130ac 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -1921,14 +1921,7 @@ static int
On Thu, Nov 30, 2017 at 01:35:52PM +, Marc-Antoine ARNAUD wrote:
> Le jeu. 30 nov. 2017 à 01:51, Michael Niedermayer
> a écrit :
>
> > On Wed, Nov 29, 2017 at 11:28:40AM +, Marc-Antoine ARNAUD wrote:
> > > Le mer. 22 nov. 2017 à 17:54, Michael Niedermayer
Am 30.11.2017 14:48, schrieb Michael Niedermayer:
You mean avg_frame_rate and r_frame_rate?
The framerate can vary between the values in framerate_range[0]
(min) and framerate_range[1] (max).
Ideally both values are the same, sometimes min can be lower but for
the average the framerate should be
On 11/30/2017 11:44 AM, Hendrik Leppkes wrote:
> On Thu, Nov 30, 2017 at 3:29 PM, Hendrik Leppkes wrote:
>> On Thu, Nov 30, 2017 at 3:17 PM, Michael Niedermayer
>> wrote:
>>> On Thu, Nov 30, 2017 at 11:55:03AM +, Rostislav Pehlivanov wrote:
On Thu, Nov 30, 2017 at 3:29 PM, Hendrik Leppkes wrote:
> On Thu, Nov 30, 2017 at 3:17 PM, Michael Niedermayer
> wrote:
>> On Thu, Nov 30, 2017 at 11:55:03AM +, Rostislav Pehlivanov wrote:
>>> On 28 November 2017 at 01:26, Michael Niedermayer
On Thu, Nov 30, 2017 at 08:52:21 +, Li, Zhong wrote:
> > +{ LEVEL("6", 60) },
> > +{ LEVEL("6.1", 61) },
> > +{ LEVEL("6.2", 62) },
>
> IIRC, level 5.2 is the maximum level of H264?
Higher levels were introduced in 2016. Edition V12 of H.264 lists 6,
6.1 and 6.2 in Annex A,
On Thu, Nov 30, 2017 at 3:17 PM, Michael Niedermayer
wrote:
> On Thu, Nov 30, 2017 at 11:55:03AM +, Rostislav Pehlivanov wrote:
>> On 28 November 2017 at 01:26, Michael Niedermayer
>> wrote:
>>
>> > On Mon, Nov 27, 2017 at 04:30:18AM +,
Hello,
I was wondering if someone has ever tried modifying the code of FFmpeg to
support varying the framerate during streaming. So far, I tried to
re-initialize the AVCodec Context of the output stream to apply the new
framerate. Whenever I would suddenly change the framerate (from inside
On Thu, Nov 30, 2017 at 12:54 PM, Rostislav Pehlivanov
wrote:
> On 29 November 2017 at 16:40, Michael Niedermayer
> wrote:
>
>> On Wed, Nov 29, 2017 at 03:51:34AM +, Rostislav Pehlivanov wrote:
>> > On 28 November 2017 at 20:23, Michael
On Thu, Nov 30, 2017 at 11:55:03AM +, Rostislav Pehlivanov wrote:
> On 28 November 2017 at 01:26, Michael Niedermayer
> wrote:
>
> > On Mon, Nov 27, 2017 at 04:30:18AM +, Rostislav Pehlivanov wrote:
> > > Signed-off-by: Rostislav Pehlivanov
>
Moritz Barsnick (2017-11-30):
> Wouldn't
>tile->first_frame = 0;
> be faster and easier? Or did you mean to use different variables in the
> check and the assignment?
Or even clearing the option after is has been used. Single test, single
field: faster, less memory, less code.
On Wed, Nov 29, 2017 at 20:29:49 +0100, Paul B Mahol wrote:
> +{ "init_padding", " set how many frames to initially pad",
> OFFSET(init_padding),
^ space
Some whitespace slipped in there.
> +if (tile->first_frame)
> +tile->first_frame = 0;
On Thu, Nov 30, 2017 at 11:54:25AM +, Rostislav Pehlivanov wrote:
> On 29 November 2017 at 16:40, Michael Niedermayer
> wrote:
>
> > On Wed, Nov 29, 2017 at 03:51:34AM +, Rostislav Pehlivanov wrote:
> > > On 28 November 2017 at 20:23, Michael Niedermayer
On Wed, Nov 29, 2017 at 20:16:16 +0100, Paul B Mahol wrote:
> +@item mode
> +Set fill mode.
> +
> +It accepts the following values:
> +@table @samp
> +@item smear
> +fill pixels using outermost pixels
> +
> +@item mirror
> +fill pixels using mirroring
> +
> +@item fixed
> +fill pixels with
On Thu, Nov 30, 2017 at 10:12:53AM +0100, Felix Matouschek wrote:
> Am 29.11.2017 04:31, schrieb Michael Niedermayer:
>
> >if the identifer and the string always match you could do this
> >with a macro avoiding the neede to duplcate each string
> >see AV_STRINGIFY
>
> I changed it, is it ok like
On Thu, Nov 30, 2017 at 2:43 PM, Carl Eugen Hoyos wrote:
> 2017-09-27 22:26 GMT+02:00 Hendrik Leppkes :
>> On Wed, Sep 27, 2017 at 10:11 PM, Mateusz wrote:
>>> W dniu 2017-09-27 o 17:40, Hendrik Leppkes pisze:
On Wed, Sep 27,
2017-09-27 22:26 GMT+02:00 Hendrik Leppkes :
> On Wed, Sep 27, 2017 at 10:11 PM, Mateusz wrote:
>> W dniu 2017-09-27 o 17:40, Hendrik Leppkes pisze:
>>> On Wed, Sep 27, 2017 at 4:43 PM, Anonymous Maarten
>>> wrote:
Le jeu. 30 nov. 2017 à 01:51, Michael Niedermayer
a écrit :
> On Wed, Nov 29, 2017 at 11:28:40AM +, Marc-Antoine ARNAUD wrote:
> > Le mer. 22 nov. 2017 à 17:54, Michael Niedermayer >
> > a écrit :
> >
> > > On Wed, Nov 22, 2017 at 10:24:30AM
On 28 November 2017 at 01:26, Michael Niedermayer
wrote:
> On Mon, Nov 27, 2017 at 04:30:18AM +, Rostislav Pehlivanov wrote:
> > Signed-off-by: Rostislav Pehlivanov
> > ---
> > libavcodec/parser.c | 14 --
> > 1 file changed, 8
2017-11-30 19:32 GMT+08:00 :
> From: Vishwanath Dixit
>
> ---
> libavformat/Makefile | 2 +-
> libavformat/dashenc.c | 2 +-
> libavformat/hlsenc.c | 65
> +--
> libavformat/hlsplaylist.c | 5
On 29 November 2017 at 16:40, Michael Niedermayer
wrote:
> On Wed, Nov 29, 2017 at 03:51:34AM +, Rostislav Pehlivanov wrote:
> > On 28 November 2017 at 20:23, Michael Niedermayer >
> > wrote:
> >
> > > On Mon, Nov 27, 2017 at 04:30:19AM
From: Vishwanath Dixit
---
libavformat/Makefile | 2 +-
libavformat/dashenc.c | 2 +-
libavformat/hlsenc.c | 65 +--
libavformat/hlsplaylist.c | 5 +++-
libavformat/hlsplaylist.h | 3 ++-
libavformat/reverse.c
From: Vishwanath Dixit
---
libavcodec/libx264.c | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
index 9c67c91..545826c 100644
--- a/libavcodec/libx264.c
+++ b/libavcodec/libx264.c
@@ -19,11
On 11/30/2017 4:19 PM, Clément Bœsch wrote:
Is --disable-autodetect broken/not complete for you?
This disables more than just the hwaccel libs. I've tested my patch
locally and configure lists no entries under External Libraries
Providing Hardware Acceleration, unlike with
On Thu, Nov 30, 2017 at 03:58:21PM +0530, Gyan Doshi wrote:
> I added --disable-hwaccels during configure and noticed that all
> autodetected hwaccel libs were still being linked - 6 in my case, which
> makes for a more bloated binary than warranted.
>
> Turns out the option only disables native
I added --disable-hwaccels during configure and noticed that all
autodetected hwaccel libs were still being linked - 6 in my case, which
makes for a more bloated binary than warranted.
Turns out the option only disables native components which make use of
the hwaccel libs. The reporter of
Dear Mark,
On Thu, Nov 30, 2017 at 4:53 AM, Mark Reid wrote:
> clang give me a warning telling to do this instead
> packages[3] = {{0}};
> I assume thats correct as I see thats used throughout the codebase.
Ah yes, that's perfect - good catch.
Kind regards,
Matthias
On Thu, Nov 30, 2017 at 10:40 AM, Li, Zhong wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of Mark Thompson
>> Sent: Thursday, November 30, 2017 7:30 AM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: [FFmpeg-devel]
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: Thursday, November 30, 2017 7:30 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 2/2] vaapi_h265: Add named options for
> setting profile and level
>
>
Sorry, my mail client swallowed the attachment, sent it again.
0001-avdevice-add-android_camera-indev.patch
Description: Binary data
> Am 30.11.2017 um 10:12 schrieb Felix Matouschek :
>
> Am 29.11.2017 04:31, schrieb Michael Niedermayer:
>
>> if the identifer and the
On 11/30/17, wm4 wrote:
> On Wed, 29 Nov 2017 23:15:44 +0100
> Paul B Mahol wrote:
>
>> Signed-off-by: Paul B Mahol
>> ---
>> doc/filters.texi | 4
>> libavfilter/vf_stereo3d.c | 35 ---
>>
Am 29.11.2017 04:31, schrieb Michael Niedermayer:
if the identifer and the string always match you could do this
with a macro avoiding the neede to duplcate each string
see AV_STRINGIFY
I changed it, is it ok like this?
[...]
+static int add_video_stream(AVFormatContext *avctx)
+{
+
From: Karthick Jeyapal
Before this patch persistent http connections would work only for media
segments.
The playlists were still opening a new connection everytime.
This patch extends persistent http connections to playlists as well.
---
libavformat/hlsenc.c | 46
From: Karthick Jeyapal
Since close is not called, during http persistent connection,
flush needs to be called so that output is written on time.
---
libavformat/hlsenc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index
From: Karthick Jeyapal
---
libavformat/hlsenc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 9048cb2..ff982c5 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -244,7 +244,7 @@ static
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> +#define LEVEL(name, value) name, NULL, 0, AV_OPT_TYPE_CONST, \
> + { .i64 = value }, 0, 0, FLAGS, "level"
> +{ LEVEL("1", 10) },
> +{ LEVEL("1.1", 11) },
> +{ LEVEL("1.2", 12) },
> +
72 matches
Mail list logo