On 5/4/19, Michael Niedermayer wrote:
> Fixes: Assertion failure
> Fixes:
> 14484/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_PGMYUV_fuzzer-5150016408125440
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by: Michael Nied
The patch is for ticket #5154. https://trac.ffmpeg.org/ticket/5154
Suggest any changes required.
Shivam GoyalFrom 8416b130d461da117ca2d0b64e805c8e9cbe675c Mon Sep 17 00:00:00 2001
From: Shivam Goyal
Date: Sat, 4 May 2019 12:46:39 +0530
Subject: [PATCH] lavf/h264: Add support for raw h264 strea
The improved patch is for ticket #5154.
Support for Raw h264 stream from Arecont Camera.
Suggest any changes required.
Shivam GoyalFrom c9e03c2460630686c6942b2078c64f82143d76f8 Mon Sep 17 00:00:00 2001
From: Shivam Goyal
Date: Sat, 4 May 2019 14:04:36 +0530
Subject: [PATCH] lavf/h264: Add su
On Sat, May 4, 2019 at 10:52 AM Shivam Goyal wrote:
>
> The improved patch is for ticket #5154.
>
> Support for Raw h264 stream from Arecont Camera.
>
> Suggest any changes required.
>
The format-name based check in ff_raw_read_partial_packet is really
iffy. You can setup a specific read function
> >
> > @xwmeng, We now can support 3 padding options for conv layer.
> > - valid: the same definition as TF model. (the size of feature map
> > changed).
> > - same: the same definition as TF model. (zero filled for outside pixels).
> > - same_clamp_to_edge: just like 'same' option, but edge f
On 04-05-2019 15:15, Hendrik Leppkes wrote:
> On Sat, May 4, 2019 at 10:52 AM Shivam Goyal wrote:
>
>> The improved patch is for ticket #5154.
>>
>> Support for Raw h264 stream from Arecont Camera.
>>
>> Suggest any changes required.
>
> The format-name based check in ff_raw_read_partial_pac
Gyan (12019-05-02):
> The flow is
>
> avformat_write_header -> avformat_init_output -> init_muxer
>
> And in the last function, lines 293-385 (as of 7eba26451) carry out the
> checks, and which my patch skips.
I missed this. My bad.
> The problem is that there is no clean set of flags which iso
Στις Παρ, 3 Μαΐ 2019 στις 6:39 μ.μ., ο/η Michael Niedermayer
έγραψε:
>
> This allows handling more than 26.5h of mpeg* input
>
> Fixes: Ticket 7876
>
I confirm it fixes the case described in the ticket. Will now test it
in realtime environment, so it will take 26,5 hours to report back.
Thank you
Hi,
I open votes for 7 days. Voting is about inclusion of scaletempo
filter (IMHO it is better than atempo) in FFmpeg.
Thanks for voting.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscr
Fixes ticket #2956.
Signed-off-by: Swaraj Hota
---
Revised patch. Made some minor changes based on original player:
- Removed incorrect reading of frame_rate, instead frame rate
is kept fixed at 25 (seems like this value is always same).
- Added reading of frame width and height from input file.
Hi,
I open voting for 7 days, for inclusion of colorhold filter in FFmpeg,
with minor changes.
Thanks.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffm
Paul B Mahol (12019-05-04):
> I open votes for 7 days. Voting is about inclusion of scaletempo
> filter (IMHO it is better than atempo) in FFmpeg.
>
> Thanks for voting.
Voting for what? This mail does not look remotely like the voting
procedure. For starters, a vote must come after a discussion
Paul B Mahol (12019-05-04):
> I open voting for 7 days, for inclusion of colorhold filter in FFmpeg,
> with minor changes.
See:
https://ffmpeg.org/pipermail/ffmpeg-devel/2019-May/243478.html
--
Nicolas George
signature.asc
Description: PGP signature
__
On Sat, May 4, 2019 at 2:41 PM Nicolas George wrote:
> Paul B Mahol (12019-05-04):
> > I open votes for 7 days. Voting is about inclusion of scaletempo
> > filter (IMHO it is better than atempo) in FFmpeg.
> >
> > Thanks for voting.
>
> Voting for what? This mail does not look remotely like the v
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 18 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/vf_colorkey.c | 102 +-
4 files changed, 121 insertions(+), 1 deletion(-)
diff --git a/doc/filters.texi b
On 5/1/19, Moritz Barsnick wrote:
> ---
> doc/filters.texi | 8
> libavfilter/f_realtime.c | 7 +--
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index cd82869849..2f9333c3f3 100644
> --- a/doc/filters.texi
> +++ b/
On 5/4/19, John Warburton wrote:
> On Sat, May 4, 2019 at 2:41 PM Nicolas George wrote:
>
>> Paul B Mahol (12019-05-04):
>> > I open votes for 7 days. Voting is about inclusion of scaletempo
>> > filter (IMHO it is better than atempo) in FFmpeg.
>> >
>> > Thanks for voting.
>>
>> Voting for what?
On Sat, May 04, 2019 at 15:10:03 +0100, John Warburton wrote:
> Is there a patch I can use to test scaletempo to compare it against atempo?
You can see the patch and follow the discussion here. The patch is at
the bottom (also available in raw form as download):
https://patchwork.ffmpeg.org/patch/
Paul B Mahol (12019-05-04):
> There is old patch on this ML (but it probably no more applies cleanly), and
> no,
> this is not about removing/replacing filter, this is about adding new filter.
And as I said, this vote is invalid.
--
Nicolas George
signature.asc
Description: PGP signature
__
On 5/4/19, Paul B Mahol wrote:
> Hi,
>
> I open voting for 7 days, for inclusion of colorhold filter in FFmpeg,
> with minor changes.
>
> Thanks.
>
See: http://ffmpeg.org/pipermail/ffmpeg-devel/2019-May/243481.html
___
ffmpeg-devel mailing list
ffmpeg-d
On 5/4/19, Nicolas George wrote:
> Paul B Mahol (12019-05-04):
>> There is old patch on this ML (but it probably no more applies cleanly),
>> and no,
>> this is not about removing/replacing filter, this is about adding new
>> filter.
>
> And as I said, this vote is invalid.
Every vote is valid an
On 5/4/19, Swaraj Hota wrote:
> Fixes ticket #2956.
>
> Signed-off-by: Swaraj Hota
> ---
> Revised patch. Made some minor changes based on original player:
> - Removed incorrect reading of frame_rate, instead frame rate
> is kept fixed at 25 (seems like this value is always same).
> - Added readi
John Warburton (12019-05-04):
> An earlier post referring to scaletempo, from December 2017, suggested
> replacement of atempo. Please may I note that at least one commercial radio
> station, that I personally broadcast on daily, uses atempo for adjusting
> the timing of news bulletins so they exac
Paul B Mahol (12019-05-04):
> Every vote is valid and counts.
Are you sure you want to go in that direction?
In that case, I call for another vote, right now:
Please vote about the following motion:
Nicolas George shall have the authority to
kick any member of the FFmpeg proje
Nicolas George (12019-05-04):
> Please vote about the following motion:
>
> Nicolas George shall have the authority to
> kick any member of the FFmpeg project (commit rights and voting
> rights) for any reason and without discussion.
>
> Voting is open until 2019-05-04T14:40:00
On Sat, May 04, 2019 at 16:19:13 +0200, Paul B Mahol wrote:
> > +{ "speed", "speed factor", OFFSET(speed), AV_OPT_TYPE_DOUBLE, { .dbl =
> > 1.0 }, DBL_MIN, DBL_MAX, FLAGS },
>
> Why is this allowed to be negative?
In my reading (and intent), it's forbidden to be negative. Both min and
max are
On Fri, May 03, 2019 at 23:47:47 -0300, James Almer wrote:
> The flush() callback exists to reset the bsf into its initial state
> without the need to destroy and recreate the context.
> For example, some decoders auto-insert certain bitstream filters that
[...]
> avcodec_flush_buffers(), which mus
On Sat, May 4, 2019 at 3:34 PM Nicolas George wrote:
> John Warburton (12019-05-04):
>
> > Is there a patch I can use to test scaletempo to compare it against
> atempo?
> > It'll be no trouble to do that with the normal audio that is
> time-adjusted
> > on that radio station. It may be that its i
On 5/4/19, Moritz Barsnick wrote:
> On Sat, May 04, 2019 at 16:19:13 +0200, Paul B Mahol wrote:
>> > +{ "speed", "speed factor", OFFSET(speed), AV_OPT_TYPE_DOUBLE, {
>> > .dbl =
>> > 1.0 }, DBL_MIN, DBL_MAX, FLAGS },
>>
>> Why is this allowed to be negative?
>
> In my reading (and intent), it'
Okay. Thanks!
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
On Sat, May 04, 2019 at 10:08:38AM +0200, Paul B Mahol wrote:
> On 5/4/19, Michael Niedermayer wrote:
> > Fixes: Assertion failure
> > Fixes:
> > 14484/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_PGMYUV_fuzzer-5150016408125440
> >
> > Found-by: continuous fuzzing process
> > https://github.c
Signed-off-by: James Almer
---
libavcodec/Makefile | 4 +-
libavcodec/mlp_parse.c | 213 +++
libavcodec/{mlp_parser.h => mlp_parse.h} | 15 +-
libavcodec/mlp_parser.c | 193 +---
libavcodec/mlpdec.c
On Fri, May 03, 2019 at 09:08:57PM +0200, Lynne wrote:
> This commit adds a new API to libavutil to allow for arbitrary transformations
> on various types of data.
> This is a partly new implementation, with the power of two transforms taken
> from libavcodec/fft_template, the 5 and 15-point FFT ta
On Sat, May 04, 2019 at 11:30:38AM +1000, Peter Ross wrote:
> On Sat, May 04, 2019 at 01:38:38AM +0200, Michael Niedermayer wrote:
> > Fixes: Timeout (11sec -> 5sec)
> > Fixes:
> > 14473/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_JV_fuzzer-5761630857592832
> >
> > Found-by: continuous fuzz
On 5/4/2019 4:04 PM, James Almer wrote:
> Signed-off-by: James Almer
> ---
> libavcodec/Makefile | 4 +-
> libavcodec/mlp_parse.c | 213 +++
> libavcodec/{mlp_parser.h => mlp_parse.h} | 15 +-
> libavcodec/mlp_parser.c
Hi all!
On 2019-04-28 00:38 +, Guo, Yejun wrote:
> > From: avih [mailto:avih...@yahoo.com]
> > Sent: Wednesday, April 24, 2019 9:23 PM
> > To: FFmpeg development discussions and patches
> > Cc: Guo, Yejun
> > Subject: Re: [FFmpeg-devel] [PATCH V5 2/2] configure: replace 'pr' with
> > printf
Hi!
On 2019-05-04 06:28 +, avih wrote:
> > On 2019-05-02 08:55 +, avih wrote:
> > > > It seems awk is unconditionally required already. However I wanted to
> > > > say that it's a very nice dep to have
> > >
> > > While it's possibly nicer than other deps to have, it's still better to
> >
May 4, 2019, 8:10 PM by mich...@niedermayer.cc:
> On Fri, May 03, 2019 at 09:08:57PM +0200, Lynne wrote:
>
>> This commit adds a new API to libavutil to allow for arbitrary
>> transformations
>> on various types of data.
>>
> breaks build on mips
>
> CClibavutil/fft.o
> src/libavutil/fft.c:47
On 4/25/2019 7:04 PM, James Almer wrote:
> 10 bytes (id3v2 header amount of bytes) were being read before any checks
> were made on the bitstream. The result was that we were overreading into
> the next frame if the current one was 8 or 9 bytes long.
>
> Fixes tickets #7271 and #7869.
>
> Signed-
Fixes: signed integer overflow: -1877966852 + -469491713 cannot be represented
in type 'int'
Fixes:
14561/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_TRUEMOTION2_fuzzer-5167608359288832
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Sig
Am Sa., 4. Mai 2019 um 15:01 Uhr schrieb Shivam Goyal :
>
> On 04-05-2019 15:15, Hendrik Leppkes wrote:
>
> > On Sat, May 4, 2019 at 10:52 AM Shivam Goyal wrote:
> >
> >> The improved patch is for ticket #5154.
> >>
> >> Support for Raw h264 stream from Arecont Camera.
> >>
> >> Suggest any change
Am Sa., 27. Apr. 2019 um 13:12 Uhr schrieb Carl Eugen Hoyos
:
>
> 2019-04-25 0:45 GMT+02:00, Carl Eugen Hoyos :
>
> > Attached patch allows to run fate from wsl for out-of-tree builds.
>
> I will push this patch if there are no objections.
Patch applied.
Carl Eugen
___
Signed-off-by: James Almer
---
libavcodec/truehd_core_bsf.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/libavcodec/truehd_core_bsf.c b/libavcodec/truehd_core_bsf.c
index 409e570eec..9e3ee07eed 100644
--- a/libavcodec/truehd_core_bsf.c
+++ b/libavcodec/truehd_core_bsf.c
@@ -174,6 +1
On Sun, Apr 28, 2019 at 7:02 PM myp...@gmail.com wrote:
>
> On Sun, Apr 28, 2019 at 5:30 PM Gyan wrote:
> >
> >
> >
> > On 28-04-2019 07:19 AM, myp...@gmail.com wrote:
> > > On Sat, Apr 27, 2019 at 8:22 PM Gyan wrote:
> > >>
> > >>
> > >> On 27-04-2019 05:25 PM, Carl Eugen Hoyos wrote:
> > >>> 2
Am So., 5. Mai 2019 um 03:23 Uhr schrieb myp...@gmail.com :
>
> On Sun, Apr 28, 2019 at 7:02 PM myp...@gmail.com wrote:
> >
> > On Sun, Apr 28, 2019 at 5:30 PM Gyan wrote:
> > >
> > >
> > >
> > > On 28-04-2019 07:19 AM, myp...@gmail.com wrote:
> > > > On Sat, Apr 27, 2019 at 8:22 PM Gyan wrote:
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Alexander Strasser
> Sent: Sunday, May 05, 2019 3:42 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH V5 2/2] configure: replace 'pr' with printf
> si
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Alexander Strasser
> Sent: Thursday, May 02, 2019 12:08 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH 1/2] configure: print_in_columns: Replace pr
> with awk
>
> Get rid
Fix #6945
Exif extension has 'Orientaion' field for image flip and rotation.
This change is to add the first frame's exif into stream so that
autorotation would use the info to adjust the frames.
---
fftools/ffmpeg.c | 45 +
1 file changed, 45 insertions
Current implemantion for autoratation does not support flip.
That is, if the matrix contains flip info, the API get_rotation
only reflects partial information. This change is for adding
support for hflip (vflip can be achieved by rotation+hflip).
---
fftools/cmdutils.c| 4 ++--
fftools/cm
On Sun, May 5, 2019 at 9:31 AM Carl Eugen Hoyos wrote:
>
> Am So., 5. Mai 2019 um 03:23 Uhr schrieb myp...@gmail.com :
> >
> > On Sun, Apr 28, 2019 at 7:02 PM myp...@gmail.com wrote:
> > >
> > > On Sun, Apr 28, 2019 at 5:30 PM Gyan wrote:
> > > >
> > > >
> > > >
> > > > On 28-04-2019 07:19 AM, m
On Mon, Apr 29, 2019 at 4:02 AM Marton Balint wrote:
>
> Hi All,
>
> There has been discussion on the mailing list several times about the
> inclusion of support for closed source components (codecs, formats,
> filters, etc) in the main ffmpeg codebase.
>
> Also the removal of libNDI happened with
On 5/4/2019 12:06 PM, Moritz Barsnick wrote:
> On Fri, May 03, 2019 at 23:47:47 -0300, James Almer wrote:
>> The flush() callback exists to reset the bsf into its initial state
>> without the need to destroy and recreate the context.
>> For example, some decoders auto-insert certain bitstream filte
Will apply.
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
_
53 matches
Mail list logo
