As of 1.2.21, The VST versions of the LSP plugins are crashing in my Bitwig DAW and Carla-Rack.
When bitwig tries to pre-load them, I get the following error:
com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: createAEffectInstance returned NULL
I also tested on Carla-Rack and I simply get a popup saying "Plugin failed to initialize". and in the Logs:
[ERR] Could not find VST core library
Reverting to 1.2.20 resolves the issue.
I do not have any issues with the latest versions using clap or vst3, but some old projects were using the vst, and I needed to open them so I could save the settings to preset config.
Hello! It looks like VST2 version of LSP Plugins can not find the
liblsp-plugins-vst2.soshared library or it's version mismatches the desired. Please try to removeliblsp-plugins-vst2.sofrom your system and reinstall the package.Also the problem may be related to missing some system libraries. You can check it by issuing
ldd liblsp-plugins-vst2.so.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.
IN 1.2.21 we introduced OpenGL drawing instead of slow Cairo. Maybe that can be a reason. What does
ldd liblsp-plugins-vst2.socommand show?if I enter
ldd liblsp-plugins-vst2.soin a generic console, I getIf I enter it in either the 1.20 or 1.21+ versions the
lsp-plugins.vstfolder, I getYou need to switch to the folder where the
liblsp-plugins-vst2.sois located and enter the command there or specify the full path to the location of the file: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).
ditto if I run
sudo ldd ...Last edit: David Harty 2025-06-26
Try to add execution permission to
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.sodepends on. Show it please.ditto:
I don't have any idea why
lddfails to dump dependencies for shared object.For me it woks just fine:
Try also
readelf -h liblsp-plugins-vst2.so.readelf of the 1.22 binary returns:
The 1.20 in comparison returns:
Only difference appears to be in start of section headers.
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?
I'm using Manjaro (based on Arch).
FWIW, I built 1.2.20 from source, and ldd returns:
for 1.2.21 it returns
With the 1.2.21 build,Impulse reverb is loadable in the daw, but it does not provide a ui.
Looks like you have built LSP Plugins without the UI.
If you build VST2 only, you need to provide:
The 'ui' option is important here.
yup, adding "ui" to features resolved not having a ui. who'd a thunk it.
Does the UI work now?
yes
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.
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.
That looks strange.
Have you tried builds from tarballs provided here?
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.