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.