On 22 October 2016 at 01:17, Kieran Kunhya wrote:
> On Fri, 21 Oct 2016, 20:05 Marton Balint, wrote:
>
> >
> > On Thu, 20 Oct 2016, Michael Niedermayer wrote:
> >
> > > On Tue, Oct 18, 2016 at 05:36:27PM -0700, Carlos Fernandez Sanz wrote:
> > >> From: Carlos
Hello everybody,
as far as I could see ffmpeg from the 'master' branch doesn't add custom
HTTP headers (specified by means of '-headers' option) to the requests
when 'segment' format is used (checked on August 31st.)
I prepared a patch that allows to use custom headers along with
'segment'
---
libavformat/rtmpproto.c | 49 +
1 file changed, 37 insertions(+), 12 deletions(-)
diff --git a/libavformat/rtmpproto.c b/libavformat/rtmpproto.c
index 95d1c1d..8a3 100644
--- a/libavformat/rtmpproto.c
+++ b/libavformat/rtmpproto.c
@@ -227,6
On 10/21/2016 10:30 PM, Carl Eugen Hoyos wrote:
2016-09-27 9:15 GMT+02:00 Carl Eugen Hoyos :
2016-09-27 6:45 GMT+02:00 Stephen Hutchinson :
Ping.
Consider sending your public key to Michael, you maintain this code.
Ping.
Carl Eugen
On 10/17/2016 9:48 PM, Stephen Hutchinson wrote:
On 9/27/2016 10:07 PM, Stephen Hutchinson wrote:
On 9/27/2016 4:11 PM, Michael Niedermayer wrote:
can you update the status for the patch(es) on
https://patchwork.ffmpeg.org/project/ffmpeg/list/?submitter=49
?
so developers know what needs a
2016-09-27 9:15 GMT+02:00 Carl Eugen Hoyos :
> 2016-09-27 6:45 GMT+02:00 Stephen Hutchinson :
>
>> Ping.
>
> Consider sending your public key to Michael, you maintain this code.
Ping.
Carl Eugen
___
ffmpeg-devel
On 8/30/2016 8:26 PM, Stephen Hutchinson wrote:
---
libavformat/avisynth.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavformat/avisynth.c b/libavformat/avisynth.c
index 1fe8e08..1acc44f 100644
--- a/libavformat/avisynth.c
+++ b/libavformat/avisynth.c
@@ -690,8
2016-10-14 15:12 GMT+02:00 Carl Eugen Hoyos :
> Attached patch fixes ticket #5890, completely untested.
Patch applied.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
It is negative, so can't be used for left shifting.
This fixes ubsan runtime error: shift exponent -1 is negative
Signed-off-by: Andreas Cadhalpun
---
libavformat/mpegts.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On 22.10.2016 00:18, Michael Niedermayer wrote:
> On Mon, Oct 17, 2016 at 08:49:23PM +0200, Andreas Cadhalpun wrote:
>> The parser depends on the codec and thus must not be used with a different
>> one.
>> If it is, the 'avctx->codec_id == s->parser->codec_ids[0] ...' assert in
>>
On Mon, Oct 17, 2016 at 08:49:23PM +0200, Andreas Cadhalpun wrote:
> The parser depends on the codec and thus must not be used with a different
> one.
> If it is, the 'avctx->codec_id == s->parser->codec_ids[0] ...' assert in
> av_parser_parse2 gets triggered.
>
> Signed-off-by: Andreas
On 22/10/16 01:06, James Zern wrote:
> From: Kagami Hiiragi
>
> vp9_cx_iface actually allows values in range [0..2].
> This fixes ticket #5894.
>
> Signed-off-by: Kagami Hiiragi
> ---
> libavcodec/libvpxenc.c | 5 +++--
> 1 file changed, 3
From: Kagami Hiiragi
vp9_cx_iface actually allows values in range [0..2].
This fixes ticket #5894.
Signed-off-by: Kagami Hiiragi
---
libavcodec/libvpxenc.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
On Fri, Oct 21, 2016 at 4:55 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Thu, Oct 20, 2016 at 11:14 PM, James Zern > wrote:
>
>> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi
>> wrote:
>> > vp9_cx_iface actually allows
On 21.10.2016 23:47, Lou Logan wrote:
> On Fri, Oct 21, 2016, at 01:21 PM, Andreas Cadhalpun wrote:
>>
>> Updated patch is attached.
>
> LGTM, thanks.
Pushed.
Best regards,
Andreas
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Fri, Oct 21, 2016 at 1:22 AM, James Zern wrote:
> On Fri, Oct 21, 2016 at 1:14 AM, Kagami Hiiragi wrote:
>> On 21/10/16 06:14, James Zern wrote:
>>> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi
>>> wrote:
vp9_cx_iface
On Fri, Oct 21, 2016, at 01:21 PM, Andreas Cadhalpun wrote:
>
> Updated patch is attached.
LGTM, thanks.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 21.10.2016 22:12, Lou Logan wrote:
> On Thu, Oct 13, 2016, at 01:25 PM, Andreas Cadhalpun wrote:
> [...]
>> @item mgain
>> Set max gain that will be displayed. Only useful if curves option is
>> activated.
>> -Setting this to reasonable value allows to display gain which is derived
>> from
On Thu, Oct 20, 2016 at 12:06:14 -0400, Ronald S. Bultje wrote:
> +s->did_range_warn = 1;
> +}
> // fall-through
> +}
> case AVCOL_RANGE_MPEG:
The fall-through comment seems misplaced now (both logically and
probably for Coverity).
Moritz
On Thu, Oct 13, 2016, at 01:25 PM, Andreas Cadhalpun wrote:
[...]
> @item mgain
> Set max gain that will be displayed. Only useful if curves option is
> activated.
> -Setting this to reasonable value allows to display gain which is derived
> from
> +Setting this to reasonable value allows one
On Thu, 20 Oct 2016, Michael Niedermayer wrote:
On Tue, Oct 18, 2016 at 05:36:28PM -0700, Carlos Fernandez Sanz wrote:
From: Carlos Fernandez
Signed-off-by: Carlos Fernandez
---
libavformat/mpegts.c | 47
On Thu, 20 Oct 2016, Michael Niedermayer wrote:
On Tue, Oct 18, 2016 at 05:36:27PM -0700, Carlos Fernandez Sanz wrote:
From: Carlos Fernandez
Signed-off-by: Carlos Fernandez
---
libavcodec/avcodec.h| 1 +
libavcodec/codec_desc.c | 6
On Fri, 14 Oct 2016, Marton Balint wrote:
Signed-off-by: Marton Balint
---
doc/indevs.texi | 4
libavdevice/decklink_common.h | 1 +
libavdevice/decklink_common_c.h | 1 +
libavdevice/decklink_dec.cpp| 3 ++-
libavdevice/decklink_dec_c.c| 1 +
On 21/10/16 19:14, Mark Thompson wrote:
> Merged as-at libav 398f015, and therefore includes outstanding skipped
> merges 04b17ff and 130e1f1.
>
> All features not in libav are preserved, and no options change.
For comparison, here is the resulting diff from libav at 398f015.
diff -ur
Merged as-at libav 398f015, and therefore includes outstanding skipped
merges 04b17ff and 130e1f1.
All features not in libav are preserved, and no options change.
---
As discussed previously, this replaces the libmfx implementation in ffmpeg with
the current version from libav as at the merge
On 10/21/2016 6:47 PM, Sasi Inguva wrote:
> * Audio packets. Especially audio packets with a large number of
> samples.
> It's extremely likely that edits will not fall on packet
> boundaries, and
> depending on the number of samples per packet, audio sync issues
>
On 17.10.2016 20:49, Andreas Cadhalpun wrote:
> The parser depends on the codec and thus must not be used with a different
> one.
> If it is, the 'avctx->codec_id == s->parser->codec_ids[0] ...' assert in
> av_parser_parse2 gets triggered.
>
> Signed-off-by: Andreas Cadhalpun
On 13.10.2016 23:25, Andreas Cadhalpun wrote:
> Thanks to Mathieu Malaterre for reporting the
> Que/Queue typo. (https://bugs.debian.org/839542)
>
> Signed-off-by: Andreas Cadhalpun
> ---
> doc/Doxyfile| 2 +-
>
On 21.10.2016 01:32, Michael Niedermayer wrote:
> On Thu, Oct 20, 2016 at 08:11:19PM +0200, Andreas Cadhalpun wrote:
>> aiffdec.c |5 +
>> 1 file changed, 5 insertions(+)
>> 2fb78e5573b52b635b5077a265a54542e054cf02
>> 0001-aiff-check-block_align-in-aiff_read_packet.patch
>> From
On Fri, Oct 21, 2016 at 8:32 AM, Derek Buitenhuis <
derek.buitenh...@gmail.com> wrote:
> > In YouTube we have long been receiving MOV files from users, which have
> non-trivial edit lists (Those edit lists which are not just used to offset
> video start from audio start) and multiple edit lists.
On 21.10.2016 02:36, Michael Niedermayer wrote:
> On Thu, Oct 20, 2016 at 10:57:15PM +0200, Andreas Cadhalpun wrote:
>> Otherwise another frame gets referenced into picture, triggering an assert
>> (from commit 13aae8) in av_frame_ref.
>>
>> Signed-off-by: Andreas Cadhalpun
On 21.10.2016 02:31, Michael Niedermayer wrote:
> On Thu, Oct 20, 2016 at 10:16:17PM +0200, Andreas Cadhalpun wrote:
>> This fixes asserts (from commit 13aae8) in av_frame_ref and
>> av_frame_move_ref.
>>
>> Signed-off-by: Andreas Cadhalpun
>> ---
>>
On 21.10.2016 01:37, Michael Niedermayer wrote:
> On Thu, Oct 20, 2016 at 08:19:00PM +0200, Andreas Cadhalpun wrote:
>> dcstr.c |8 +++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>> 365ebc3a050f6754a981340e0a8df5dbf781
>> 0001-dcstr-fix-division-by-zero.patch
>> From
>> I already post my mail to ffmpeg-users group regarding this issue but no
one could help me out and advised to ask more experienced users. So i hope
you can tell me something and sorry posting here.
Here is my re-encoding command's output (Windows 8.1 with Bash):
*$ ffmpeg -i perspective.mp4
On Fri, 21 Oct 2016 16:59:14 +0100
Derek Buitenhuis wrote:
> On 10/21/2016 4:32 PM, Derek Buitenhuis wrote:
> > * Audio packets. Especially audio packets with a large number of
> > samples.
> > It's extremely likely that edits will not fall on packet
On 10/21/2016 4:32 PM, Derek Buitenhuis wrote:
> * Audio packets. Especially audio packets with a large number of samples.
> It's extremely likely that edits will not fall on packet boundaries, and
> depending on the number of samples per packet, audio sync issues can and
>
> In YouTube we have long been receiving MOV files from users, which have
> non-trivial edit lists (Those edit lists which are not just used to offset
> video start from audio start) and multiple edit lists. Recently the uploads
> of such files has increased with the introduction of apps that
On Tue, Oct 18, 2016 at 12:14:56AM +1100, Xidorn Quan wrote:
> This isn't maintained by me. You should probaby ping Sebastien Zwickert <
> dilar...@free.fr>.
>
> But this change looks trivial, so I think it is fine.
applied
thx
[...]
--
Michael GnuPG fingerprint:
On 21/10/16 14:42, Michael Niedermayer wrote:
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Modern terrorism, a quick summary: Need oil, start war with country that
has oil, kill hundread thousand in war. Let country fall into chaos,
be surprised about raise of
On Fri, Oct 21, 2016 at 03:31:43PM +0200, Michael Niedermayer wrote:
> Fixes undefined behavior due to calling libc allocation with unclean FPU state
>
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/mpegvideo_enc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
>
Signed-off-by: Michael Niedermayer
---
libavutil/mem.c | 7 +++
libavutil/mem_internal.h | 2 ++
2 files changed, 9 insertions(+)
diff --git a/libavutil/mem.c b/libavutil/mem.c
index 1a8fc21..0771fa3 100644
--- a/libavutil/mem.c
+++ b/libavutil/mem.c
@@
Fixes undefined behavior from calling libc allocation with unclean FPU state.
Signed-off-by: Michael Niedermayer
---
libavcodec/snowenc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavcodec/snowenc.c b/libavcodec/snowenc.c
index 00aef57..5cc7997 100644
---
Signed-off-by: Michael Niedermayer
---
libavutil/avassert.h | 9 +
libavutil/utils.c| 13 +
2 files changed, 22 insertions(+)
diff --git a/libavutil/avassert.h b/libavutil/avassert.h
index f473637..46f3fea 100644
--- a/libavutil/avassert.h
+++
Signed-off-by: Michael Niedermayer
---
libavcodec/utils.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavcodec/utils.c b/libavcodec/utils.c
index 7da6a66..7c26485 100644
--- a/libavcodec/utils.c
+++ b/libavcodec/utils.c
@@ -1994,6 +1994,8 @@
Fixes undefined behavior due to calling libc allocation with unclean FPU state
Signed-off-by: Michael Niedermayer
---
libavcodec/mpegvideo_enc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavcodec/mpegvideo_enc.c b/libavcodec/mpegvideo_enc.c
index
The MMX state must be cleared between using MMX and using memory allocation
thats basically the only location between the 2
Signed-off-by: Michael Niedermayer
---
libavcodec/cavsdec.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavcodec/cavsdec.c
svq1_encode_plane() uses SIMD and we call libc memory allocation functions
after it
Signed-off-by: Michael Niedermayer
---
libavcodec/svq1enc.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/libavcodec/svq1enc.c b/libavcodec/svq1enc.c
index
LGTM
小山浩之 于2016年10月21日 周五上午4:47写道:
> ping
>
> > 2016/10/12 15:33、Hiroyuki OYAMA :
> >
> > Fix problem to fail by a RTMP Control Message except "Set Chunk Size
> (1)" after an RTMP handshake. When 'nginx-rtmp-module' relays an RTMP, it
> sends not only control
Hi,
On Thu, Oct 20, 2016 at 11:14 PM, James Zern wrote:
> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi
> wrote:
> > vp9_cx_iface actually allows values in range [0..2].
> > This fixes ticket #5894.
> >
> > Signed-off-by: Kagami Hiiragi
On 20.10.2016 09:36, Tobias Rapp wrote:
On 19.10.2016 23:06, Michael Niedermayer wrote:
On Wed, Oct 19, 2016 at 02:35:22PM +0200, Tobias Rapp wrote:
Signed-off-by: Tobias Rapp
---
tests/fate/mxf.mak| 19 ++-
tests/ref/fate/mxf-probe-d10 |
On 21/10/16 06:14, James Zern wrote:
> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi wrote:
>> vp9_cx_iface actually allows values in range [0..2].
>> This fixes ticket #5894.
>>
>> Signed-off-by: Kagami Hiiragi
>> ---
>> libavcodec/libvpxenc.c | 7
On 21.10.2016 00:55, Michael Niedermayer wrote:
On Wed, Oct 19, 2016 at 02:35:19PM +0200, Tobias Rapp wrote:
This patch series adds fate tests for probing MXF D10 (top field first) and
DV25 (bottom field first) file properties. Patch #2 is taken from
On Thu, Oct 20, 2016 at 11:51 AM, Rostislav Pehlivanov
wrote:
> On 20 October 2016 at 16:31, Kagami Hiiragi wrote:
>
>> vp9_cx_iface actually allows values in range [0..2].
>> This fixes ticket #5894.
>>
>> Signed-off-by: Kagami Hiiragi
53 matches
Mail list logo