When referring to VST plugins, Qtractor do search for Linux native VST plugins that have been compiled and built from source on Linux with either the official Steinberg VST-SDK headers or the VeSTige header. These plugins come in the form of ELF shared object files (.so).
You're probably trying to look after Windows VSTs (.dll) which are only made available by proxy ie. DSSI-VST through WINE. That means that all regular Windows VST plugins will appear as DSSI plugins, never as VST.
One more thing you might need to know, is that the path for the dssi-vst scanner to search for those .dll's is exclusively given by the VST_PATH environment variable. Again, Linux native VSTs are scanned under default search path /usr/local/lib/vst:/usr/lib/vst (32bit) or /usr/local/lib64/vst:/usr/lib64/vst (64bit) or whatever you set in View/Options.../Plugins configuration.
When referring to VST plugins, Qtractor do search for Linux native VST plugins that have been compiled and built from source on Linux with either the official Steinberg VST-SDK headers or the VeSTige header. These plugins come in the form of ELF shared object files (.so).
You're probably trying to look after Windows VSTs (.dll) which are only made available by proxy ie. DSSI-VST through WINE. That means that all regular Windows VST plugins will appear as DSSI plugins, never as VST.
One more thing you might need to know, is that the path for the dssi-vst scanner to search for those .dll's is exclusively given by the VST_PATH environment variable. Again, Linux native VSTs are scanned under default search path
/usr/local/lib/vst:/usr/lib/vst(32bit) or/usr/local/lib64/vst:/usr/lib64/vst(64bit) or whatever you set in View/Options.../Plugins configuration.HTH