View Full Version : Help troubleshooting: can't load a plugin
ajp_anton
30th January 2020, 11:04
I'm having trouble with this plugin:
http://avisynth.nl/index.php/Spinner
http://www.avisynth.nl/users/vcmohan/movePlus/movePlus.7z
I'm trying to use the "turn" function. The x86 version works fine, the x64 one doesn't.
colorbars
turn(angle=45.0)
"There is no function named 'turn'."
Also,
loadplugin("movePlus.dll")
colorbars
turn(angle=45.0)
Cannot load file '...'.
Platform returned code 126:
The specified module could not be found.
Loading the same script using 32-bit software returns the expected "Cannot load a 64 bit DLL in 32 bit Avisynth", so the path is correct.
The exact same x64 DLL works in another computer using the exact same Avisynth+ version on the same Windows 10 with the same Visual Studio C++ stuff installed.
Avisynth version is 3.4 r2923 (but had the same problem using r2772 as well).
Groucho2004
30th January 2020, 12:58
Put the movePlus plugin into your 64 bit auto-load directory and run this tool:
https://forum.doom9.org/showthread.php?t=176079
StainlessS
30th January 2020, 16:19
Avs 2.6 x64 CPP plugin, req msvcr120.dll from VS 2013, CPP runtimes.
MS Official page:- https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
CPP runtimes AIO (All in one) on github (Smaller and less bloated than official):- https://github.com/abbodi1406/vcredist/releases
[If you are missing the runtimes, run Grouchy tool]
EDIT: Oops, forgot the AIO link, fixed.
ajp_anton
30th January 2020, 16:34
Put the movePlus plugin into your 64 bit auto-load directory and run this tool:
https://forum.doom9.org/showthread.php?t=176079
[OS/Hardware info]
Operating system: Windows 10 (x64) (Build 18362)
CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz / Sandy Bridge (Core i7)
MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX
4 physical cores / 8 logical cores
[Avisynth info]
VersionString: AviSynth+ 3.4 (r2923, 3.4, x86_64)
VersionNumber: 2.60
File / Product version: 3.4.0.0 / 3.4.0.0
Interface Version: 6
Multi-threading support: Yes
Avisynth.dll location: C:\WINDOWS\SYSTEM32\avisynth.dll
Avisynth.dll time stamp: 2019-10-20, 11:58:12 (UTC)
PluginDir2_5 (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64
PluginDir+ (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64+
[CPP 2.5 Plugins (64 Bit)]
C:\Program Files (x86)\AviSynth+\plugins64\dither.dll [2014-09-24]
[CPP 2.6 Plugins (64 Bit)]
C:\Program Files (x86)\AviSynth+\plugins64+\ConvertStacked.dll [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64+\DirectShowSource.dll [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64+\ImageSeq.dll [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64+\Shibatch.dll [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64+\TimeStretch.dll [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64+\VDubFilter.dll [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64\ConvertStacked.dll [2019-08-29]
C:\Program Files (x86)\AviSynth+\plugins64\DePan.dll [2.13.1.3]
C:\Program Files (x86)\AviSynth+\plugins64\DePanEstimate.dll [2.10.0.2]
C:\Program Files (x86)\AviSynth+\plugins64\DirectShowSource.dll [2019-08-29]
C:\Program Files (x86)\AviSynth+\plugins64\eedi3.dll [0.9.2.1]
C:\Program Files (x86)\AviSynth+\plugins64\FastBlur.dll [2019-06-30]
C:\Program Files (x86)\AviSynth+\plugins64\ffms2.dll [2016-12-29]
C:\Program Files (x86)\AviSynth+\plugins64\fft3dfilter.dll [2.6.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\grunt-x64.dll [2016-05-17]
C:\Program Files (x86)\AviSynth+\plugins64\ImageSeq.dll [2019-08-29]
C:\Program Files (x86)\AviSynth+\plugins64\masktools2.dll [2.2.17.0]
C:\Program Files (x86)\AviSynth+\plugins64\movePlus.dll [2018-04-09]
C:\Program Files (x86)\AviSynth+\plugins64\mvtools2.dll [2.7.31.0]
C:\Program Files (x86)\AviSynth+\plugins64\nnedi3.dll [0.9.4.41]
C:\Program Files (x86)\AviSynth+\plugins64\RgTools.dll [0.97.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\Shader-x64.dll [2016-01-19]
C:\Program Files (x86)\AviSynth+\plugins64\Shibatch.dll [2019-08-29]
C:\Program Files (x86)\AviSynth+\plugins64\SmoothAdjust.dll [3.2.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\TimeStretch.dll [2019-08-29]
C:\Program Files (x86)\AviSynth+\plugins64\VDubFilter.dll [2019-08-29]
[Scripts (AVSI)]
C:\Program Files (x86)\AviSynth+\plugins64+\colors_rgb.avsi [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64\colors_rgb.avsi [2016-07-05]
C:\Program Files (x86)\AviSynth+\plugins64\dither.avsi [2014-09-24]
C:\Program Files (x86)\AviSynth+\plugins64\FFMS2.avsi [2019-03-19]
C:\Program Files (x86)\AviSynth+\plugins64\LSFmod.v1.9.avsi [2014-01-06]
C:\Program Files (x86)\AviSynth+\plugins64\MT.avsi [2018-08-09]
C:\Program Files (x86)\AviSynth+\plugins64\Shader.avsi [2016-05-05]
[Uncategorized DLLs (64 Bit)]
C:\Program Files (x86)\AviSynth+\plugins64\libfftw3f-3.dll [2016-07-30]
[Uncategorized files]
C:\Program Files (x86)\AviSynth+\plugins64+\colors_rgb.txt [2019-10-20]
C:\Program Files (x86)\AviSynth+\plugins64\colors_rgb.txt [2016-07-05]
C:\Program Files (x86)\AviSynth+\plugins64\ffms2.lib [2016-12-29]
C:\Program Files (x86)\AviSynth+\plugins64\ffmsindex.exe [2016-12-29]
[Plugin errors/warnings]
____________________________________________________________________________________________________________
"C:\Program Files (x86)\AviSynth+\plugins64\DePanEstimate.dll" requires the FFTW library for some functions.
Note: 'libfftw3f-3.dll' can be downloaded here:
http://www.fftw.org/install/windows.html
'libfftw3f-3.dll' should be placed in "System32" and/or "SysWoW64"
____________________________________________________________________________________________________________
Cannot load file 'C:/Program Files (x86)/AviSynth+/plugins64/eedi3.dll'. Platform returned code 126:
The specified module could not be found.
Dependencies that could not be loaded:
VCOMP120.DLL
Note: Visual Studio 2013 Runtime doesn't seem to be installed
____________________________________________________________________________________________________________
"C:\Program Files (x86)\AviSynth+\plugins64\fft3dfilter.dll" requires the FFTW library for some functions.
Note: 'libfftw3f-3.dll' can be downloaded here:
http://www.fftw.org/install/windows.html
'libfftw3f-3.dll' should be placed in "System32" and/or "SysWoW64"
____________________________________________________________________________________________________________
Cannot load file 'C:/Program Files (x86)/AviSynth+/plugins64/movePlus.dll'. Platform returned code 126:
The specified module could not be found.
Dependencies that could not be loaded:
MSVCR120.dll
Note: Visual Studio 2013 Runtime doesn't seem to be installed
____________________________________________________________________________________________________________
"C:\Program Files (x86)\AviSynth+\plugins64\mvtools2.dll" requires the FFTW library for some functions.
Note: 'libfftw3f-3.dll' can be downloaded here:
http://www.fftw.org/install/windows.html
'libfftw3f-3.dll' should be placed in "System32" and/or "SysWoW64"
____________________________________________________________________________________________________________
It's there under 2.6 plugins, pretending there's no problem.
Also I see some unnecessary warnings about a missing libfft file that I already have. It's in the "wrong place", but it's working fine.
StainlessS
30th January 2020, 16:54
Cannot load file 'C:/Program Files (x86)/AviSynth+/plugins64/movePlus.dll'. Platform returned code 126:
The specified module could not be found.
Dependencies that could not be loaded:
MSVCR120.dll
Note: Visual Studio 2013 Runtime doesn't seem to be installed
as in my prev post [download the one in blue].
Avs 2.6 x64 CPP plugin, req msvcr120.dll from VS 2013, CPP runtimes.
MS Official page:- https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
CPP runtimes AIO (All in one) on github (Smaller and less bloated than official):- https://github.com/abbodi1406/vcredist/releases
[If you are missing the runtimes, run Grouchy tool]
EDIT: Oops, forgot the AIO link, fixed.
ajp_anton
30th January 2020, 22:36
as in my prev post [download the one in blue].
Well would you look at that, it worked. Thanks! Weird part is, these two computers had a completely identical list of those installed, now this one has a few more.
StainlessS
30th January 2020, 23:26
Actually, I recently had problem with VS CPP 2013 runtimes on XP64, reinstall/uninstall were both failing for vs2013 runtimes (official install exe, and Control Panel uninstall).
(think problem was to do with some certificate or something, maybe certificate expired or similar)
[EDIT: So I was left with a system that had a sort of half installed vs2013 runtimes, ie broken]
I tried the github AIO installer (linked previously), and it solved the problems and installed correctly [official MS installer just point blank refused install].
EDIT: Actually, I extracted the AIO installer[EDIT: 7zip] , and just ran the 2013 installer part, not the Install all runtimes .bat thingy.
I think there were actually 4 installers, for
x86 install vs 2013 basic(or some other similar word)
x86 install vs 2013 additional(or some other similar word)
x64 install vs 2013 basic(or some other similar word)
x64 install vs 2013 additional(or some other similar word)
EDIT:
The VS2013 runtimes would also solve this problem
Cannot load file 'C:/Program Files (x86)/AviSynth+/plugins64/eedi3.dll'. Platform returned code 126:
The specified module could not be found.
Dependencies that could not be loaded:
VCOMP120.DLL
Note: Visual Studio 2013 Runtime doesn't seem to be installed
Groucho2004
31st January 2020, 10:39
Also I see some unnecessary warnings about a missing libfft file that I already have. It's in the "wrong place", but it's working fine.Could you please define 'wrong place' and elaborate on 'it's working fine'?
I'm aware of just two ways to load the fftw DLLs:
Load them implicitly by placing them in System32 and/or SysWoW64 (or another directory that is reachable through the standard Windows search hierarchy)
Load them explicitly through tsp's 'LoadDLL' helper plugin.
Functions within plugins that use the fftw DLLs will fail if neither of the above methods is used.
TheFluff
31st January 2020, 16:52
Could you please define 'wrong place' and elaborate on 'it's working fine'?
I'm aware of just two ways to load the fftw DLLs:
Load them implicitly by placing them in System32 and/or SysWoW64 (or another directory that is reachable through the standard Windows search hierarchy)
Load them explicitly through tsp's 'LoadDLL' helper plugin.
Functions within plugins that use the fftw DLLs will fail if neither of the above methods is used.
Avs+ passes LOAD_WITH_ALTERED_SEARCH_PATH to LoadLibraryEx (https://github.com/pinterf/AviSynthPlus/blob/b8fc314b76a9f0cbdc5fa118bcb8f0feb7ba6f82/avs_core/core/PluginManager.cpp#L754), which means the dependency search will start in the folder the loaded module is in (that is, the plugins folder). Putting libfftw3.dll in the plugins dir is thus fine.
Groucho2004
31st January 2020, 17:44
Avs+ passes LOAD_WITH_ALTERED_SEARCH_PATH to LoadLibraryEx (https://github.com/pinterf/AviSynthPlus/blob/b8fc314b76a9f0cbdc5fa118bcb8f0feb7ba6f82/avs_core/core/PluginManager.cpp#L754), which means the dependency search will start in the folder the loaded module is in (that is, the plugins folder). Putting libfftw3.dll in the plugins dir is thus fine.The calls to the fftw DLLs are in the plugins themselves, for example in dtftest it's this line:
hLib = LoadLibrary("libfftw3f-3.dll");
Anyway, I tested this and AVS+ does not change what I stated above.
TheFluff
31st January 2020, 19:36
The calls to the fftw DLLs are in the plugins themselves, for example in dtftest it's this line:
hLib = LoadLibrary("libfftw3f-3.dll");
Anyway, I tested this and AVS+ does not change what I stated above.
No, it still can, but it depends on where in the plugin the call to LoadLibrary is done. Avs+ calls SetDllDirectory() with the plugins folder as the argument before loading, but then restores the search path after plugin init is done. So if the plugin calls LoadLibrary in AvisynthPluginInit it'll still work.
Groucho2004
31st January 2020, 19:57
So if the plugin calls LoadLibrary in AvisynthPluginInit it'll still work.Fair enough but the LoadLibrary call is usually in the constructor of the plugin (dfttest, fft3dfilter).
ajp_anton
1st February 2020, 00:28
Could you please define 'wrong place' and elaborate on 'it's working fine'?
I'm aware of just two ways to load the fftw DLLs:
Load them implicitly by placing them in System32 and/or SysWoW64 (or another directory that is reachable through the standard Windows search hierarchy)
Load them explicitly through tsp's 'LoadDLL' helper plugin.
Functions within plugins that use the fftw DLLs will fail if neither of the above methods is used.
All plugins I have that need libfft work fine with having it in the plugins folder.
Groucho2004
1st February 2020, 00:39
All plugins I have that need libfft work fine with having it in the plugins folder.Maybe you have your auto-load directory referenced in the PATH environment variable. If not, consider filling out an application for the Hogwarts School Of Wizardry. :D
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.