This patch is only for solving the bug introduced by chunksize has been
initial set as UINT64 MAX.
2017-05-27 19:24 GMT+08:00 Ronald S. Bultje :
> Hi,
>
> On Fri, May 26, 2017 at 10:36 PM, raymond zheng <
> raymondzheng1...@gmail.com> wrote:
>
>> Hi:
>> I find an issue about http. I don't us
On 5/31/2017 12:04 AM, James Almer wrote:
> On 5/23/2017 7:07 PM, James Almer wrote:
>> It's an AVColorSpace value since 82ad9cbd32c873bced9adf4a2bb67dcda7294c61.
>>
>> Signed-off-by: James Almer
>> ---
>> libavutil/pixfmt.h | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/libavutil/p
On 5/31/17, Matthias Troffaes wrote:
> Dear Paul,
>
> On Wed, May 31, 2017 at 7:59 PM, Paul B Mahol wrote:
>> This code does not belong in this filter.
>>
>> Make new filter instead.
>
> May I kindly ask why you think so? I considered this as well but then
> decided against it, as this new filter
On Wed, 31 May 2017 20:59:07 +0200
Paul B Mahol wrote:
> On 5/31/17, Matthias Troffaes wrote:
> > Dear Moritz,
> >
> > On Wed, May 31, 2017 at 2:17 PM, Moritz Barsnick wrote:
> >> On Wed, May 31, 2017 at 13:31:14 +0100, Matthias C. M. Troffaes wrote:
> >>> @@ -2,6 +2,7 @@ Entries are sorted
Dear Paul,
On Wed, May 31, 2017 at 7:59 PM, Paul B Mahol wrote:
> This code does not belong in this filter.
>
> Make new filter instead.
May I kindly ask why you think so? I considered this as well but then
decided against it, as this new filter would behave like framestep as
a common special ca
On 5/31/17, Matthias Troffaes wrote:
> Dear Moritz,
>
> On Wed, May 31, 2017 at 2:17 PM, Moritz Barsnick wrote:
>> On Wed, May 31, 2017 at 13:31:14 +0100, Matthias C. M. Troffaes wrote:
>>> @@ -2,6 +2,7 @@ Entries are sorted chronologically from oldest to
>>> youngest within each release,
>>> re
Dear Moritz,
On Wed, May 31, 2017 at 2:17 PM, Moritz Barsnick wrote:
> On Wed, May 31, 2017 at 13:31:14 +0100, Matthias C. M. Troffaes wrote:
>> @@ -2,6 +2,7 @@ Entries are sorted chronologically from oldest to youngest
>> within each release,
>> releases are sorted from youngest to oldest.
>>
On Wed, May 31, 2017 at 05:18:57PM +0200, Tobias Rapp wrote:
> On 31.05.2017 15:42, wm4 wrote:
> >On Wed, 31 May 2017 14:49:19 +0200
> >Michael Niedermayer wrote:
> >
> >> [...]
> >>
> >>Security fixes should be as simple as
> >> possible.
> >
> >Well, your fix isn't simple. It adds yet another
Fixes detection of some TV sample as 24.5 FPS. With the patch applied,
it's detected as 25 FPS.
This is enabled for mpegts only.
---
libavformat/internal.h | 5 +
libavformat/mpegts.c | 2 ++
libavformat/utils.c| 10 ++
3 files changed, 17 insertions(+)
diff --git a/libavform
On Wed, May 31, 2017 at 03:42:41PM +0200, wm4 wrote:
> On Wed, 31 May 2017 14:49:19 +0200
> Michael Niedermayer wrote:
>
> > On Wed, May 31, 2017 at 01:13:50PM +0200, wm4 wrote:
> > > On Wed, 31 May 2017 12:51:35 +0200
> > > Michael Niedermayer wrote:
> > >
> > > > On Wed, May 31, 2017 at 11:
---
ffprobe.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/ffprobe.c b/ffprobe.c
index f2a3cc7a73..f6d0264334 100644
--- a/ffprobe.c
+++ b/ffprobe.c
@@ -35,6 +35,7 @@
#include "libavutil/bprint.h"
#include "libavutil/display.h"
#include "libavutil
---
ffprobe.c | 8
1 file changed, 8 insertions(+)
diff --git a/ffprobe.c b/ffprobe.c
index f6d0264334..b3464aac8f 100644
--- a/ffprobe.c
+++ b/ffprobe.c
@@ -1913,6 +1913,10 @@ static void print_pkt_side_data(WriterContext *w,
print_q("min_luminance", metadata->min_lumin
On 31.05.2017 15:42, wm4 wrote:
On Wed, 31 May 2017 14:49:19 +0200
Michael Niedermayer wrote:
>> [...]
>>
Security fixes should be as simple as
possible.
Well, your fix isn't simple. It adds yet another exception with
questionable effect. It makes it more complex and harder to predict
wh
On Wed, 31 May 2017 14:49:19 +0200
Michael Niedermayer wrote:
> On Wed, May 31, 2017 at 01:13:50PM +0200, wm4 wrote:
> > On Wed, 31 May 2017 12:51:35 +0200
> > Michael Niedermayer wrote:
> >
> > > On Wed, May 31, 2017 at 11:52:06AM +0200, wm4 wrote:
> > > > On Wed, 31 May 2017 11:29:56 +020
On Wed, May 31, 2017 at 13:31:14 +0100, Matthias C. M. Troffaes wrote:
> @@ -2,6 +2,7 @@ Entries are sorted chronologically from oldest to youngest
> within each release,
> releases are sorted from youngest to oldest.
>
> version :
> +- framestep filter: add blend parameter for motion blur eff
On Wed, May 31, 2017 at 01:13:50PM +0200, wm4 wrote:
> On Wed, 31 May 2017 12:51:35 +0200
> Michael Niedermayer wrote:
>
> > On Wed, May 31, 2017 at 11:52:06AM +0200, wm4 wrote:
> > > On Wed, 31 May 2017 11:29:56 +0200
> > > Michael Niedermayer wrote:
> > >
> > > > On Wed, May 31, 2017 at 09:
Note that this is a resubmission of
https://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209794.html - in
particular the mips test failure reported in
https://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209820.html has
been fixed.
Kind regards,
Matthias
On Wed, May 31, 2017 at 1:31 PM, Matthias
This patch adds a "blend" parameter to the framestep filter, to blend
frames together at each step, for a motion blur effect. The number of
frames that are blended (i.e. the exposure time, in frames) can be
controlled, allowing control over the strength of the motion blur. The
filter has timeline s
Hello,
Could you please provide us with some feedback on this patch?
Thanks,
Saverio
-Original Message-
From: Saverio Blasi [mailto:saverio.bl...@bbc.co.uk]
Sent: 09 May 2017 11:08
To: ffmpeg-devel@ffmpeg.org
Cc: Saverio Blasi
Subject: [PATCH v10] - Added Turing codec interface for ffm
On Wed, 31 May 2017 12:51:35 +0200
Michael Niedermayer wrote:
> On Wed, May 31, 2017 at 11:52:06AM +0200, wm4 wrote:
> > On Wed, 31 May 2017 11:29:56 +0200
> > Michael Niedermayer wrote:
> >
> > > On Wed, May 31, 2017 at 09:03:34AM +0200, Hendrik Leppkes wrote:
> > > > On Wed, May 31, 2017
On Wed, May 31, 2017 at 11:52:06AM +0200, wm4 wrote:
> On Wed, 31 May 2017 11:29:56 +0200
> Michael Niedermayer wrote:
>
> > On Wed, May 31, 2017 at 09:03:34AM +0200, Hendrik Leppkes wrote:
> > > On Wed, May 31, 2017 at 2:09 AM, Michael Niedermayer
> > > wrote:
> > > > On Wed, May 31, 2017 at
On Wed, 24 May 2017 15:47:36 +0200
wm4 wrote:
> With the new decode API, you can't handle errors directly in the API
> user - you only know that the hwaccel did not initialize at all.
>
> Add some approximate logging.
> ---
> libavcodec/videotoolbox.c | 6 ++
> 1 file changed, 6 insertions(
On Wed, 31 May 2017 11:29:56 +0200
Michael Niedermayer wrote:
> On Wed, May 31, 2017 at 09:03:34AM +0200, Hendrik Leppkes wrote:
> > On Wed, May 31, 2017 at 2:09 AM, Michael Niedermayer
> > wrote:
> > > On Wed, May 31, 2017 at 01:14:58AM +0200, Hendrik Leppkes wrote:
> > >> On Wed, May 31, 2
On Wed, May 31, 2017 at 09:03:34AM +0200, Hendrik Leppkes wrote:
> On Wed, May 31, 2017 at 2:09 AM, Michael Niedermayer
> wrote:
> > On Wed, May 31, 2017 at 01:14:58AM +0200, Hendrik Leppkes wrote:
> >> On Wed, May 31, 2017 at 12:52 AM, Michael Niedermayer
> >> wrote:
> >> > This prevents an expl
On Wed, May 31, 2017 at 2:09 AM, Michael Niedermayer
wrote:
> On Wed, May 31, 2017 at 01:14:58AM +0200, Hendrik Leppkes wrote:
>> On Wed, May 31, 2017 at 12:52 AM, Michael Niedermayer
>> wrote:
>> > This prevents an exploit leading to an information leak
>> >
>> > The existing exploit depends on
25 matches
Mail list logo