Quote:
Originally Posted by Sagekilla
You do know you can do a huge chunk of code with triple quotes for MT, right?  |
Yes, I saw that opportunity. I can only use that if I need the same amount of frame overlapping for every filter. Which is not the case.
I'm still thinking that MT does not do anything. It calls SetMTMode(5) which is the slowest solution, even slower than not using MT. What sense does this make?
Here are some encoding times for the above script:
VirutalDubMod/Xvid using no MT at all: 18 hours
VirutalDubMod/Xvid using MT() only (= above script): 18 hours
VirutalDubMod/Xvid using SetMTMode(2) only: 16 hours
Can you verify my following thoughts?
AviSynth multithreading has basically nothing to do with multithreading XviD or x264.
You can do one of the following 4:
1.) NO Avisynth MT + NO XviD MT (standard encoding)
2.) Avisynth MT + NO XviD MT
3.) NO Avisynth MT + XviD MT
4.) Avisynth MT + XviD MT
NO Avisynth MT + XviD MT is basically the same as using Avisynth MT + NO XviD MT with SetMTMode() in AviSynth, because they both result in temporal multithreading.
AviSynth MT + XviD MT is quite nonsense, because it uses multiple threads for creating XviD frames whereas every XviD thread in addition is split up into another threads at the level of AviSynth.