Non-usable plugins show up in list

[CoDEmanX]

Building on Windows worked fine for me and in general the plugin also does - kudos!

One thing I noticed however, is that you can pick VST plugins, which are not suitable. I believe the general rule here is that VST filters work fine, whereas VSTis (virtual instruments) do not, because they require MIDI input to synthesize some output.

If I select such a plugin, e.g. Toxic Biohazard, there is no audio signal on that source anymore until I change it to a filter plugin.

If there is any way to do it, this plugin should filter out non-functional VSTi plugins and only present the ones that actually work.

[c3r1c3]

Hmm... that would require looking at the VST type (types are defined in the header) and filtering those out from display.

I think the MrsWatson code has an example of how to do that.

[c3r1c3]

One issue with doing 'deep' scanning of VST plugins is that some tend to crash the program scanning. This means lots of trouble for people starting up OBS, and also requires OBS to keep some type of 'registry' of plugins scanned/changed/not scanned/that cause OBS to crash.

Not saying it isn't worthwhile, or that it can't be done, but there are currently bigger fish to fry.