Add new comment

note that ardour embeds the LV2 GUI of triceratops (or any other LV2 plugin GUI, but only LV2) in the same window.

qtractor does not do that. instead, it splits the plugin's own GUI into one window (cf. plugin/edit...) and a generic qtractor stock UI in another (cf. plugin/properties...) which is like the one you see floating for zyn, only that it has no controls for you to tweak, just empty.

let's try inserting a triceratops instance in a qtractor MIDI track. then you'll see what i mean: you'll get a fancy GUI window (triceratops own) that probably shows up automatically as if plugin/edit... context menu is clicked, or you could get a generic dull window box (ie. plugin/properties...) full of sliders and such, where you also see a preset drop-down list at the top--that's precisely where you get the LV2 presets listing as you could see on ardour. in fact, you can interchange the presets there (pre)defined from and into ardour3 as they are part of the LV2 state world space (in your system). this applies to LV2 plugins only.

otoh. DSSI plugins are supposed to expose patch, bank/program selection through the MIDI track properties dialog--NOT the plugin's dialog, which only sets for so-called presets (nb. presets are not patches) and that i'm afraid, is bogus for a zynaddsubfx plugin instance in particular, just because it does not expose any parameter for you to aggregate in a possible set of values (aka. preset)

hth.
byee