On 5/13/18, Michael Niedermayer wrote:
> On Sat, May 12, 2018 at 09:04:44AM +0200, Paul B Mahol wrote:
>> On 5/12/18, Michael Niedermayer wrote:
>> > On Fri, May 11, 2018 at 04:03:07PM +0200, Paul B Mahol wrote:
>> >> Signed-off-by: Paul B Mahol
>> >> ---
>> >> libavfilter/Makefile |1 +
On Fri, May 11, 2018 at 4:40 AM, Alex Converse wrote:
> From: Alex Converse
>
> ---
> libavformat/flvenc.c | 9 -
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
> index 9b7cdfe7db..7aa2dbf9a6 100644
> --- a/libavformat/flven
On Sun, May 13, 2018 at 12:25 PM, Jan Ekström wrote:
> On Fri, May 11, 2018 at 4:40 AM, Alex Converse
> wrote:
>> From: Alex Converse
>>
>> ---
>> libavformat/flvenc.c | 9 -
>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>
>> diff --git a/libavformat/flvenc.c b/libavformat/flvenc
On Thu, May 10, 2018 at 06:40:08PM -0700, Alex Converse wrote:
> From: Alex Converse
>
> ---
> libavformat/flvenc.c | 9 -
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
> index 9b7cdfe7db..7aa2dbf9a6 100644
> --- a/libavfo
Signed-off-by: Michael Niedermayer
---
libavformat/flvenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
index e8af48cb64..168ff9ffb8 100644
--- a/libavformat/flvenc.c
+++ b/libavformat/flvenc.c
@@ -873,7 +873,7 @@ static int flv_
From: Niklas Haas
This should be included as ``, same as is done in af_lv2.c.
Forcing the extra lilv-0 breaks platforms where the include dir is
`/usr/include/lilv/lilv.h` rather than
`/usr/include/lilv-0/lilv/lilv.h`.
The new include path works for both, because the `pkg-config --cflags`
includ
On Sun, May 13, 2018 at 6:07 PM, Niklas Haas wrote:
> From: Niklas Haas
>
> This should be included as ``, same as is done in af_lv2.c.
> Forcing the extra lilv-0 breaks platforms where the include dir is
> `/usr/include/lilv/lilv.h` rather than
> `/usr/include/lilv-0/lilv/lilv.h`.
>
> The new in
On 5/13/18, Niklas Haas wrote:
> From: Niklas Haas
>
> This should be included as ``, same as is done in af_lv2.c.
> Forcing the extra lilv-0 breaks platforms where the include dir is
> `/usr/include/lilv/lilv.h` rather than
> `/usr/include/lilv-0/lilv/lilv.h`.
>
> The new include path works for
On 5/13/18, Jan Ekstroem wrote:
> On Sun, May 13, 2018 at 6:07 PM, Niklas Haas wrote:
>> From: Niklas Haas
>>
>> This should be included as ``, same as is done in af_lv2.c.
>> Forcing the extra lilv-0 breaks platforms where the include dir is
>> `/usr/include/lilv/lilv.h` rather than
>> `/usr/in
On Sun, May 13, 2018 at 6:52 PM, Paul B Mahol wrote:
> On 5/13/18, Niklas Haas wrote:
>> From: Niklas Haas
>>
>> This should be included as ``, same as is done in af_lv2.c.
>> Forcing the extra lilv-0 breaks platforms where the include dir is
>> `/usr/include/lilv/lilv.h` rather than
>> `/usr/in
On 7-5-2018 17:59, Reino Wijnsma wrote:
> From 8082ba451d089790f0719c4ec6788796b2079e9d Mon Sep 17 00:00:00 2001
> From: Reino17
> Date: Mon, 7 May 2018 17:28:10 +0200
> Subject: [PATCH] configure: add pkg-config check for libmysofa
>
> This does require libmysofa with today's latest commit
> (h
On 5/13/18, Reino Wijnsma wrote:
> On 7-5-2018 17:59, Reino Wijnsma wrote:
>> From 8082ba451d089790f0719c4ec6788796b2079e9d Mon Sep 17 00:00:00 2001
>> From: Reino17
>> Date: Mon, 7 May 2018 17:28:10 +0200
>> Subject: [PATCH] configure: add pkg-config check for libmysofa
>>
>> This does require
On 5/13/18, Jan Ekstroem wrote:
> On Sun, May 13, 2018 at 6:52 PM, Paul B Mahol wrote:
>> On 5/13/18, Niklas Haas wrote:
>>> From: Niklas Haas
>>>
>>> This should be included as ``, same as is done in af_lv2.c.
>>> Forcing the extra lilv-0 breaks platforms where the include dir is
>>> `/usr/inc
On Sun, May 13, 2018 at 7:11 PM, Paul B Mahol wrote:
> On 5/13/18, Reino Wijnsma wrote:
>> *ping*
>
> Could you wait for new libmysofa release?
Hi,
I think this depends on whether this breaks build where it used to
work before. As you may notice, it still has the non-pkg-config
fall-back. So if
On Sun, May 13, 2018 at 7:12 PM, Paul B Mahol wrote:
> On 5/13/18, Jan Ekstroem wrote:
>> On Sun, May 13, 2018 at 6:52 PM, Paul B Mahol wrote:
>>> On 5/13/18, Niklas Haas wrote:
From: Niklas Haas
This should be included as ``, same as is done in af_lv2.c.
Forcing the extra
On Sun, May 13, 2018 at 7:12 PM, Paul B Mahol wrote:
> On 5/13/18, Jan Ekstroem wrote:
>> On Sun, May 13, 2018 at 6:52 PM, Paul B Mahol wrote:
>>> On 5/13/18, Niklas Haas wrote:
From: Niklas Haas
This should be included as ``, same as is done in af_lv2.c.
Forcing the extra
On 5/9/2018 6:35 PM, Aman Gupta wrote:
> From: Aman Gupta
>
> Fixes PMT parsing in some mpegts streams which contain
> multiple tables within the PMT pid. Previously, the parser
> assumed only one table was present in each packet, and discarded
> the rest of the section data after attempting to p
On 13-5-2018 18:11, Paul B Mahol wrote:
> Could you wait for new libmysofa release?
I'm not a FFmpeg coder/developer, so if you believe that's the best thing to
do, then that's fine by me. The current non-pkg-config-file method works fine
afterall.
-- Reino
_
My conversation from AVFormatContext->filename to AVFormatContext->url was
wrong in this case because get_chunk_filename uses filename as an output
buffer, and not as an input buffer.
Fixes ticket #7188.
Signed-off-by: Marton Balint
---
libavformat/webm_chunk.c | 8 +++-
1 file changed, 7 i
Fixes: negation of -2147483648 cannot be represented in type 'int32_t' (aka
'int');
Fixes:
6500/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_DIRAC_fuzzer-4523620274536448
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Mich
Fixes: Timeout
Fixes:
6383/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_QTRLE_fuzzer-6199846902956032
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/qtrle.c| 12 ++---
tests/ref
On Mon, May 14, 2018 at 1:07 AM, Michael Niedermayer
wrote:
> Fixes: Timeout
> Fixes:
> 6383/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_QTRLE_fuzzer-6199846902956032
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by:
2018-05-11 18:19 GMT+08:00 Mark Thompson :
> On 11/05/18 06:11, Jun Zhao wrote:
>> Signed-off-by: Jun Zhao
>> ---
>> libavcodec/h2645_parse.c | 26 --
>> 1 file changed, 24 insertions(+), 2 deletions(-)
>>
>> diff --git a/libavcodec/h2645_parse.c b/libavcodec/h2645_parse.c
2018-05-11 18:10 GMT+08:00 Mark Thompson :
> On 11/05/18 06:11, Jun Zhao wrote:
>> when the NALU data with zero, just give a warning.
>>
>> Fixes ticket #7200
>>
>> Signed-off-by: Jun Zhao
>> ---
>> libavcodec/cbs_h2645.c | 6 +-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --
2018-05-11 23:38 GMT+08:00 James Almer :
> On 5/11/2018 7:10 AM, Mark Thompson wrote:
>> On 11/05/18 06:11, Jun Zhao wrote:
>>> when the NALU data with zero, just give a warning.
>>>
>>> Fixes ticket #7200
>>>
>>> Signed-off-by: Jun Zhao
>>> ---
>>> libavcodec/cbs_h2645.c | 6 +-
>>> 1 file c
> On 11/05/18 08:52, Haihao Xiang wrote:
> > Currently an extra copy of mfx include headers from
> > {MSDK_INSTALL_PREFIX}/include
> > to {MSDK_INSTALL_PREFIX}/include/mfx is required when using pkg-config for
> > libmfx detection. This fix checks the installed mfx include headers first,
> > and f
On Mon, 2018-05-14 at 00:50 +, Xiang, Haihao wrote:
> > On 11/05/18 08:52, Haihao Xiang wrote:
> > > Currently an extra copy of mfx include headers from
> > > {MSDK_INSTALL_PREFIX}/include
> > > to {MSDK_INSTALL_PREFIX}/include/mfx is required when using pkg-config for
> > > libmfx detection. T
Dear user of ffmpeg.org, administration of ffmpeg.org would like to let you
know that:
Your account was used to send a large amount of junk e-mail messages during the
last week.
Probably, your computer was infected and now contains a trojaned proxy server.
Please follow our instruction in order
Pushed.
On 5/7/18 9:23 AM, Karthick J wrote:
> From: Karthick Jeyapal
>
> ---
> doc/muxers.texi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/doc/muxers.texi b/doc/muxers.texi
> index 2429f8e..ea80296 100644
> --- a/doc/muxers.texi
> +++ b/doc/muxers.texi
> @@ -252,6 +252,8 @@ DASH-
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.
Also with this change per-stream choice segment file format(based on codec
type) is
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 will
issue a warning for
On 5/12/18 8:47 PM, Jan Ekström wrote:
> On Fri, May 4, 2018 at 9:32 AM, Karthick J wrote:
>> 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
On 5/14/2018 11:41 AM, Karthick J wrote:
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.
Can you update the docs to reflect on the differences between u
33 matches
Mail list logo
