26.07.2020, 13:01
Quote:Ah, this one is user error, sort of. I must select Avisynth processing (default is Vapoursynth) BEFORE dropping the avs script in to load.Sure otherwise Hybrid tries to open the script using Vapoursynth,...
Quote:Which now alarms me ... why is Hybrid dipping into my "C:\Program Files (x86)\AviSynth+" folder???That's the avisynth.dll looking for default filters.
Quote:Did Hybrid add or change anything at that folder?No, Hybrid itself doesn't write anything in any Avisynth folder.
Quote: avsInfo still crashes.Without a debug output my only guess is that avsInfo 32bit is used for a 64bit script or avsInfo 64bit is used for a 32bit script or something is wrong with the script.
Without details: no real clue
Quote:So now I must ask ... is that something within Hybrid, or is it pulling from elsewhere on my system? Though I don't believe that I have avsInfo anywhere, so assuming from within Hybrid folders.Hybrid should update the avsInfo used depending on the "Avisynth type" setting,...
Would need a debug output to be sure what's happening.
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.