I see, maybe it is not liking it this way indeed, i have not looked into the code plus I am not a coder so i don't know much more than this sadly.
The very last thing that come to my mind and might help figure out thing is in avspmod to only do this as script, without using the LoadPlugin("C:\Program Files (x86)\AviSynth+\plugins64+\MP_Pipeline.dll") that is not needed anymore with avs+ ( it is needed inside the win32 or win64 loops of mp_pipeline as this nice tool can't auto-load plugins sadly ), anyways :
MP_Pipeline("""
### platform: win32
Version()
### ###
""")
And after the same with win64 variant
MP_Pipeline("""
### platform: win64
Version()
### ###
""")
and see what the preview window returns you for the versions of avisynth+ it is using, this is if it managed to load anything at all with mp_pipeline.
good luck
|