FFmpeg reporting different frame counts for the same piece of media

[jrobble]

Three different jobs for different pipelines for the same piece of media produced these errors:

"OpenCV reported the frame count to be 2908, but FFmpeg reported it to be 519. 519 will be used."

"OpenCV reported the frame count to be 2908, but FFmpeg reported it to be 202. 202 will be used."

"OpenCV reported the frame count to be 2908, but FFmpeg reported it to be 123. 123 will be used."

This is the FFmpeg command we're using via Tika:

ffmpeg -i ${INPUT} -map 0:v:0 -c copy -f null -

This results in output that is periodically updated as the video stream is copied. Tika uses the frame=\s*(\d+) regex on the output. Since there is a frame= match on each update we can't guarantee that the value is pulled from the final update. This may result in different values each time the media is inspected.

The solution is to use -nostats in the FFmpeg command.

Land to 6.0.