Quote:AVSPmod is very good at picking up script errors and I regularly use it just for that.Man, you don't get it. If you use FilterView with AvisynthView and use an avs script as input the old Hybrid version has a bug. It doesn't use 'Source ='.
Believe it or not, what you call a broken script did show in avsPmod and there were no errors.
screenshot is attached which clearly shows the content of the script called..
The script you refer to is the one you feed Hybrid as input, the one I referred to is the one Hybrid feeds to avsViewer.
Quote:The suggestion that I have a version of x264 from last year is sheer nonsense. Version info is attached.it is not. Your build is from x264 0.152 (which is from 2017) not from the current 0.155 sorry that you don't see that. Current version should be: 'x264 0.155.2901 7d0ff22'
Quote:I have a working linux vapoursynth installation but that has no bearing on the Hybrid problem where I am only interested in using avisynth filters anyway and the linux vapoursynth filters cannot be used so I don't know what relevance the last reply has where you seem to refer to vapoursynth??I referred to Vapoursynth since the Debug Output you posted contained this error.
Before established that the old version had a bug regarding handling Avisynth input when FilterView and AvisynthView are used together (missing 'Source ='), which is why I compiled a modified version which should fix that. You then went back to the old version and complained about the AvisynthView not working when FilterView is sued.
=> Sorry, but I got no clue how I can help you if you do something like that.
Cu Selur
