a dummy-plugin is kind of a a stub for each one of the library shared objects files (.so) that are found across the search path scan; for each library file that is found, it makes it a generic so called "dummy-plugin" instance filename, each one faking 1 MIDI input and stereo (2 channels) audio inputs/outputs .danboid wrote:What is a dummy VST plugin? I presume its a different thing from a VST plugin that contains sub-plugins but maybe I'm wrong? Is a sub-plugin a dummy plugin?
How can we scan for and detect dummy plugins or plugins that may cause issues when we disable the dummy plugin scanning?
Will you not officially support sub-plugins in qtractor?
this dummy scan is/was the safest way to scan for VST plugins that doesn't cope with actual open/load and close/unload in quick succession (aka. real non-dummy scan process); historically, many JUCE based VSTs were prone to crash and lock-up the host that eg. doesn't open their GUI editor immediately on load, something that qtractor doesn't do ever, especially while scanning on discovery--this might not be an issue any more for most recent JUCE-plugin builds, but it takes just one old leftover still around to doom and compromise it all.
now, VST-shell (sub-)plugins can only be discovered if its library object (.so) is actually loaded up and gone through its run-time programmatic interface, something that is simply skipped while on a dummy-scan, as explained before.
besides, the dummy-scan is just an user safety option rather than an official stance against VST sub-plugins or whatever.
hth.
cheers