Activity for Linux Studio Plugins Project
-
SadKo modified a blog post
LSP Plugins 1.2.26!
-
LSP Plugins 1.2.26!
-
Linux Studio Plugins Project updated /lsp-plugins/CHANGELOG
-
-
-
-
-
-
-
-
-
-
-
-
-
LSP Plugins 1.2.25
-
-
-
-
-
-
-
-
-
-
-
-
-
LSP Plugins 1.2.24 released!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
LSP Plugins 1.2.23 released!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
David Harty posted a comment on ticket #17
Yes, when the package manager version didn't work. I downloaded 1.2.22 from here. Then, when that didn't work I jumped back to a version (1.1.16 IIRC) that worked, then I split the difference until I landed on 1.2.20 as the one (tarball) that worked on my ssystem and 1.2.21 as the version where the built tarballs stopped working on my system.
-
That looks strange. Have you tried builds from tarballs provided here?
-
Thats what I had done originally. The package manager updated my plugins to 1.2.22 and the vst versions stopped working. This began my investigation into what happened and determining that 1.2.20 worked, but not 1.2.21.
-
1.2.21 VST crashes on loading
-
Still I think the problem is caused by mismatching shared libraries name on your system to the system I build plugins. This may be a reason, and installing LSP Plugins from Arch Linux repository could be a better option for you.
-
yes
-
Does the UI work now?
-
yup, adding "ui" to features resolved not having a ui. who'd a thunk it.
-
Looks like you have built LSP Plugins without the UI. If you build VST2 only, you need to provide: make config FEATURES='vst2 ui' The 'ui' option is important here.
-
I'm using Manjaro (based on Arch).
-
FWIW, I built 1.2.20 from source, and ldd returns: linux-vdso.so.1 (0x00007ff598eb7000) /usr/NX/lib/libnxegl.so (0x00007ff598200000) libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x00007ff598ddc000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007ff597e00000) libm.so.6 => /usr/lib/libm.so.6 (0x00007ff598508000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007ff598daf000) libc.so.6 => /usr/lib/libc.so.6 (0x00007ff597c10000) /usr/lib64/ld-linux-x86-64.so.2 (0x00007ff598eb9000) libdl.so.2 => /usr/lib/libdl.so.2...
-
Looks like both binaries are valid. Still I suppose that the problem of loading 1.22 version is related to missing some dynamic libraries lilke libgl. What operating system and of what version do you use?
-
readelf of the 1.22 binary returns: ELF Header: Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: DYN (Shared object file) Machine: Advanced Micro Devices X86-64 Version: 0x1 Entry point address: 0x0 Start of program headers: 64 (bytes into file) Start of section headers: 12836440 (bytes into file) Flags: 0x0 Size of this header: 64 (bytes) Size of program headers: 56 (bytes) Number...
-
I don't have any idea why ldd fails to dump dependencies for shared object. For me it woks just fine: ldd liblsp-plugins-vst2.so linux-vdso.so.1 (0x00007ffd8f37a000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fc4c09f8000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fc4c09d4000) librt.so.1 => /lib64/librt.so.1 (0x00007fc4c09ca000) libsndfile.so.1 => /usr/lib64/libsndfile.so.1 (0x00007fc4c094d000) libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007fc4c0816000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1...
-
ditto: [lsp-plugins.vst.1.20]$ chmod a+x liblsp-plugins-vst2.so [lsp-plugins.vst.1.20]$ ldd liblsp-plugins-vst2.so ldd: warning: you do not have execution permission for `./liblsp-plugins-vst2.so' not a dynamic executable
-
Try to add execution permission to liblsp-plugins-vst2.so: chmod a+x liblsp-plugins-vst2.so Anyway, it is not that warning to worry about. Below you should see the list of dynamic libraries the liblsp-plugins-vst2.so depends on. Show it please.
-
Right, when I'm in the directory of a given lsp version, I get the following (for both the working 1.20 and the non working 1.21+ versions). ldd: warning: you do not have execution permission for `./liblsp-plugins-vst2.so' not a dynamic executable ditto if I run sudo ldd ...
-
Right, when I'm in the directory of a given lsp version, I get the following (for both the working 1.20 and the non working 1.21+ versions). ldd: warning: you do not have execution permission for `./liblsp-plugins-vst2.so' not a dynamic executable
-
Right, when I'm in the directory, I get the following for both the working 1.20 and the non working 1.21+ versions. ldd: warning: you do not have execution permission for `./liblsp-plugins-vst2.so' not a dynamic executable
-
You need to switch to the folder where the liblsp-plugins-vst2.so is located and enter the command there or specify the full path to the location of the file: ldd <path-to-library>/liblsp-plugins-vst2.so
-
if I enter ldd liblsp-plugins-vst2.so in a generic console, I get ldd: ./liblsp-plugins-vst2.so: No such file or directory If I enter it in either the 1.20 or 1.21+ versions the lsp-plugins.vst folder, I get ldd: warning: you do not have execution permission for `./liblsp-plugins-vst2.so' not a dynamic executable
-
IN 1.2.21 we introduced OpenGL drawing instead of slow Cairo. Maybe that can be a reason. What does ldd liblsp-plugins-vst2.so command show?
-
In both cases, (1.20 and 1.21+) liblsp-plugins-vst2.so is included in the released zip. I also tried installing my distro's (Arch/Manjaro) lsp 1.22 package instead of the downloaded files. In that case, liblsp-plugins-vst2.so was in /usr/lib/vst/lsp-plugins.vst/, but none of the vst2 plugins would load.
-
Also the problem may be related to missing some system libraries. You can check it by issuing ldd liblsp-plugins-vst2.so.
-
Hello! It looks like VST2 version of LSP Plugins can not find the liblsp-plugins-vst2.so shared library or it's version mismatches the desired. Please try to remove liblsp-plugins-vst2.so from your system and reinstall the package.
-
1.2.21 VST crashes on loading
-
-
LSP Plugins 1.2.22 released!
-
-
-
-
-
-
-
-
-
-
-
-
LSP Plugins 1.2.21 released!
-
-
-
-
1 >
