Hi, I second TheRyuu demand for posting your script. I made some (promising) MT tests on a slow 2 cores but would like to test your script or an evolution of your script (apple to oranges once again) ;) Thanks. Did

Also, don't forget the efforts for four h.264 lossless decompression and four h.264 lossless compression. If you are just doing some intermediate processing tasks, I believe space is not much a concern and you may consider other less CPU-intensive compression such as huffyv12. The kernel is spending considerable effort in the USB connection too. Opt for an e-SATA harddisk if external enclosure is a must (still worse than internal ones though, coz the e-SATA chipset such as JMicron can't really compete with the ICHx controllers) And, as Ryuu and I mentioned, don't run overload your Windows box with busy threads. The Windows kernel is not particularly efficient managing multiple multi-thread CPU-intensive programs. From my own experience on Q6600, 4 single-threaded encodes run faster than 4 quadruple-threaded encodes.

Hi, @chengbin, thanks for the script. @theRyuu, thanks for testing I could have been stuck with the mt=true thingie - Gear is listed in my sig, with 2*1Gb Ram; - Source is a Mpeg2 capture movie, 4500Kbp/s; - Outputs are: 1/ Xvid 1.22 vfw/Vdub 1 pass, Quant 2.67 (usual) 2/ x264 r1145 vfw/Vdub 1 pass lossless (not usual) - Script is related to the original except: setmemorymax(512) # 1st line autocrop() #720*400 Setmtmode(1,0) # eventually MT("""sharpaamcmod(...)""",2,8) # same as TheRyuu, eventually or sharpaamcmod(...) without MT() MT("SelectRangeEvery(300,10)") # gives 4940 frames - Results, from slower to quicker, estimation from 3' encode each time: 1/Setmtmode() xvid. 23'07" gives 3.56fps x264 23' 2/ no MT or Setmt, just plain calls xvid. 22'55" gives 3.59fps x264 22'52" 3/ MT() alone without ,2,8) in the end not working ! 4/ MT(...,2,8) xvid. 13'42" gives 6fps x264 15'38" gives 5.26fps ... and for comparison purposes MT("Maa()") xvid. 3'40" gives 22.45fps x264 4'45" Without same source, script and parameters, speed may vary but it gives some clues. Did

Thank you for your testings. Some questions: Is directshowsource still frame inaccurate when it loads ffmpeg-mt to decode the video? So encoding a 1920x1080 video with this script, running single thread, at 0.06fps, doesn't that sound a bit too slow to your results?