How to list "blocked" (failed) LV2 plugins?

[mjolnir]

Starting LMMS from the terminal in Linux, I get the advice:

Code: Select all

Lv2 plugin SUMMARY: 220 of 287  loaded in 5845 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.

However, when I set the variable using SET, and re-run the LMMS AppImage, nothing changes, and I get no additional info. Is there a log filed somewhere that I can read to find out which plugins were blocked or failed to scan?

Otherwise, I'd like to request that as a feature: (please store a list of blocked/failed LV2 plugins inside of a file inside of the LMMS prefs folder). For that matter, it'd be nice to get a list of blocked/failed LADSPA plugins also.

Any assistance on this topic is greatly appreciated.

[musikbear]

Code: Select all

Blocked Lv2 Plugins: 16 of 287 
  If you want to enable them (dangerous!), please set
  environment variable "LMMS_ENABLE_BLOCKED_PLUGINS" to nonempty.

If we should investigate this, we need to know the version of LMMS. Including the +.... string

[mjolnir]

Oh, thanks. OK:
LMMS
Version 1.3.0-alpha.1.1034+4e677cb (Linux/x86_64, Qt 5.15.3, GCC 11.4.0).

I'm on CachyOS Linux with the XFCE DE and using a "stable" recent kernel: 7.1.8-1-cachyos

And I must say that I'm very impressed with the recent LMMS Nightlies.
I'm not getting any crashiness anymore, so I'm able to work on projects much more thoroughly and I'm actually learning to use the features one by one. Huge thanks to you and the LMMS devs.

I'm really impressed. I didn't even know about the LMMS built-in effects until recently.
LMMS is continuing to be very polished and very well-thought out.

Thanks for your help.

[mjolnir]

I just noticed this: LV2: Block plugins that require GUI support (#6486)
from the GitHub page. My best guess is that my LSP(?) LV2's are getting blocked for that reason.
Also, the LSP's give REAPER a wierd "http" error during REAPER's startup.

So I guess I'm not going to worry about it.
Besides, I ought to try out the brand new Alpha version! Yay!

[musikbear]

Besides, I ought to try out the brand new Alpha version!

It would be interesting to hear if the behaviour is different in Alpha.2

[mjolnir]

Besides, I ought to try out the brand new Alpha version!

It would be interesting to hear if the behaviour is different in Alpha.2

OK, so I tried the same thing in Alpha.2, and unfortunately I'm getting the same result.
Specifically, I set the variable ("SET LMMS_LV2_DEBUG=1") and checked (using "env"), then ran LMMS. I get zero terminal output about plugins, and no generated log files.

Also, I peeked within LMMS to see if the effect menu had anything different, and nothing's different.

However, on the bright side, most/maybe all of the LSP plugins are loading. I have a lot of LV2's in my "/home/username/.lv2/" folder and LMMS reports about 287 plugins, so I don't know how to start manually without being overwhelmed.

During my actual composing, I've been using the LMMS effects, some LADSPA effects, and the Calf plugins. My WINE-staging (v9.21)/yabridge related VST2 plugins load but usually their GUI's are unresponsive (but that's probably a WINE problem). I get the same types of error in REAPER if I use a more modern WINE/WINE-staging. Again, that's probably a WINE issue.

On the good side, I can still get actual work done in LMMS using the aforementioned LMMS effects/LADSPA effects, and the Calf plugins.

I originally installed the LSP plugins to support EasyEffects, so I'm not likely to remove those.

For what it's worth, I do have some LV2's inside of "/usr/lib/lv2/", but I don't manually interact with that, and some of those are things such as Carla and Yoshimi and OB-Xf and several technical LV2's that I don' recognize.

Thanks for trying to help out.
If I learn anything more useful, I'll be back.

[musikbear]

OK, so I tried the same thing in Alpha.2, and unfortunately I'm getting the same result.

Outch : (

If I learn anything more useful, I'll be back

.
Thanks!

[mjolnir]

Ah, it's okay. I'm still getting good audio work done in LMMS.
And I'm able to get useful linux plugins working as effects.
Here's a quick screenshot of the ones that did seem to load:

Also, I tested running REAPER from the commandline, and the LSP plugins literally give REAPER 258 different errors upon each startup. So I have a feeling that they are maybe a little bit buggy somehow. I don't get any errors from any other plugins during REAPER lauching. This is ironic to me, because there's a guy on the REAPER forums who swears that the Calf plugins are buggy, but I find them to be stable (and LMMS comes with some(?)|all(?) of the Calf plugins, right?

EXAMPLE portion of LV2 errors in Reaper:

Code: Select all

lv2: /usr/lib/lv2/lsp-plugins.lv2/ http://lsp-plug.in/plugins/lv2/spectrum_analyzer_x12 - patch specified with unsupported type http://lv2plug.in/ns/ext/atom#String

But of course LMMS isn't Reaper, and Reaper isn't LMMS. So I digress.
Good working combo, though. Import/Export between the two is great so long as the BPM's match, which is easy to do.