please refrain to tell the world that I or qtractor are not "officially" supporting VST sub/shell plugins whatsoever just because that's dang not true.
you can read several threads on the LM fora where you'll see there's issues re the use of the vst plugin dummy scan, and for which you don't get to discover new sub/shell plugins. but that's NOT an issue to already loaded ones.
maybe tl;dr :/ you'd must realize that having the vst-dummy-scan turned off will get your qtractor sessions pretty unstable, provided you do the vst-scan at least once. if, for instance, you have one nasty VST plugin on the search path, and one example is u-he's Diva (but there are plenty more) you'll get a time-bomb ticking started... so, my suggestion is about the following: you know about some vst-shell plugins you like to insert onto your session. so be it. do that with vst-dummy-scan on. once those inserted, please save your session and turn the vst-dummy-scan back on. remember: problem only arises down-hill from vst plugin discovery. once you get your pretty session laid out, with all the vst sub/shell plugins you like around and ready to party then i'd say you won't need to vst-plugin discovery/scan ordeal any more. avoid it at all costs. you're now set to make some music, remember? all your sessions with vst sub/shell plugins will get up and loaded without issues thereafter, hopefully.
Dan,
please refrain to tell the world that I or qtractor are not "officially" supporting VST sub/shell plugins whatsoever just because that's dang not true.
you can read several threads on the LM fora where you'll see there's issues re the use of the vst plugin dummy scan, and for which you don't get to discover new sub/shell plugins. but that's NOT an issue to already loaded ones.
maybe tl;dr :/ you'd must realize that having the vst-dummy-scan turned off will get your qtractor sessions pretty unstable, provided you do the vst-scan at least once. if, for instance, you have one nasty VST plugin on the search path, and one example is u-he's Diva (but there are plenty more) you'll get a time-bomb ticking started... so, my suggestion is about the following: you know about some vst-shell plugins you like to insert onto your session. so be it. do that with vst-dummy-scan on. once those inserted, please save your session and turn the vst-dummy-scan back on. remember: problem only arises down-hill from vst plugin discovery. once you get your pretty session laid out, with all the vst sub/shell plugins you like around and ready to party then i'd say you won't need to vst-plugin discovery/scan ordeal any more. avoid it at all costs. you're now set to make some music, remember? all your sessions with vst sub/shell plugins will get up and loaded without issues thereafter, hopefully.
hth.
cheers