Quote:
Originally Posted by MysteryX
Another question to throw into the mix. MP_Pipeline is one of these plugins that is designed to do something that Avisynth isn't supposed to do: running Avisynth in several processes and/or several threads.
Although the concept seems simple, in truth, it runs into all the same challenges as MT modes, but doesn't have the same level of sophistication. How does it handle these challenges, and what is it doing, really?
The other option would be to complete VapourSynth to have all the benefits and features of Avisynth; one of which is audio support.
|
MP_Pipeline's idea is really simple. Create several Avisynth instances in separate processes. Put a pre-fetcher to make it "multi-threaded" and the needed things to pass frames between these processes. And when you start wrapping Avisynth instances in multiple processes, who's really the plugin then?
If you look at the limitations the answer is that it doesn't get around anything that's relevant anymore. Avs+ has an x64 version and multi-threading. The only thing that might work better is ScriptClip and friends if you're very careful.
Note that I'm not a MP_Pipeline user.