LSFplus - "ERROR: Average Plane: This filter can only be used within run-time filters"

[radpopl]

When using LSFplus(preset="slow", strength-20) in the log (created by AviSynth using SetLogParams) I find something like this:

ERROR: Average Plane: This filter can only be used within run-time filters
---------------------------------------------------------------------
ERROR: Average Plane: This filter can only be used within run-time filters
(C:/ProgramData/AviSynth+/plugins64+/ExTools.avsi, line 7323)
---------------------------------------------------------------------
ERROR: Average Plane: This filter can only be used within run-time filters
---------------------------------------------------------------------
ERROR: Average Plane: This filter can only be used within run-time filters
(C:/ProgramData/AviSynth+/plugins64+/ExTools.avsi, line 7323)

Nevertheless, LSFplus It seems to work, but is it optimal and should it be this way?

Script:

BSource("2024_12_26 14_52_34 (PXL_20241226_145234798).mp4",timecodes=".2024_12_26 14_52_34 (PXL_20241226_145234798).txt",atrack=-1).TimeCodeFPS(".2024_12_26 14_52_34 (PXL_20241226_145234798).txt",fpsnum=59940,fpsden=1001,report=false).ConvertToYUV444.TurnRight
propSet("_ColorRange", 0)
DRRife(method=1,maxdups=20,preset="vfr",model=73)
ConvertBits(10)
dfttest(tbsize=9,tmode=1)
ApplyGradationCurves(lumapoints="0,0,16,8,32,24, 63,63,127,127,192,192, 222,230,254,255")
lsfplus(preset="slow", strength=10)
Prefetch

[Dogway]

Thanks for the report, Ill have a look. As for the usage it seems ok, but for 1080 or 2160, you should test the different Smethod and Smode options. I personally like to use ex_unsharp() with safe=true, and play with the Fc values.