Esxi running macos For selur

[shijan]

Have no idea if it may be a source of problem, but i noticed some names confusion in VS Editor window:

# Loading Plugins
core.std.LoadPlugin(path="/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libneo-fft3d.dylib")
As you may remember neo-fft3d don't works on macOS and formally don't exists yet on macOS, so it probably needs to load fft3dfilter instead?

core.std.LoadPlugin(path="/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libvsznedi3.dylib")
I see only plug-in named libznedi3.dylib in that folder

core.std.LoadPlugin(path="/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libvslsmashsource.dylib")
I see only plug-in named liblsmashsource.dylib in that folder

---

Main thing that is annoying on Linux and Mac is that there's no good (manageable way) to create a portable Vapoursynth.

Just adjust it to l33tmeatwad's VapourSynth Installer & Plugins package and everybody will be happy. It worked well all this time with old Hybrid. And forum users even where able to find some bugs in plug-ins (like broken last versions of MVtools-v22 and v23). All plug-ins where updated to self-contained versions and don't require external dependencies libraries anymore. Some people use this package with command line, some use with Hybrid. Totally universal package. And it takes just few clicks to install VapourSynth from .pkg installer and copy plug-ins and scripts to folder alias.
For sure i will keep support this package and will update it with new plug-ins and components releases when possible, but i wonder why don't you collaborate somehow into single all-in one DMG package release? Formally you develop and compile two equal large parts of same system (VapourSynth + Plug-ins + QTGMC + Hybrid)