Scanning of VST's

[curlymorphic]

Currently we do very little to help our users when it comes to loading vst's. In Vestige, you are simply presented with a file dialog

When opening as an effect, it is a little better, but really just a list of dll's

This is prone to error, Instrument and effects are mixed together, but only one type is usable, there could be midi plugins, or the dll's could not be vst's.

It is common practice for Daws to scan vst folders. cataloging and deciding where these can be used.
The user is then presented with a list of suitable choices. When loading effects, the list of vst's would be filtered, and a similar styled list presented in vestige.

NOTE: Some related ideas were discussed in this duplicate issue: #4907

[Em-Lopez]

ALSO, on Windows 10, it seems like LMMS does not search for VSTs recursively.
For example, in a folder structure like this:
.../VSTs/
...VSTs/MidSideMangler.dll
...VSTs/G-Clip/
...VSTs/G-Clip/GClip.dll
-MidSideMangler will load, but GClip will not load because it is in subfolder.
When I changed it to this:
...VSTs/
...VSTs/MidSideMangler/
...VSTs/MidSideMangler/MidSideMangler.dll
...VSTs/GClip.dll
-GClip did load, but MidSideMangler did not!
This demonstrates that LMMS does not have the capability to search recursively through folders for VSTs. Which kinda sucks.

I was able to work around this by making symlinks! But alas, that is very bad...

[Spekular]

Closing and consolidating into #5433