On Wed, Mar 27, 2019 at 02:11:59PM -0700, Thierry Foucu wrote: > Right now, the code check for no filter description, but if we use a > filter_complex, the code will use the AVFrame.duration which could be > wrong in case of using fps filter. > > How to reproduce the problem: > ffmpeg -f lavfi -i testsrc=duration=1 -vf fps=fps=50 -vsync 1 -f null - > output 50 frames > > ffmpeg -f lavfi -i testsrc=duration=1 -filter_complex fps=fps=50 -vsync 1 -f > null - > output 51 frames > > With the patch, the same command will always output 50 frames. > > --- > fftools/ffmpeg.c | 1 + > 1 file changed, 1 insertion(+)
will apply thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Whats the most studid thing your enemy could do ? Blow himself up Whats the most studid thing you could do ? Give up your rights and freedom because your enemy blew himself up.
signature.asc
Description: PGP signature
_______________________________________________ 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".
