I see, thanks for the clarification.
Isn't the AVS+ CUDA framework use feasible?
https://forum.doom9.org/showthread.php? ... ost1943973Such an Avisynth+ build does not use CUDA at all, it is just able to host such filters; the only known plugin set which is compatible with this interface is https://github.com/pinterf/AviSynthCUDAFilters which is there for people/developers who'd like to play with this interface.
https://github.com/pinterf/AviSynthCUDA ... umentationCUDA-capable Avisynth+ is simply an Avisynth+ which can support CUDA-aware filters. Nothing is accelerated inside.
AvisynthCUDAFilters.txt, AvisynthNeoFeatures.txt, build_help.txt
I don't know what that means and reading the links doesn't tell me. Setting up a pipeline of filters that all run on the GPU without transferring data except at the start and end of the chain is what is needed. How would that be done?CUDA-capable Avisynth+ is simply an Avisynth+ which can support CUDA-aware filters.
This documentation in the English translation of https://github.com/nekopanda/AviSynthPlus/wiki
1. Avisynth is CUDA compatible!
[snipped for readability -- admin]
8. CUDA compatible Avisynth filters (some by external AvsCUDA.dll)
A filter that can be used inside OnCPU() and OnCUDA().
This is the case when AvsCUDA.dll included in KFM is added.
<INFO REMOVED>
9. Sample Avisynth Filter (needs update for Avisynth+ 3.7 level)
https://github.com/nekopanda/AviSynthPlusCUDASample