On 09/01/2014 12:39 PM, SF wrote: > Is someone here have ideas about what is going on ? Why the bufsize + maxrate > option can create so much CPU load, > even with still pictures ? And why this does not occur with the same FFMPEG > command-line ? >
Did you try to do some profiling and identify the code parts which are taking so much additional time? Something like: valgrind --tool=callgrind --callgrind-out-file=/tmp/prof yourprogram kcachegrind /tmp/prof or whatever tool you prefer. -- Roberto Ragusa mail at robertoragusa.it _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
