Quote:
Originally Posted by Stereodude
Your direct link gives a 404.
|
Works for me.
Quote:
Originally Posted by Stereodude
I also have a question about AviSynth+. I see a big push related to MT in the past week. I thought the whole idea was to get better performance without requiring the user to mess around with MT commands and the like?
|
Ultimately, that is what everybody (including us developers) would like to see. But unfortunately what you wish for is simply technically not possible for many filters due to the way they work. What we
can do though is to minimize the MT-related commands the user has to issue, instead of completely eliminating them. Minimizing the MT-commands for script writers is the collective goal of many of our efforts, such as many filter rewrites (both internal and external), adding support for filters to signal to Avs+ the MT mode they need, the way SetFilterMTMode() works, and even of
this post to teach plugin developers how to support MT hassle-free for the user.
So we do what we can, but sometimes there are hard limits to what is possible at all.