On 12/13/2018 9:12 AM, James E. Baird wrote:
ffprobe version git-2017-01-22-f1214ad Copyright (c) 2007-2017 the FFmpeg developers
First thing- get a newer version (the latest, if possible) of ffmpeg and see how that behaves. Best would to build from the latest source, but at least something no more than a couple of months old. The official position of developers, and I am not one of them, is that only the latest revision in git is "supported" here. Anyway, try a newer version.
You might also try transcoding into a file (or null) and outputing from a file to see if one or the other parts is a CPU hog.
z! _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".