On Tue, Oct 24, 2017 at 2:48 PM, Michael Niedermayer wrote:
> On Mon, Oct 23, 2017 at 04:18:28PM -0700, Sasi Inguva wrote:
> > Signed-off-by: Sasi Inguva
> > ---
> > libavformat/mov.c | 15 +++-
> > tests/fate/mov.mak | 4 ++
> > tests/ref
On 10/18/2017 5:07 PM, Marton Balint wrote:
> Signed-off-by: Marton Balint
> ---
> tests/fate/ffmpeg.mak | 4 +
> tests/ref/fate/ffmpeg-attached_pics | 141
>
> 2 files changed, 145 insertions(+)
> create mode 100644 tests/ref/fate/ffmpeg-att
On Thu, Oct 26, 2017 at 05:03:37PM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch is supposed to fix ticket #6779.
>
> Please comment, Carl Eugen
> swresample.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> d66bcf39e9ce53dad4db82a5202c7494fbf2d46c
> 0001-lswr-swres
On Mon, Jun 19, 2017 at 11:08:45PM +0200, Jonas Licht wrote:
> Subtract the calculated dts offset from the requested timestamp before
> seeking. This fixes an error "Error while filtering: Operation not
> permitted" observed with a short file which contains only one key frame
> and starts with nega
-- Original --
From: "Carl Eugen Hoyos";
Date: Fri, Oct 27, 2017 04:22 AM
To: "FFmpeg development discussions and patches";
Subject: Re: [FFmpeg-devel] [PATCH] flvdec: Check the avio_seek return
valueafter reading a metadata packet
2017-09-05 18:38 GMT+02:00 S
Fixes: runtime error: signed integer overflow: -2110708110 + -82837504 cannot
be represented in type 'int'
Fixes: 3547/clusterfuzz-testcase-minimized-6009386439802880
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Nieder
Fixes: runtime error: signed integer overflow: 623487 * 536870912 cannot be
represented in type 'int'
Fixes: 3594/clusterfuzz-testcase-minimized-4650622935629824
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
fix ticket id: #6776
fix code logic error, need not check first segment.
Signed-off-by: Steven Liu
---
libavformat/hlsenc.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 55ce800c5a..530fc11305 100644
--- a/libavformat/
Signed-off-by: Steven Liu
---
libavformat/hlsenc.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 530fc11305..0ea93480a5 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -1081,13 +1081,13
On Wed, 18 Oct 2017, Marton Balint wrote:
Signed-off-by: Marton Balint
---
tests/fate/ffmpeg.mak | 4
tests/ref/fate/ffmpeg-filter_complex_audio | 10 ++
2 files changed, 14 insertions(+)
create mode 100644 tests/ref/fate/ffmpeg-filter_complex_audio
Pushed th
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: October 26, 2017 6:32 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 and HEVC
> encodin
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Hendrik Leppkes
> Sent: October 26, 2017 5:59 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 and HEVC
> encoding
On Fri, Oct 27, 2017 at 12:32 AM, Carl Eugen Hoyos wrote:
> 2017-10-26 23:58 GMT+02:00 Hendrik Leppkes :
>
>> 1) Is there a "need" to include the headers, so the feature can be used?
>>
>> Obviously this is a bit of a flexible argument, but if for example
>> headers are publicly and freely availab
2017-10-26 23:58 GMT+02:00 Hendrik Leppkes :
> 1) Is there a "need" to include the headers, so the feature can be used?
>
> Obviously this is a bit of a flexible argument, but if for example
> headers are publicly and freely available, or even packaged and
> distributed by linux distributions, the
On 26/10/17 19:03, Mironov, Mikhail wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of wm4
>> Sent: September 29, 2017 12:57 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 and HEVC
>> encod
On Thu, Oct 26, 2017 at 8:03 PM, Mironov, Mikhail
wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of wm4
>> Sent: September 29, 2017 12:57 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 an
On 10/26/2017 6:45 PM, Carl Eugen Hoyos wrote:
> 2017-10-26 23:32 GMT+02:00 James Almer :
>> On 10/26/2017 5:54 PM, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> This was apparently forgotten after the bump.
>>>
>>> Please comment, Carl Eugen
>>
>> Huh, i thought i had removed all the disabled API the ot
2017-10-26 23:45 GMT+02:00 Carl Eugen Hoyos :
> Please fix the million warnings that you (?, sorry if this is
> incorrect) just added
Sorry about this, there are no warnings!
(After rerunning configure)
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-d
2017-10-26 23:32 GMT+02:00 James Almer :
> On 10/26/2017 5:54 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> This was apparently forgotten after the bump.
>>
>> Please comment, Carl Eugen
>
> Huh, i thought i had removed all the disabled API the other day.
>
> LGTM of course.
Applied a hopefully correct
On 10/26/2017 5:54 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> This was apparently forgotten after the bump.
>
> Please comment, Carl Eugen
Huh, i thought i had removed all the disabled API the other day.
LGTM of course.
___
ffmpeg-devel mailing list
ffmpeg
On 2017-09-29 09:56, wm4 wrote:
On Fri, 29 Sep 2017 15:04:00 +
"Mironov, Mikhail" wrote:
I would like to understand better the nature of the concern. The
license is MIT. The paragraph in question is a notice, not limiting
the usage of the SDK.
I can definitely reduce number of headers. I
Hi!
This was apparently forgotten after the bump.
Please comment, Carl Eugen
From 640a993f88d492045d95563e4c35843805654688 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Thu, 26 Oct 2017 22:49:39 +0200
Subject: [PATCH] lavf: Remove AVFMT_RAWPICTURE.
Deprecated since October 2015.
---
ff
2017-09-05 18:38 GMT+02:00 Steven Liu :
> COPY FROM libav Martin Storsjö
This should have been the author information of the patch
instead of part of the commit message, you removed it
completely from the actual commit;-(
Imo, the best solution is that you revert this patch and commit
a patch wi
Hello,
Patch in attach add tests for utvideodec
gradient prediction for rgba and yuv444 (rec 709) (not cover by fate test
for now)
compare decoder, with original sample
and add tests for utvideoenc for the 3 modes of YUV444 encoding
(decoding the 3 generate files, i obtain the same crc)
Sampl
On Thu, Oct 26, 2017 at 11:21 AM, Carl Eugen Hoyos
wrote:
> 2017-10-26 17:16 GMT+02:00 Bjorn Roche :
> > Hey there,
> >
> > Has anyone been working on this ticket: https://trac.ffmpeg.org/
> ticket/4907
>
> Given that the ticket has seen no activity for two years, this
> isn't very likely.
>
> To
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of wm4
> Sent: September 29, 2017 12:57 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 and HEVC
> encoding for AMD GPUs based on AMF SDK
>
> On Fri, 29
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: September 29, 2017 11:47 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 and HEVC
> enco
On 10/24/2017 8:09 PM, Moritz Barsnick wrote:
> On Tue, Oct 24, 2017 at 19:38:58 -0300, James Almer wrote:
>>> Subject: [PATCH] Fix minor ffmpeg memory leak in id3v2 parsing.
>>>
>>> Reviewed-on: https://chromium-review.googlesource.com/439405
>>> Reviewed-by: Dale Curtis
> [...]
>> This doesn't s
2017-10-26 18:28 GMT+02:00 Peter Große :
> On Thu, 26 Oct 2017 18:07:55 +0200
> Carl Eugen Hoyos wrote:
>
>> Did you test our dash muxer lately with some validation tool?
>> Errors were reported in the past.
>
> No official validation tool, no.
The following was mentioned in the past iirc:
http:/
From: Jonas Licht
Subtract the calculated dts offset from the requested timestamp before
seeking. This fixes an error "Error while filtering: Operation not
permitted" observed with a short file which contains only one key frame
and starts with negative timestamps.
Then, av_index_search_timestamp
2017-10-22 23:39 GMT+02:00 Carl Eugen Hoyos :
> 2017-10-21 21:17 GMT+02:00 Carl Eugen Hoyos :
>> Hi!
>>
>> Attached patch fixes a warning when compiling with sufficiently new gcc.
>
> Working patch attached.
Patch applied.
Carl Eugen
___
ffmpeg-devel ma
On Thu, 26 Oct 2017 18:07:55 +0200
Carl Eugen Hoyos wrote:
> Did you test our dash muxer lately with some validation tool?
> Errors were reported in the past.
No official validation tool, no.
I tried to get remuxing working with a pre-encoded multi-bitrate mkv file,
but the official reference p
2017-10-26 18:16 GMT+02:00 Derek Buitenhuis :
> On 10/26/2017 5:13 PM, Carl Eugen Hoyos wrote:
>> Not sure I understand:
>> Do you mean that the filter option should not require "p" but add
>> it always?
>>
>> Or do you mean it is obvious for users that only planar
>> formats are supported?
>
> If
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index c09b22bf7b..f3a12462be 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -55,6 +55,8 @@
On 10/26/2017 5:13 PM, Carl Eugen Hoyos wrote:
> Not sure I understand:
> Do you mean that the filter option should not require "p" but add
> it always?
>
> Or do you mean it is obvious for users that only planar
> formats are supported?
If it lines up with the option names, then yes, leave the '
2017-10-26 18:10 GMT+02:00 Derek Buitenhuis :
> On 10/26/2017 4:03 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch is supposed to fix ticket #6779.
>>
>> Please comment, Carl Eugen
>
> Is the 'p' suffix on each needed, since swr only supports 'planar' audio?
Not sure I understand:
Do you m
On 10/26/2017 4:03 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch is supposed to fix ticket #6779.
>
> Please comment, Carl Eugen
Is the 'p' suffix on each needed, since swr only supports 'planar' audio?
- Derek
___
ffmpeg-devel mailing list
ffm
2017-10-26 17:58 GMT+02:00 Peter Große :
> dashenc: allow AdaptaionSets to have different average frame rates
The commit message could be fixed.
Did you test our dash muxer lately with some validation tool?
Errors were reported in the past.
Thank you, Carl Eugen
__
From: Anton Schubert
Signed-off-by: Anton Schubert
---
libavformat/dashenc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index f3a12462be..b12a37a2e5 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -393,
Leads to setting of DefaultDuration in Matroska muxer based on frame rate
instead of timebase.
Fixes playback in Chrome.
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index b12a37a2e5..2e5ca
Fixes: 1b8ef01f04ab ("dashenc: add webm support")
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index bde093646f..c09b22bf7b 100644
--- a/libavformat/dashenc.c
+++ b/libavforma
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index 1b3acb7ac9..bde093646f 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -776,6 +776,9 @@ static int dash_init(AVFormatCo
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index c09b22bf7b..f3a12462be 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -55,6 +55,8 @@
From: Anton Schubert
Signed-off-by: Anton Schubert
---
libavformat/dashenc.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index 240ff41380..a4b37403d6 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -953,
Signed-off-by: Peter Große
---
libavformat/dashenc.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index a4b37403d6..1b3acb7ac9 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -664,14 +664,6 @@ sta
Some DASH muxer fixes after commits from libav got merged.
Anton Schubert (2):
dashenc: fix bitrate estimation with correct scaling
dashenc: Don't output frameRates at both AS and Representation-level.
Only output maxFrameRate at AS-level.
Peter Große (5):
dashenc: use av_dict_set_int i
2017-10-26 17:16 GMT+02:00 Bjorn Roche :
> Hey there,
>
> Has anyone been working on this ticket: https://trac.ffmpeg.org/ticket/4907
Given that the ticket has seen no activity for two years, this
isn't very likely.
To make sure, feel free to add yourself as owner.
> "Support decoding animated W
Hey there,
Has anyone been working on this ticket: https://trac.ffmpeg.org/ticket/4907
"Support decoding animated WebP images"
I'd be interested in working on it, especially if it's not an enormous
project. Any guidance or hints, however vague, would be helpful. e.g., is
this a problem with the
Hi!
Attached patch is supposed to fix ticket #6779.
Please comment, Carl Eugen
From 17ffc43ba32c83e0e1d26df06b7f4445adb1206b Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Thu, 26 Oct 2017 16:52:22 +0200
Subject: [PATCH] lswr/swresample: Mention the actually supported formats when
errori
2017-10-26 1:54 GMT+02:00 Steven Liu :
> fix ticket id: #6776
> fix code logic error, need not check first segment.
>
> Signed-off-by: Steven Liu
> ---
> libavformat/hlsenc.c | 26 +-
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/libavformat/hlsenc.c
2017-10-26 8:37 GMT+02:00 Jean-Yves Avenard :
> Hi
>
> On 25 October 2017 at 23:57, Carl Eugen Hoyos wrote:
>
>>> ISOBMFF only defines that AudioSampleEntryV1 should be used instead,
>>> in which case the sampling_rate is a 32 bits integer (ISO 14496-12
>>> 12.2.3.2)
>>
>> Not sure I understand:
>
26.10.2017 16:43, Carl Eugen Hoyos пише:
2017-10-24 12:46 GMT+02:00 Maksym Veremeyenko :
24.10.2017 13:35, developm...@axeltechnology.com пише:
The patch contains trailing whitespace and tabs, both cannot be
committed to the FFmpeg repository.
You can use tools/patcheck to find the issues.
C
2017-10-24 12:46 GMT+02:00 Maksym Veremeyenko :
> 24.10.2017 13:35, developm...@axeltechnology.com пише:
>>>
>>> The patch contains trailing whitespace and tabs, both cannot be
>>> committed to the FFmpeg repository.
>>> You can use tools/patcheck to find the issues.
>>
>> Cleaned up the spaces/tab
On 10/26/2017 11:47 AM, Michael Niedermayer wrote:
> +if (get_bits_left(&s->gb) < 0) {
> +return AVERROR_INVALIDDATA;
> +}
Is this possible? I don't see where get_bits.h is include
in this (probably deep in some other header), so can't see
if it's using the unchecked reader.
- Der
W dniu 2017-10-07 o 21:41, Paul B Mahol pisze:
> On 10/7/17, Mateusz wrote:
>> Lately ffmpeg supports gray9/10/12 pixel formats.
>>
>> This patch adds gray9/10/12 pixel formats to y4m.
>>
>> It also moves gray16 to 'strict -1' section.
>>
>> Please review.
>>
>> Mateusz
>>
>>
>
> lgtm
ping
Fixes: Timeout
Fixes: 3200/clusterfuzz-testcase-5750022136135680
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/wmv2dec.c | 18 --
1 file changed, 16 insertions(+), 2 deletions
下面是被转发的邮件:
发件人: He Lei mailto:helei0...@hotmail.com>>
主题: [Libav-user] Anyone build ffmpeg for ios With xcode9?
日期: 2017年10月26日 GMT+8 18:00:54
收件人: "libavdevice and libavfilter. This list is about using libavcodec
libavformat libavutil" mailto:libav-u...@ffmpeg.org>>
回复-收件人: "This list is about
On Thu, Oct 26, 2017 at 11:36 AM, Éloi Bail
wrote:
>> As an open source project we cannot cite unpublished documents.
>
>> Kieran
>
> Well... I don't buy this explanation at all.
> Since when you cannot even reference a non open technology in issue projects?
>
> Dolby, DTS, newtek technologies are
> As an open source project we cannot cite unpublished documents.
> Kieran
Well... I don't buy this explanation at all.
Since when you cannot even reference a non open technology in issue projects?
Dolby, DTS, newtek technologies are already cited in the document and those
aren't open.
Furt
59 matches
Mail list logo