Before it worries you too much, DSSI support is still not complete, non-functional, nor even tested. And that applies to native DSSI plugins. That said, having DSSI-VST wrappers working is still a miss in Qtractor. ATM, you only have it on good old LADSPA and these new linux native VSTs, audio effects only.
[UPDATE] Just found a flaw on DSSI plug-in instantiation which was preventing DSSI-VST wrappers to show up. Now fixed and it also sets a new stance on the VST plug-in search path resolution:
- native Linux VST plug-ins (.so) should now be searched under the directories given on the View/Options.../Display/Plugin Paths dialog (defaults to /usr/local/lib/vst and /usr/lib/vst, or in VST_PATH environment variable)
- foreign Windows VST plug-ins (.dll), as wrapped by DSSI-VST through WINE, are found by proxy in the directories given by the VST_PATH environment variable only.
Both rules should apply, starting from todays CVS HEAD (qtractor 0.1.0.848+)
Before it worries you too much, DSSI support is still not complete, non-functional, nor even tested. And that applies to native DSSI plugins. That said, having DSSI-VST wrappers working is still a miss in Qtractor. ATM, you only have it on good old LADSPA and these new linux native VSTs, audio effects only.
[UPDATE] Just found a flaw on DSSI plug-in instantiation which was preventing DSSI-VST wrappers to show up. Now fixed and it also sets a new stance on the VST plug-in search path resolution:
- native Linux VST plug-ins (.so) should now be searched under the directories given on the View/Options.../Display/Plugin Paths dialog (defaults to
/usr/local/lib/vstand/usr/lib/vst, or inVST_PATHenvironment variable)- foreign Windows VST plug-ins (.dll), as wrapped by DSSI-VST through WINE, are found by proxy in the directories given by the
VST_PATHenvironment variable only.Both rules should apply, starting from todays CVS HEAD (qtractor 0.1.0.848+)
Byee
--
rncbc aka Rui Nuno Capela