2018-08-19 19:22 GMT+02:00, Vasiliy Volkov <[email protected]>: > While working on application based on libav* we've encountered strange > decoder behavior: it detects wrong input framerate when we specify more > than 1 thread to it. So it looks like a bug, but maybe we do something > wrong? > The problem with framerate detected by decoder: when we set 1 decoder > thread it detects framerate correctly, but when we set 2 or more it doubles > the framerate. > > Here is a minimal code with h264 sample bitstream for reproduce such > behavior: https://yadi.sk/d/SBC1mv_L3aNJKK
While H.264 timestamps (and therefore framerate) can be wrong with FFmpeg (this is a long-standing issue), I always get "50fps" for the given sample with current FFmpeg, no matter the number of threads, so I suspect the issue is in your code. Carl Eugen _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
