Failed to open codec in av_find_stream_info Format image2 detected only with low score of 5, misdetection possible! For example using the native H.Invalid buffer size, packet size 417540 < expected frame_size 720000Įrror while decoding stream #0:0: Invalid argumentĪlso, the video processed till here is just static. To verify the desired decoder is being used I added the outputs from time in the example (the last three lines) for comparison purposes.

If you want real time as well add the time command before the ffmpeg command (if you're on Linux). Note the benchmark option outputs user CPU time, not the elapsed real time.

Libopenh264 $ ffmpeg -benchmark -c:v libopenh264 -i input.mp4 -map 0:v:0 -f null. Native FFmpeg H.264 decoder $ ffmpeg -benchmark -i input.mp4 -map 0:v:0 -f null. The -map option is also used so only the (first) video stream is decoded and to ignore other, non-video streams such as audio. Below are two decoding benchmark examples using the null muxer. To choose the decoder you want use the -c:v input option. It appears you're working with the FFmpeg libraries, but here are some examples using ffmpeg.

FFmpeg H.264 decoder is LGPL 2.1 or later. OpenH264 is licensed BSD 2-Clause 'Simplified' License. So the FFmpeg H.264 decoder is much faster than OpenH264. The native FFmpeg H.264 decoder has threading capabilities (frame and slice) but OpenH264 does not. The actual capabilities appear to be undocumented, so it is unclear if it has partial or full support for Main and High profiles. However it was able to decode a Main and a High profile video I tested. The documentation states that OpenH264 supports decoding of Constrained Baseline profile, so its usefulness may be limited. There are also several supported hardware assisted H.264 decoders, but I'm not going to go into detail about those. FFmpeg can use OpenH264 (named libopenh264 in FFmpeg) to decode in addition to the native FFmpeg H.264 decoder (named h264).

Ffmpeg encode yuv to h264