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 condition to display the warning is faulty
It can be triggered by the following command form:
ffmpeg -f image2 -framerate X -i images -r Y -vsync vfr out
where 0.6*X < Y < X.
It always spams my console when I'm saving a live capture to MPEG-TS.
This patch is less about the logic and more about a cleaner stderr.
Are you planning to revisit the logic? If not, I'd like to push this.
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.
Regards,
Marton
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
