Should I re-install?

[lmv]

Well, all those plugins are blacklisted again now. You know how to remove them from the blacklist and rescan, but first you're going to have to find out why your system doesn't get along with them. I don't know why. I don't even use Windows.

Linux can run most Windows plugins with the help of linvst. I downloaded and tried Afroplug, and it works. Of course, "works for me" is useless to you, except to know that the plugin can run on some condition or other.

I can also run the Windows version of Waveform, which I never use. I added all my drum plugins to it including Afroplug, and 64-bit Afroplug works there, too. However, I noticed that most of my plugins were rejected (including 32-bit Afroplug), and a quick glance at the list of rejected plugins suggests that they were all 32-bit which means I would have to use jbridge to make them work because there isn't a 32-bit version of Waveform. 32-bit plugins run on Linux Waveform, but that is thanks to linvst which does some kind of bridging of its own. You seem to have 64-bit (clearly named so) plugins in your list of rejected plugins, but you also seem to have 32-bit (clearly named so) plugins in it, so the last ditch suggestion I can make is that you make sure you are using 64-bit versions of all plugins OR that you make 64-bit versions of all 32-bit plugins with jbridge, and try again. Remove them from the blacklist and rescan.

I also suggest you install the demo version of Mulab (www.mutools.com). Version 8 is free but with multiple restrictions, it won't run any external plugins. Use the demo (8 or 9, whatever). Even if you don't like Mulab, you can and probably should test your plugins in it. Windows programs or plugins may fail due to lack or incompatibility of libraries, especially after Windows 7. I have tried Windows 8, 10 and 11, and a lot of stuff that used to work fine on XP don't work on those. If your plugins run on Mulab but won't run on Waveform, then you can finally blame Waveform.

Yes, it's a headache, but that's computers for ya.

[irpacynot]

Well, all those plugins are blacklisted again now. You know how to remove them from the blacklist and rescan, but first you're going to have to find out why your system doesn't get along with them. I don't know why. I don't even use Windows.

Linux can run most Windows plugins with the help of linvst. I downloaded and tried Afroplug, and it works. Of course, "works for me" is useless to you, except to know that the plugin can run on some condition or other.

I can also run the Windows version of Waveform, which I never use. I added all my drum plugins to it including Afroplug, and 64-bit Afroplug works there, too. However, I noticed that most of my plugins were rejected (including 32-bit Afroplug), and a quick glance at the list of rejected plugins suggests that they were all 32-bit which means I would have to use jbridge to make them work because there isn't a 32-bit version of Waveform. 32-bit plugins run on Linux Waveform, but that is thanks to linvst which does some kind of bridging of its own. You seem to have 64-bit (clearly named so) plugins in your list of rejected plugins, but you also seem to have 32-bit (clearly named so) plugins in it, so the last ditch suggestion I can make is that you make sure you are using 64-bit versions of all plugins OR that you make 64-bit versions of all 32-bit plugins with jbridge, and try again. Remove them from the blacklist and rescan.

I also suggest you install the demo version of Mulab (www.mutools.com). Version 8 is free but with multiple restrictions, it won't run any external plugins. Use the demo (8 or 9, whatever). Even if you don't like Mulab, you can and probably should test your plugins in it. Windows programs or plugins may fail due to lack or incompatibility of libraries, especially after Windows 7. I have tried Windows 8, 10 and 11, and a lot of stuff that used to work fine on XP don't work on those. If your plugins run on Mulab but won't run on Waveform, then you can finally blame Waveform.

Yes, it's a headache, but that's computers for ya.

Yeah, I typically install both the 32 and 64-bit versions of plugins if I have an issue when scanning the first time.

But yeah, after reflecting, it occurred to me that Windows has locked up, forcing me to restart a few times, giving me a thread-related error message. So, yeah, it seems it's a Windows issue. And I think they updated not more than a few weeks ago. I've checked to see if there are any additional updates, but none thus far.

Guess I shouldn't be too surprised. Whether intentional or not, these massive corporate softwares never seem to play nice with others.