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 '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'm missing. > >> > >>Thoughts, Michael? > > > >I think, the condition shouldnt happen really > > Why not? For CFR output frames are dropped if delta0 < -1.1, but an error is > reported if delta0 < -0.6. So delta0 can remain indefinitely between -1.1 > and -0.6 spamming the console endlessly. > > Or am I missing something?
well if you have input like timestamps: 1 2 4 5 7 9 durations: 1 2 1 2 1 1 then the warning should never trigger no matter what frame rate convertion is used 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 [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Take away the freedom of one citizen and you will be jailed, take away the freedom of all citizens and you will be congratulated by your peers in Parliament.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
