[Libav-user] Decoder detects wrong framerate

Vasiliy Volkov volk.vasiliy at gmail.com
Mon Aug 20 09:08:41 EEST 2018

Carl, have you seen my code? I use nothing except libav methods, so maybe
yes, there is something with my code, but could you be more specific?
Also FFmpeg tries to determine framerate based on container information,
while I need to detect it from bitstream. So it's different approaches.

пн, 20 авг. 2018 г. в 0:24, Carl Eugen Hoyos <ceffmpeg at gmail.com>:

> 2018-08-19 19:22 GMT+02:00, Vasiliy Volkov <volk.vasiliy at gmail.com>:
> > 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
> Libav-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/libav-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20180820/6b1b97db/attachment.html>

More information about the Libav-user mailing list