+ Reply to Thread
Results 1 to 4 of 4
x264's optimal thread count for highest CPU usage is 1.5*logical threads, or 12 in your case. It should be calculate by default without setting threads manually
You might have other filter bottlenecks, like overlay . Post your avs script and encoding settings
If filtering is the bottleneck, I often encode a video in two halves simultaneously, then join them together when they're done. That way between them they keep the CPU working pretty hard. Just make sure to check "stitchable" in the x264 encoder configuration (under the Misc tab) so you won't have an issue appending the two output files together with MKVMergeGUI (assuming you're wanting MKV).
It's easy enough to do. I usually make note of a frame number somewhere near the middle which is at the end of a scene (so the second half is encoded from the first frame in a new scene), make a copy of the script, then add Trim() to each script so each one encodes half the video.
ie If the video had 100,000 frames, I'd add something like this to the end of the first script. Frame number 50258 would be the first frame of a new scene.
and this to the end of the second script (the copy):
Or you could add this to the end of the second script instead.
Trim(50258, 0) # Encodes from frame number 50258 to the last frame.
Then I add them both to the job queue and run them at the same time, finally appending the two output files together with MKVMergeGUI.
Last edited by hello_hello; 28th Jan 2014 at 17:52.
this is the script
FFVideoSource("E:\OSN\Wadi.Al.The2ab.S07.HDTV.1080 p.Arabox.org\Valley.Of.The.Wolves.S07.EP19.HDTV.10 80p.Arabox.org.mkv", threads=8)