Function not here?
- mirkosp
- The Absolute Mudman
- Joined: Mon Apr 24, 2006 6:24 am
- Status: (」・ワ・)」(⊃・ワ・)⊃
- Location: Gallarate (VA), Italy
- Contact:
Re: Function not here?
Mmmh... could you provide screenshot of the folder with its content? This really feels weird.
- Eake4
- Australian Zeus
- Joined: Tue Jul 26, 2011 6:15 am
- Status: Doing something useless again
- Location: Sydney, Australia
- mirkosp
- The Absolute Mudman
- Joined: Mon Apr 24, 2006 6:24 am
- Status: (」・ワ・)」(⊃・ワ・)⊃
- Location: Gallarate (VA), Italy
- Contact:
Re: Function not here?
That folder is looking quite empty, there should be MANY more things, I actually don't get how dfttest can work either to be honest...
http://www.animemusicvideos.org/guides/ ... inPack.zip
Grab that zip and unpack its content directly in the plugins folder (should be a bunch of .dll and .avsi files). That should do...
http://www.animemusicvideos.org/guides/ ... inPack.zip
Grab that zip and unpack its content directly in the plugins folder (should be a bunch of .dll and .avsi files). That should do...
- Eake4
- Australian Zeus
- Joined: Tue Jul 26, 2011 6:15 am
- Status: Doing something useless again
- Location: Sydney, Australia
- EvaFan
- Joined: Sun Mar 21, 2004 10:25 pm
- Status: (*゚▽゚)o旦~ ー乾杯ー♪
- Location: Somerset, KY
Re: Function not here?
I remember a friend having the a-m-v.org app installed and avisynth installed seperately creating two different install locations for it. It only loaded plugins from one of them though and we spent an hour trying to figure it out till I asked about it. You might want to make sure you didn't install it twice. If you have a plugin loading and working that isnt in your plugins folder than that would lead me to believe you have another plugins folder being loaded from another install directory or your autoloading directory location is somewhere your unaware of. I'd tell you how you can check but someone would probably be in shortly to raise hell about even checking the registry yet alone changing it.
"The people cannot be [...] always, well informed. The part which is wrong will be discontented, in proportion to [...] the facts they misconceive. If they remain quiet under such misconceptions, it is lethargy, the forerunner of death to public liberty. What country can preserve its liberties, if it's rulers are not warned [...] that this people preserve the spirit of resistance? The tree of liberty must be refreshed from time to time, with the blood of patriots and tyrants."-Thomas Jefferson
- mirkosp
- The Absolute Mudman
- Joined: Mon Apr 24, 2006 6:24 am
- Status: (」・ワ・)」(⊃・ワ・)⊃
- Location: Gallarate (VA), Italy
- Contact:
Re: Function not here?
No, checking the registry is actually a good idea to make sure the autoload directory is correct. I think I had suggested it in the past myself. I doubt Hatt would be against it in all honesty.
Rather, he'd be raising hell about using autoload and not loading plugins manually, so you're not safe either way.
Rather, he'd be raising hell about using autoload and not loading plugins manually, so you're not safe either way.
-
- Joined: Tue Dec 25, 2007 8:26 am
- Status: better than you
- Contact:
Re: Function not here?
DON'T USE AUTOLOAD! Kids these days :V
- Eake4
- Australian Zeus
- Joined: Tue Jul 26, 2011 6:15 am
- Status: Doing something useless again
- Location: Sydney, Australia
Re: Function not here?
Probably gonna follow Hatt's "Sage & Wise" technique of not using daa() currently i have no real need for it but later it might prove useful for cleaning footage.
- Cannonaire
- Joined: Wed May 05, 2010 5:59 pm
- Status: OVERLOAD
- Location: Oregon
Re: Function not here?
Solution to Avisynth not finding plugins/scripts:
Keep your plugins organized in a specific, easy-to-remember folder (mine is c:\avsplugins), then loadplugin/import the ones you need when needed.
Example:
Doing so allows you to avoid potential conflicts most of the time as well as being a good workaround in your current situation. The only drawback is that you do have to manually load the plugins in each script, which can be annoying at times. It is well worth it in my opinion.
Keep your plugins organized in a specific, easy-to-remember folder (mine is c:\avsplugins), then loadplugin/import the ones you need when needed.
Example:
Code: Select all
LoadPlugin("C:\avsplug\TIVTC.dll")
Import("C:\avsplug\script\MCTemporalDenoise.v1.4.16.avsi")
Think millionaire, but with cannons. || Resident Maaya Sakamoto fan.
-
- Joined: Tue Dec 25, 2007 8:26 am
- Status: better than you
- Contact:
Re: Function not here?
I have an avs plugin manager which I'll probably eventually upload to github or somewhere. I suggest doing the same for others, but Cannonaire's method of manually loading what you need is great. Of course, it helps to have a program that scans your script and any dependent scripts to find and load exactly the plugins you need, but other than dependencies the above method is A++ for most users. I think my setup is only required due to the sheer size of my own avs scripts, often several thousand lines.
Autoload is kinda bad anyway for some stuff, and it helps to avoid it when you have multiple plugins, or versions of the same plugin, providing the same function name.
Autoload is kinda bad anyway for some stuff, and it helps to avoid it when you have multiple plugins, or versions of the same plugin, providing the same function name.