Hybrid 2022.03.20.1: No module named 'vsdpir'

[Dan64]

From VapourSynth documentation

Windows

Windows has in total 3 different autoloading directories: user plugins, core plugins and global plugins. They are searched in that order. User plugins are always loaded first so that the current user can always decide which exact version of a plugin is used. Core plugins follow. Global plugins are placed last to prevent them from overriding any of the included plugins by accident.

The searched paths are:

1. <AppData>\VapourSynth\plugins32 or <AppData>\VapourSynth\plugins64
   
2. <VapourSynth path>\core32\plugins or <VapourSynth path>\core64\plugins
   
3. <VapourSynth path>\plugins32 or <VapourSynth path>\plugins64
   

Note that the per user path is not created by default. On modern Windows versions the AppData directory is located in <user>\AppData\Roaming by default.

Shortcuts to the global autoload directory are located in the start menu.

Avisynth plugins are never autoloaded. Support for this may be added in the future.

User plugins should never be put into the core\plugins directory.

Windows Portable

The searched paths are:

1. <VapourSynth.dll path>\vapoursynth32\coreplugins or <VapourSynth.dll path>\vapoursynth64\coreplugins
   
2. <VapourSynth.dll path>\vapoursynth32\plugins or <VapourSynth.dll path>\vapoursynth64\plugins
   

User plugins should never be put into the coreplugins directory.

In my case the portable version was located in "D:\Programs\VapourSynth64Portable\VapourSynth64"

In my installation VapourSynth.dll used by Hybrid is located in "D:\Programs\Hybrid\64bit\Vapoursynth" the KNLMeansCL.dll located by "autoload" was in the directory "D:\Programs\VapourSynth64Portable\VapourSynth64\vapoursynth64\plugins", while following the documentation the search paths used by the autoload should be:

"D:\Programs\Hybrid\64bit\Vapoursynth\core64\plugins"
"D:\Programs\Hybrid\64bit\Vapoursynth\plugins64"
"D:\Programs\Hybrid\64bit\Vapoursynth\Vapoursynth64\coreplugins"
"D:\Programs\Hybrid\64bit\Vapoursynth\Vapoursynth64\plugins"

of these directories only the last 2 are present and are almost empty, so I still don't understand how was possible the autoload of KNLMeansCL.dll in "D:\Programs\Hybrid\64bit\Vapoursynth".