by
mjolnir » August 31st, 2026, 2:16 am
I'm not sure about part II of your question: using Carla.
However, I think the linux distro has the system install *.lv2 files into: "/usr/lib/lv2/"
Meanwhile, the /home/username/.lv2/ folder is where you can manually put the pluginname.lv2 folder(s) containing the *.so files and the possibly accompanying *.ttl files.
When you download LV2 files manually, after you decompress them, each one has a WHOLE_FOLDER.lv2
So, for example, hypothetically, I download "ZL Equalizer 2". Let's say it was stored in "ZL_Equalizer_II.tar.xz". So I fully decompress "ZL_Equalizer_II.tar.xz" and get "ZL_Equalizer_II" folder. Inside the folder is maybe a *.PDF manual file and/or a "README.md" text file and of course the "ZL Equalizer 2.lv2" folder. The "ZL Equalizer 2.lv2" folder (and all of it's default contents" are the *.lv2 plugin. The plugin won't work if you disassemble that folder; it's contents go with it, and I don't think you can safely change the name either.
So, to continue the hypothetical example, inside the "ZL Equalizer 2.lv2" folder is:
lbZL Equalizer 2.so
dsp.ttl
manifest.ttl
ui.ttl
But there's not much need to look in there, since were not going to change anything INSIDE the LV2.
Let's say, my Linux username is "mjolnir".
So, I put the "ZL Equalizer 2.lv2" folder (that was just decompressed) into: /home/mjolnir/.lv2/
Additionally:
Perhaps there was also a "ZL Equalizer 2.vst3" inside of the *.tar.xz archive that was downloaded.
You would put that ENTIRE folder into the "/home/mjolnir/.vst3/" folder, if your username is "mjolnir"
As you can see, there's a pattern to this. CLAP files are different, as they usually just have the *.clap file go manually straight into the /home/username/.clap/ folder
Obviously, you have a different username, so use yours. For example, if your username is "thor", you'd put your *.lv2 folder(s) into "/home/thor/.lv2/". Likewise, you'd put *.clap FILES into "/home/thor/.clap/".
After that, log out and log back in or reboot to be safe.
The plugins are scanned during DAW program startup.
OK, so after reboot/relogin start LMMS again to get it to rescan for plugins.
NOTE: If you just double-click on the LMMS.AppImage it will run and rescan (if it's set to "executable" in your Desktop Environment's "File" >> "Properties" Menu). In that case, the plugin scanning will happen silently, of course.
If you run LMMS from the command line, you'll see a message about how many *.lv2's loaded and how many didn't and LMMS gives a brief message about what you can do about it with environmental variables.
For example: (command line stuff:)
[mjolnir@ragnarok]$ ./lmms.AppImage
[AppRun] Carla appears to be installed on this system at /usr/lib/carla so we'll use it.
[AppRun] Jack appears to be installed on this system, so we'll use it.
[AppRun] Defaulting to QT_QPA_PLATFORM="xcb" for compatibility purposes.
[AppRun] To force wayland, set QT_QPA_PLATFORM="wayland" or call using "-platform wayland".
Lv2 plugin SUMMARY: 220 of 287 loaded in 6494 msecs.
For details about not loaded plugins, please set
environment variable "LMMS_LV2_DEBUG" to nonempty.
Blocked Lv2 Plugins: 16 of 287
If you want to enable them (dangerous!), please set
environment variable "LMMS_ENABLE_BLOCKED_PLUGINS" to nonempty.
I hope this explanation isn't too wordy and I hope I didn't make any logical errors.
Please let us know if this did or didn't work or whatnot.
Again, sorry if this is TMI (too much information) and not enough of a solution.