[INFO] HLSL Shaders for Avisynth+

[mogobime]

That sounds nice here:
http://avisynth.nl/index.php/AviSynthShader

For example, GPU-accelerated HLSL resizers could be used to get a bit more out of AVISynth+ (DGDecNV doesn't support high color depth and isn't useful for AMD users).
And a whole bunch of other filters might also be usable with that plugin.
Since you have GLSL implemented in VapourSynth, it would be nice to have a bunch of GPU acclerated filters in AviSynth+, too. 
It also is an official up-to-date AViSynth+ X64 plugin. Quote from Github:

With AviSynth+, all filters run as MT=1 and automatically configure their mode. If you run 8 threads, it will alternate all threads between 2 engines for optimal performance.

Last version is from 2020.06.17: https://github.com/mysteryx93/AviSynthShader

Apparently it is also possible to cross-compile GLSL to HLSL with this tool, so it might be possible to port the well known filters from VapourSynth to AviSynth+.
https://github.com/septag/glslcc

cu, mogobime

[Selur]

Not sure I'll add it any time soon, since:
I more and more think I should drop AviSynth support as it is atm., since:
a. the whole AviSynth code section would need a rewrite. (it's way easier to add Vapoursynth filters than AviSynth filters with the current Hybrid source code.)
b. avsViewer should be rewritten/overhault.
c. aside from a few filters (like InpaintDelogo, RemoveDirt,.. ) I don't really thing it's worth using AviSynth nowadays.
I'm thinking about dropping AviSynth in favour or adding a Vapoursynth->Avisynth subsection which would allow to add AviSynth filters in Vapoursynth.
(note that I'm just thinking about it, so it might no happen in the forseeable future)

That said:
Have you actually tried the filter and some of the hslsl filters from https://github.com/zachsaw/MPDN_Extensio...derScripts?
Any experience with how 'Shader(...)' need to be configured for them? (I guess for at least some of them additional parameters need to be configured.)
Does this run stable? (Tested it a few years ago and couldn't get it to run stable in complex scripts. I don't want to bug MysterX, too much with potential problems, since I'm still hoping the comes around and further developes FrameRateConverter.)

DGDecNV doesn't support high color depth and isn't useful for AMD users

Are you sure? iirc it should support high bit depth on Avisynth+ and Vapoursynth iirc. (not sure whether there are some old restrictions in Hybrid)

Cu Selur

[mogobime]

DGDecNV doesn't support high color depth and isn't useful for AMD users

Are you sure? iirc it should support high bit depth on Avisynth+ and Vapoursynth iirc. (not sure whether there are some old restrictions in Hybrid)

I've meant chroma subsampling above yuv420, 10 bit is supported.

c. aside from a few filters (like InpaintDelogo, RemoveDirt,.. ) I don't really thing it's worth using AviSynth nowadays.

I would think about that. It seems so, that avs2yuv64 0.30 and probably ffmpeg, too often perform much better, if AviSynth+ scripts with correctly placed filter prefetches are used, than VapourSynth/Vspipe. I don't know, if these are the best times to trash a potentially more efficient tool (at least at older non high end systems which get fully utilized by AviSynth+).
But I can also understand that you want to focus on one frame server and don't want to realize every filter in the VapourSynth section in the AviSynth section, too.
But since there are - except of FFT3DGPU and KNLMeansCL - almost no GPU filters available, getting a bunch of GPU filters which might all get usable by implementing only one plugin in a clever way (e.g. a possibility to submit the parameters to HLSL filters via a custom field) sounds alluring

Have you actually tried the filter and some of the hslsl filters from https://github.com/zachsaw/MPDN_Extensio...derScripts?

No, not yet. Also no time atm   But there is no hurry...