-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong duration of AVC elementary stream after recent changes #2040
Comments
Here is an example file - named .mp4 to be able to attach to issue ;-) bunny_30fps.h264.mp4generated with
Not sure if the file can be downloaded. If not please give me a hint how to send the sources in proper way. |
It can be downloaded, right click, save video.
Well, ffplay cannot recognise any fps in this video and just says 25 fps. Now, this is a mistake, as it appears it has 60 fps data. [trace_headers @ 000002185997d200] 70 vui_parameters_present_flag 1 = 1 |
Quick test with FFmpeg 4.4.2 and 30 fps are detected: Issue is in MI, no discussion about that. |
MediaInfo v24.01 reports different Duration and Frame Rate of the AVC (H.264) elementary stream then v22.09. I only noticed it when I use the source which was sliced from the origin video (but not sure if it needed). Here is how I prepared the source:
ffmpeg -y -ss 00:00:05.0 -i big_buck_bunny.mov -t 00:00:10.0 -c:v libx264 -an -vf "fps=30,scale=640:480" -f h264 bunny.h264
So it cut from 5 second to 15 second of source, changes fps to 30 + downsizes image (just for reducing size of the file) and outputs as H.264 elementary stream.
I would expect the duration of such stream to be close to 10 seconds + fps reported as 30.
I noticed different behaviour of MediaInfoLib after commit 5271548
Before that commit I got Duration 10 s 0 ms and FPS 30.000 FPS
But after this commit I get Duration 6 s 933 ms and FPS 43.271 FPS
I also noticed that the difference in Duration is highly related with the fps which I use to encode the stream.
The text was updated successfully, but these errors were encountered: