On 28-06-2018 02:13 PM, Gyan Doshi wrote:
Alt patch attached. Plan to push tonight.
Pushed in 07987404a8b7346e1904501b88320c9bab353298.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Alt patch attached. Plan to push tonight.
From 07987404a8b7346e1904501b88320c9bab353298 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Thu, 28 Jun 2018 14:05:31 +0530
Subject: [PATCH] ffmpeg: make loglevel verbose for frame duration warning
---
fftools/ffmpeg.c | 2 +-
1 file changed, 1 insert
On 27-06-2018 11:30 PM, Marton Balint wrote:
If we don't know why it spams the console or nobody is willing to fix it,
then decrease loglevel to verbose.
Will do this instead.
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
On Wed, Jun 27, 2018, at 10:00 AM, Marton Balint wrote:
>
> If we don't know why it spams the console or nobody is willing to fix it,
> then decrease loglevel to verbose. I am strongly against adding a command
> line option for this.
I was just about to give the same suggestion.
__
On Wed, 27 Jun 2018, Gyan Doshi wrote:
On 27-06-2018 05:13 PM, Michael Niedermayer wrote:
It was intended IIRC to detect cases where the code misbeahves or where the
input/demuxer/parser is badly broken as in:
timestamps: 1 2 4 5 7 9
durations: 9 8 1 -3 7 99
Maybe the conditio
On 27-06-2018 05:13 PM, Michael Niedermayer wrote:
It was intended IIRC to detect cases where the code misbeahves or where the
input/demuxer/parser is badly broken as in:
timestamps: 1 2 4 5 7 9
durations: 9 8 1 -3 7 99
Maybe the condition to display the warning is faulty
It can
On Wed, Jun 27, 2018 at 03:03:02AM +0200, Marton Balint wrote:
>
>
> 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
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 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
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
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
13 matches
Mail list logo
