On 27-06-2018 06:33 AM, Marton Balint wrote:
Maybe we should disable the message for CFR only?
First question is, who is the message meant for? End-users can't do
anything with it. At most, a one-time message is fine, similar to the
"More than 1000 frames duplicated" message.
Regards,
G
On Wed, 27 Jun 2018, Michael Niedermayer wrote:
On Tue, Jun 26, 2018 at 05:13:36PM +0530, Gyan Doshi wrote:
On 26-06-2018 04:29 PM, Marton Balint wrote:
Many users have queried/complained about the 'Past duration too large'
messages.
If the message is useless, then why not remove it ent
On Tue, Jun 26, 2018 at 04:22:42AM +, Song, Ruiling wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> > Michael Niedermayer
> > Sent: Friday, June 22, 2018 2:32 AM
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-d
On Tue, Jun 26, 2018 at 05:13:36PM +0530, Gyan Doshi wrote:
>
>
> On 26-06-2018 04:29 PM, Marton Balint wrote:
>
> >>Many users have queried/complained about the 'Past duration too large'
> >>messages.
> >
> >If the message is useless, then why not remove it entirely?
>
> Good question. Don't s
2018-06-26 6:22 GMT+02:00, Song, Ruiling :
> Basically I think we have three ways to handle it:
> a.) ignore the warning.
This is the worst solution as it may hide other, useful warnings.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On 06/26/2018 11:36 PM, Lukas Rusak wrote:
This was found using valgrind. Using this patch there is no more memleak
present.
---
libavcodec/v4l2_m2m_dec.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libavcodec/v4l2_m2m_dec.c b/libavcodec/v4l2_m2m_dec.c
index 598dc1
This was found using valgrind. Using this patch there is no more memleak
present.
---
libavcodec/v4l2_m2m_dec.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libavcodec/v4l2_m2m_dec.c b/libavcodec/v4l2_m2m_dec.c
index 598dc10781..710e40efd8 100644
--- a/libavcodec/v4l2_m
2018-06-26 18:32 GMT+02:00, Jacob Trimble :
> Signed-off-by: Jacob Trimble
> ---
> libavutil/encryption_info.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavutil/encryption_info.h b/libavutil/encryption_info.h
> index 9140968fde..8fe7ebfe43 100644
> --- a/libavutil
2018-06-26 1:45 GMT+02:00, Michael Niedermayer :
> On Mon, Jun 25, 2018 at 11:22:31PM +0200, Carl Eugen Hoyos wrote:
>> 2018-06-23 14:43 GMT+02:00, Michael Niedermayer :
>> > On Thu, Jun 21, 2018 at 10:09:14PM +, Carl Eugen Hoyos wrote:
>> >> ffmpeg | branch: master | Carl Eugen Hoyos | Fri
>>
2018-06-26 17:42 GMT+02:00, Moritz Barsnick :
> @@ -425,8 +435,9 @@ static int xcbgrab_read_packet
> xcbgrab_draw_mouse(s, pkt, p, geo);
> #endif
>
> -free(p);
> -free(geo);
> +fail:
> +av_free(p);
> +av_free(geo);
I suspect this is incorrect, if it is correct, it should
Sample provided by Thierry for fate
Signed-off-by: Michael Niedermayer
---
tests/fate/demux.mak | 3 ++
tests/ref/fate/ts-small-demux | 80 +++
2 files changed, 83 insertions(+)
create mode 100644 tests/ref/fate/ts-small-demux
diff --git a/tests/fate/d
On Tue, Jun 26, 2018 at 07:02:38PM +0800, Baozeng Ding wrote:
> Signed-off-by: Baozeng Ding
> ---
> libavcodec/parser.c | 10 +++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
This looks wrong. The input must have AV_INPUT_BUFFER_PADDING_SIZE
allocated at the end.
Is the buffer you p
On Mon, Jun 25, 2018 at 5:30 PM Michael Niedermayer
wrote:
>
> On Fri, Jun 01, 2018 at 12:51:48PM -0700, Jacob Trimble wrote:
> > Signed-off-by: Jacob Trimble
> > ---
> > libavutil/Makefile| 1 +
> > libavutil/encryption_info.h | 2 +-
> > libavutil/tests/.gitignore
Signed-off-by: Jacob Trimble
---
libavutil/tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavutil/tests/.gitignore b/libavutil/tests/.gitignore
index 71f75a8ee9..bf07c57b75 100644
--- a/libavutil/tests/.gitignore
+++ b/libavutil/tests/.gitignore
@@ -24,6 +24,7 @@
/hmac
/
Signed-off-by: Jacob Trimble
---
libavutil/encryption_info.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavutil/encryption_info.h b/libavutil/encryption_info.h
index 9140968fde..8fe7ebfe43 100644
--- a/libavutil/encryption_info.h
+++ b/libavutil/encryption_info.h
@@ -12
xcb_query_pointer_reply() and xcb_get_geometry_reply() return NULL
when the display drops. This needs to be checked in order to cleanly
exit, because the returned pointers are dereferenced later.
Signed-off-by: Moritz Barsnick
---
libavdevice/xcbgrab.c | 19 +--
1 file changed, 1
On 26-06-2018 04:29 PM, Marton Balint wrote:
Many users have queried/complained about the 'Past duration too large'
messages.
If the message is useless, then why not remove it entirely?
Good question. Don't see the point but Michael added it (4e20e94921) so
may have some use for it that I
Hello everyone,
we use ffmpeg libraries to ingest our video streams using the RTMP protocol .
So far we use the librtmp backend instead of the built-in implementation since
we require Flash url Autentication parameters (needed for many CDN's ),
Until now, we were using ffmpeg 2.7.0 successfu
Signed-off-by: Baozeng Ding
---
libavcodec/parser.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/libavcodec/parser.c b/libavcodec/parser.c
index f43b197..a9786af 100644
--- a/libavcodec/parser.c
+++ b/libavcodec/parser.c
@@ -355,6 +355,7 @@ int ff_combine_frame(P
On Tue, 26 Jun 2018, Gyan Doshi wrote:
Many users have queried/complained about the 'Past duration too large'
messages.
If the message is useless, then why not remove it entirely?
Thanks,
Marton
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.or
Many users have queried/complained about the 'Past duration too large'
messages.
Regards,
Gyan
From 9e265308865455c4a61b0cb65840466b4d575670 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Tue, 26 Jun 2018 15:42:04 +0530
Subject: [PATCH] fftools/ffmpeg: add option to hide vsync warnings
When t
21 matches
Mail list logo
