Carl Eugen Hoyos <[email protected]> added the comment:
The original issue was that FFmpeg simply did not output the frame-rate (but the timebase). Frame-rate is now shown, and is correct for cricket4.3gp, the file from the OP is 404 now. ---------- status: open -> closed substatus: open -> fixed ___________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/roundup/ffmpeg/issue56> ___________________________________________________
