Bug: LADSPA plugins still not loading in 3.1.1

Unlike the situation with Vamp plugins -- for which SV has an adapter that allows it to use 32-bit plugins from a 64-bit build -- SV can currently only use LADSPA plugins that are built for the same architecture as the SV executable itself. This means in particular that a 64-bit SV build can't load 32-bit LADSPA plugins. Is that the situation here?

Hi Chris,
I think you are right. It appears that Audacity is only available as
32bit for Windows, which I have installed in my 64bit OS. Audacity's
LADSPA package for Windows installed to "C:\Program Files
(x86)\Audacity\Plug-Ins". It appears that SV, by default, scans for
all LADSPA plugins regardless of whether these plugins are in
"C:\Program Files (x86)\" or "C:\Program Files\" in Windows 64bit,
even though only "C:\Program Files\Audacity\Plug-Ins" is specified in
SV's application settings. The incompatibility "Failed to Load"
message that comes up specifies plugins within "C:\Program Files
(x86)\Audacity\Plug-Ins".

Perhaps, the 64bit SV's default behavior should be not to scan for
LADSPA plugins in C:\Program Files (x86)\ , which would most likely be
32 bit, unless the SV user has added that path in the settings.

You might want to consider adding an option to hide the same "Failed
to Load" message (e.g., check box) from popping up again. Otherwise,
the same message comes up every time I start SV, despite "C:\Program
Files (x86)\Audacity\Plug-Ins" not being specified in SV's settings.
Currently, to avoid the message, I have to uninstall Audacity's LADSPA
package to avoid the error message. Also, perhaps the :Failed to Load"
message should specify that SV 64bit is not compatible with 32bit
LADSPA plugins?

Digging in further, there are a few problems here:

1. SV's initial plugin scan is scanning both the 64-bit (correct) and 32-bit (incorrect) LADSPA directories. This is because SV separates out the initial scan ("which plugin libraries are loadable at all?") from the subsequent formal load and lookup of plugins for the user interface. The latter process correctly loads plugins only from the 64-bit directory, but the initial scan wrongly follows the same procedure for LADSPAs as it does for Vamp plugins and investigates both.
2. The initial plugin scan tries to load some library files that are not plugin libraries (but are supporting DLLs like FFTW). It emits errors for these, even though they were never intended to be loaded as LADSPAs.
3. One of the LADSPAs in the Audacity distribution genuinely appears to be un-loadable (? - to investigate)
4. There is no way to ignore these errors - something which one can only really do if one also has a way to review them later in case they did turn out to matter after all.