Closed z826540272 closed 3 years ago
The obvious question to ask here is: What AviSynth version are you using?(It's shown on the Settings tab of the Config screen.) I encountered same issue yesterday. It was probably caused by incompatibility between new AviSynth Filter and old AviSynth+.
if you're using "official" build from Github - install Avisynth 3.5.1 (or 3.6+) manually note that 3.6+ has compatibility issues with ffdshow so if you want to keep ffdshow path working you'd better stick with 3.5.1
I'll update README about the version requirement.
CreateScriptEnvironment{}returns nullptr