18.07.2021, 16:00
Probably when selecting .dylib in Finder, Vapoursynth attempt to generate quicklook preview for file or reads something from it or somehow else interacts with it. And this provoke conflict if both filters use something similar inside that is already autoloaded in Vapoursynth.
And after conflict it is not enough to simply delete .dylib. Vapoursynth reinstall required to delete that cashed data of both conflicted plugins.
And after conflict it is not enough to simply delete .dylib. Vapoursynth reinstall required to delete that cashed data of both conflicted plugins.