That is why I was curious, since the plugin manager showed “Stale” state for all of the listed LV2 plugins.
Nothing happens. How do I trigger an LV2 rescan?
As mentioned in my earlier post the plugin manager (the dialog in the screenshot you provided) has several buttons on the left hand side, one of which is labeled “Re-scan All.” Just click that button.
See above
LV2s are always and unconditionally indexed when loading a session or starting Ardour.
Do you think the program’s inability to index could be from two different liblilvs in conflict?
Does lv2ls -n | grep -iE "nekobi|dragonfly|surge"
show that it’s able to see your different plugins?
What does sudo ldconfig -p | grep lilv
show?
Chances are your self compiled lilv is either buggy or something went wrong when you compiled and installed it.
Nothing.
This is shows even when I uninstalled both the apt version as well as the 0.24.24 compiled lilv.
rave@rave-machine:~/Documents/github/lilv$ sudo ldconfig -p | grep lilv
liblilv-0.so.0 (libc6,x86-64) => /usr/local/lib/x86_64-linux-gnu/liblilv-0.so.0
liblilv-0.so (libc6,x86-64) => /usr/local/lib/x86_64-linux-gnu/liblilv-0.so
That shows even if I ardour doesn’t start up from the lack of any lilv
rave@rave-machine:~/Documents/github/lilv$ ardour8
/usr/local/lib/ardour8/ardour-8.6.0: error while loading shared libraries: liblilv-0.so.0: cannot open shared object file: No such file or directory
When I manually install lilv, the command returns:
rave@rave-machine:~/Documents/github/lilv/build$ ldconfig -p | grep lilv
liblilv-0.so.0 (libc6,x86-64) => /usr/local/lib/x86_64-linux-gnu/liblilv-0.so.0
liblilv-0.so (libc6,x86-64) => /usr/local/lib/x86_64-linux-gnu/liblilv-0.so
When I compile and manually install lilv from here (the 0.24.24 tag that doesn’t cause the glitch):
https://github.com/lv2/lilv
Ardour suddenly becomes unable to detect lv2
When I install:
liblilv-0-0/noble,now 0.24.22-1build1 amd64 [installed,automatic]
library for simple use of LV2 plugins
liblilv-dev/noble,now 0.24.22-1build1 amd64 [installed]
library for simple use of LV2 plugins (development files)
Ardour can detect the lv2 plugins but since it’s 0.24.22, there’s the bug that randomly affects projects.
This is the build configuration for lilv that I use which allows me to open the affect projects, but causes the inability to detect l2v plugins
lilv 0.24.24
Components
Tests : YES
Tools : YES
Documentation : NO
Configuration
Default LV2_PATH: ~/.lv2:/usr/local/lib/x86_64-linux-gnu/lv2:/usr/lib/x86_64-linux-gnu/lv2
Directories
Install prefix : /usr/local
Headers : /usr/local/include
Libraries : /usr/local/lib/x86_64-linux-gnu
Executables : /usr/local/bin
Man pages : /usr/local/share/man
Found ninja-1.11.1 at /usr/bin/ninja
Yeah, the problem seems to be that your compiled lilv only looks for plugins in
but you actually have them installed in /usr/lib/lv2, as per your previous comment:
The quick-n-dirty fix is to link ~/.lv2 to /usr/lib/lv2 by making sure you don’t have a ~/.lv2 folder and then run ln -s /usr/lib/lv2 ~/.lv2
Or you can recompile lilv after first configuring it with something like
meson setup -Ddefault_lv2_path=~/.lv2:/usr/lib/lv2:/usr/local/lib/x86_64-linux-gnu/lv2:/usr/lib/x86_64-linux-gnu/lv2:/usr/local/lib/lv2
Recompiled liblilv. It’s fixed, thank you everyone!!!
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.