I can reproduce the issue here.
First thought it was a bug, but its not.
I culprit for it is this:
Previous versions of Hybrid came with an older versions of SVP (since I overlooked that there was an update), where this doesn't happen.
Didn't notice the problem since I tested the newer dlls only on Linux.
Cu Selur
Ps.: attached the dll used previously dlls.
if your copy the 64bit files into your 'Hybrid\64bit\vsfilters\FrameFilter\Interframe'-folder and the 32bit files into your 'Hybrid\32bit\avisynthPlugins'-folder everything should work again.
First thought it was a bug, but its not.
I culprit for it is this:
Quote:The latest version is: 4.3.0.168 (2019-07-28).see: https://www.svp-team.com/wiki/Manual:SVPflow
The distribution includes:Please note that SVPflow libs require a SVP Manager running (Windows and macOS only), otherwise you'll see a red rectangle around the video frame.
- svpflow1.dll, svpflow2.dll 32-/64-bit plugins for Avisynth and Vapoursynth on Windows
- svpflow1.so, svpflow2.so 64-bit plugins for Vapoursynth on Linux
- svpflow1.dylib, svpflow2.dylib 64-bit plugins for Vapoursynth on MacOS
- sample scripts
- readme and licenses files
You're free to disable SVP completely ("Temporarily disable SVP" + ui.disable_on_launch = true in All settings), however it still must be running in background.
Download link is there
Previous versions of Hybrid came with an older versions of SVP (since I overlooked that there was an update), where this doesn't happen.
Didn't notice the problem since I tested the newer dlls only on Linux.
Cu Selur
Ps.: attached the dll used previously dlls.
if your copy the 64bit files into your 'Hybrid\64bit\vsfilters\FrameFilter\Interframe'-folder and the 32bit files into your 'Hybrid\32bit\avisynthPlugins'-folder everything should work again.
----
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.