View Full Version : Can't get DAA/Masktoolsv2 to work
Akai-Shuichi
1st March 2012, 15:36
Everytime i try to call on daa()
I get the error that mt_average does not exist.
I've imported the daa.avsi script and I've also loaded the mt_masktools.dll plugin. What else could I be doing wrong?
Abyssal
1st March 2012, 15:39
You need NNEDI2, MaskTools2 and Removegrain to get it to work. Are you sure you have all three? Keep in mind that some of these might also need some dependencies as well. For me it was just to get NNEDI2 since I already had the other two and DAA worked for me so I don't think they themselves need anything else but who knows, they might do and that I already had them unknowingly since before so I guess you need to read up a bit about them.
Akai-Shuichi
1st March 2012, 15:41
I have NNEDI2 called on as well and I have the DLL's for RemoveGrain, do I have to import them to get it to work?
Abyssal
1st March 2012, 15:44
I have NNEDI2 called on as well and I have the DLL's for RemoveGrain, do I have to import them to get it to work?
Yes, I think so. I'm pretty new to AviSynth myself so I'm not 100% sure but you can always try.
Also, do you have two seperate plugins folder? Like if you are using MeGUI or whatever and have plugins in there? ...in addition to the plugins folder in AviSynth program folder?
Akai-Shuichi
1st March 2012, 15:49
Hmm... Still isn't working for me. Would you mind posting me a script where you use it?
Abyssal
1st March 2012, 15:56
Hmm... Still isn't working for me. Would you mind posting me a script where you use it?
Yeah, sure, but please answer me if you have another plugin folder in addition to the one in the AviSynth program folder? i.e. if you are using MeGUI or whatever and have a plugin folder there too? :)
Akai-Shuichi
1st March 2012, 15:58
Yea, I have a meGUI plugin folder as well as an AviSynth program folder. I've been using the AviSynth program one.
Abyssal
1st March 2012, 16:02
Yea, I have a meGUI plugin folder as well as an AviSynth program folder. I've been using the AviSynth program one.
This might sound stupid as hell but have you tried putting your plugins in both folders? (Even if you are importing from the AviSynth program folder. I have had an issue myself which this solved. :P
Akai-Shuichi
1st March 2012, 16:03
Nope, didn't work. :(
Abyssal
1st March 2012, 16:26
This was the only script I found where I used daa()
http://pastebin.com/c04ykxid
Do note that this was mainly for testing out random filters so I imported a heck load of plugins and filters.
Akai-Shuichi
1st March 2012, 16:30
Yea, I don't understand what could be causing the problem :s
Didée
1st March 2012, 17:23
I remember that such symptoms have been reported when using mt_masktools-26.dll together with Avisynth 2.5.x.
Once again, just to be sure, the correct usage scheme is
Avisynth 2.5.x ---> mt_masktools-25.dll
Avisynth 2.6 ----> mt_masktools-26.dll
mandarinka
1st March 2012, 18:36
This was the only script I found where I used daa()
http://pastebin.com/c04ykxid
Do note that this was mainly for testing out random filters so I imported a heck load of plugins and filters.
Pardon me, but putting three daa() calls in series, I suspect that can end up very badly. Daa is quite aggressive, it can garble together fine detail (parallel horizontal lines close to each other will suffer) by itself, and it is contrasharpening too, so with repeated runs, you will get halos or other oversharpening - that is at least the case if you use nnedi3 inside daa (nnedi2 might be less sharp, so not that affected). However, nnedi2 is less safe when it comes to destruction of small detail, iirc. I suspect that the only thing saving you from problems is that your source is blurry (and you make it more blurry with the fft3dfilter).
I always used daa with supersampling, which is likely conceptually wrong but if you want anti-aliasing without destruction of detail, you have no choice:
spline36resize(width,height*3/2).daa3.spline36resize(width,height) or more weakened: spline36resize(width,height*2).daa3.spline36resize(width,height)
P.S.:
Doesn't running FFT3dfilter AFTER gradfun completely destroy the debanding?
Abyssal
1st March 2012, 21:31
Pardon me, but putting three daa() calls in series, I suspect that can end up very badly. Daa is quite aggressive, it can garble together fine detail (parallel horizontal lines close to each other will suffer) by itself, and it is contrasharpening too, so with repeated runs, you will get halos or other oversharpening - that is at least the case if you use nnedi3 inside daa (nnedi2 might be less sharp, so not that affected). However, nnedi2 is less safe when it comes to destruction of small detail, iirc. I suspect that the only thing saving you from problems is that your source is blurry (and you make it more blurry with the fft3dfilter).
I always used daa with supersampling, which is likely conceptually wrong but if you want anti-aliasing without destruction of detail, you have no choice:
spline36resize(width,height*3/2).daa3.spline36resize(width,height) or more weakened: spline36resize(width,height*2).daa3.spline36resize(width,height)
P.S.:
Doesn't running FFT3dfilter AFTER gradfun completely destroy the debanding?
Dude, thanks for reading.:rolleyes:
...and besides, that script has nothing to do with the OP.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.