On 09/17/2014 04:27 PM, tim nicholson wrote: > On 17/09/14 11:05, Peter B. wrote: >> I've noticed that using ffprobe to analyze an FFV1/AVI file, it only >> utilizes a part of the available CPU power. >> For example, the following command: >> >> //---------------------------------------------- >> $ ffprobe_git -f lavfi -i >> "movie=qctools.avi,signalstats=stat=tout+vrep+brng,cropdetect=reset=1,split[a][b];[a]field=top[a1];[b]field=bottom[b1],[a1][b1]psnr" >> -show_frames -show_versions -of xml=x=1:q=1 -noprivate -threads auto >> -loglevel info > qctools.avi.qctools.xml >> //---------------------------------------------- > Try using a simpler ffprobe command and compare like with like. > > Your example includes a complex filter chain and not all filters > multi-thread afaik.
Thanks for the hint. I've now narrowed it down, and without the "signalstats" filter, it uses the whole CPU. So it seems that the "signalstats" filter is not multithreading. Is there a specific/technical reason for this, or could it be changed to be multithreading, too? Thanksalot! Pb _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
