TL;DR;
I found out about this project by pure coincidence and I thought you may be able to assist OR redirect me to someone who could. Otherwise I'll go through my normal discord synocommunity channels.
I'm a SynoCommunity ffmpeg maintainer and need help in testing vulkan intel-based GPU acceleration (and if this works out on a DS425+ I may switch my DS918+ to this newer model 🤷 ).
This may be a long-shot and feel-free to say you're not interested, I would totally get that.
Long-version
I'm a maintainer part of the SynoCommunity and worked on getting vulkan acceleration built into our ffmpeg package (on top of already supported QSV, VAAPI and OpenCL). I have an on-going PR SynoCommunity/spksrc#6867 where I updated to the latest available versions of intel-compute-runtime and IGC using patched llvm-14 and, most importantly, i was finally able to add meson intel vulkan ANV driver.
I was at the stage of testing things out on my DS918+ until I got nagged with an incompatibility with the default 4.4.x kernel (apollolake CPU arch)... reading things through it seems geminilakenk which is what I believe DS425+ is running uses a 5.10 kernel which would be compatible with mesa vulkan driver (at least in theory).
Long-story-short, I would need someone to test this out. Last github builds are available here: https://github.com/SynoCommunity/spksrc/actions/runs/20557448743
Documentation to test already functional VAAPI, QSV and OpenCL is here https://github.com/SynoCommunity/spksrc/wiki/FAQ-FFmpeg
In theory, it should be a matter of ensuring your username is in the videodriver group then trying out /var/packages/synocli-videodriver/target/bin/vulkaninfo. Last time I had to work build options for OpenCL icd.d location and it may be the case as well for vulkan, if that is not working out enforcing where the icd json file location might do the trick:
VK_ICD_FILENAMES=/var/packages/synocli-videodriver/target/etc/vulkan/icd.d/intel_icd.x86_64.json /var/packages/synocli-videodriver/target/bin/vulkaninfo
If that works out then output of ffmpeg7 -hide_banner -filters | grep vulkan and running a benchmark similar as those I used for other acceleration types would be awesome.
TL;DR;
I found out about this project by pure coincidence and I thought you may be able to assist OR redirect me to someone who could. Otherwise I'll go through my normal discord synocommunity channels.
I'm a SynoCommunity ffmpeg maintainer and need help in testing vulkan intel-based GPU acceleration (and if this works out on a DS425+ I may switch my DS918+ to this newer model 🤷 ).
This may be a long-shot and feel-free to say you're not interested, I would totally get that.
Long-version
I'm a maintainer part of the SynoCommunity and worked on getting vulkan acceleration built into our ffmpeg package (on top of already supported QSV, VAAPI and OpenCL). I have an on-going PR SynoCommunity/spksrc#6867 where I updated to the latest available versions of intel-compute-runtime and IGC using patched llvm-14 and, most importantly, i was finally able to add meson intel vulkan ANV driver.
I was at the stage of testing things out on my DS918+ until I got nagged with an incompatibility with the default 4.4.x kernel (apollolake CPU arch)... reading things through it seems geminilakenk which is what I believe DS425+ is running uses a 5.10 kernel which would be compatible with mesa vulkan driver (at least in theory).
Long-story-short, I would need someone to test this out. Last github builds are available here: https://github.com/SynoCommunity/spksrc/actions/runs/20557448743
Documentation to test already functional VAAPI, QSV and OpenCL is here https://github.com/SynoCommunity/spksrc/wiki/FAQ-FFmpeg
In theory, it should be a matter of ensuring your username is in the
videodrivergroup then trying out/var/packages/synocli-videodriver/target/bin/vulkaninfo. Last time I had to work build options for OpenCL icd.d location and it may be the case as well for vulkan, if that is not working out enforcing where the icd json file location might do the trick:If that works out then output of
ffmpeg7 -hide_banner -filters | grep vulkanand running a benchmark similar as those I used for other acceleration types would be awesome.