02.07.2019, 17:09
I tried it by placing the different Avisynth dlls inside the AvsPMod folder to make sure that this dll is used.
(Same can be done with ffmpeg, otherwise the first found dll will be used.)
Since I got no system wide installation of Avisynth+ (or Avisynth or Vapoursynth) I'm pretty sure this is related to using ImageSource with the Avisynth version you got on your system. (you might have some filters in your autoloading folder,... I don't have an autoloading folder.)
At least this doesn't look like an issue I can fix in Hybrid, seems more like a setup issue.
-> Won't like futher into this, especially since Hybrid already allows to read image sequences and I so no good reason to use an external Avisynth script for this.
Cu Selur
(Same can be done with ffmpeg, otherwise the first found dll will be used.)
Since I got no system wide installation of Avisynth+ (or Avisynth or Vapoursynth) I'm pretty sure this is related to using ImageSource with the Avisynth version you got on your system. (you might have some filters in your autoloading folder,... I don't have an autoloading folder.)
At least this doesn't look like an issue I can fix in Hybrid, seems more like a setup issue.
-> Won't like futher into this, especially since Hybrid already allows to read image sequences and I so no good reason to use an external Avisynth script for this.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.