Package: lsp-plugins-vst3 Version: 1.2.27-1 Severity: normal X-Debbugs-Cc: [email protected] User: [email protected] Usertags: arm64
Dear Maintainer, the autopkgtests for pd-vstplugin uses lsp-plugins-vst3 to check whether it (pd-vstplugin) can correctly detect VST3 plugins. this works great on amd64 and i386, but unfortunately not on arm64 (and therefore pd-vstplugin is currently stuck in sid). i finally found the time to investigate a bit and it seems that pd-vstplugin can detect all packaged VST3-plugins on arm64 (dpf-plugins-vst3, dragonfly-reverb-vst3, iem-plugin-suite-vst3 and vst3sdk-plugins), only lsp-plugins-vst3 is not detected. looking at the package contents, i see that all working packages install binaries as '/usr/lib/vst3/*.vst3/Contents/aarch64-linux/', only lsp-plugins-vst3 installs binaries as '/usr/lib/vst3/*.vst3/Contents/armv8l-linux/' [sic! even though the lsp-plugins.so file is really arm64] if I copy the files to ~/.vst3/*.vst/Contents/aarch64-linux/ they become detectable! (I'm afraid,my test environment is only amdahl.debian.org, so I cannot just fix the installation path to '/usr/lib/vst3/*.vst3/Contents/aarch64-linux/') my conclusion is, that lsp-plugins-vst3 installs the files to the wrong path on arm64, making the plugins useless on this platform. my interpretation is backed up by steinberg's documentation at [1], which says: > `MyPlugin.vst3/Contents/XXX-linux` with XXX the architecture name based on > the output of command-line "uname -m" (machine hardware) + "-linux" thanks for fixing :-) dfasr IOhannes [1] <https://steinbergmedia.github.io/vst3_dev_portal/pages/Technical+Documentation/Locations+Format/Plugin+Format.html?highlight=uname#for-the-linux-platform>
