Quote:
Originally Posted by Stereodude
I thought the whole idea was to get better performance without requiring the user to mess around with MT commands and the like?
|
That's right. When MT is finalized, the only thing the user will have to write in his script is the Prefetch call, which later can probably be added by programs like avsmeter, avs2yuv and the likes. All SetFilterMtMode calls will be hidden in a single .avsi script.
Compared to all those ### MT_Pipeline requires you to write, this is nothing.
Now, the problem is to build this avsi file with MT modes definitions. I put
this pad about two weeks ago and posted the link on our IRC channel, ultim also linked it here a few days ago. But since the initial script,
only one line has been added (fft3dgpu). With this kind of activity you can't expect MT to get finalized and become user-side overhead free any time soon.