Qtractor banks (lv2,vst)

in qtractor you can have access to custom presets from the plugin properties dialog aka. generic stock plugin UI. there you have all the necessary controls in the upper left side of the generic plugin window.

however there are some differences whether it applies to a LV2 or a VST plugin, being the most notable the following:

• LV2 plugins: the named preset is a genuine LV2 state preset which is implicitly stored on the file-system (default is ~/.lv2) under the proper LV2 spec. therefore you may see that some plugins already provide there their so called "factory presets" that comes with installation;

• VST presets (and any other but LV2): the preset names you may define here are private to qtractor, depending on each plugin implementation, these presets can be mapped and stored to qtractor's configuration and/or the general file-system, on a preset file and name at your discretion. this preset file is specific to qtractor and usually goes with the .qtx suffix on its file-name.

  note that the initial preset drop-down list is of course empty because of that custom, private qtractor designation, so you won't find any "factory presets" here--you have to set up your own;

  and finally, at the time of this writing, current git head (master branch; qtractor v0.7.1.8+), already has support for loading and saving, to and from .fxp/.fxb files--of course that applies to VST plugins only.

hth.
cheers

re. but I meant the track properties.

on the track properties you have access to MIDI instrument definitions, banks and respective programs (aka. patches).

currently, on LV2 spec at least, this bank/program concept is entirely undefined and void--to speak to the truth, is not there yet and probably won't any time soon. so scrap that idea for LV2 plugins for the time being. (on a side-note kind of rant: LV2 might brag it's an extensible standard but it just didn't extend over there yet. well, this is not completely true, as there was--but still is in effect on qtractor at least--a so called lv2_programs extension that provides an equivalent interface, but it fell apart on breaking the "law"of the strict LV2 specification and so, it was even dropped by its original proponent and author. true story:))

however, VST plugins (and DSSI tbh.) are a complete different story: they all have this patch/bank/programs selection interface from within its old, stringent unflexible spec. sorry for too many adjectives, but truth is that a late 90s tech is still making strides over this 2nd decade of the XXI century.

you see, now that qtractor has this .fxp/.fxb files support, you can take hold of the several bank/patches shared out there in the interwebs for your VST plugin pleasure. maybe kvraudio.com is the place to first look after for all your VST goodies, probably you already know that for granted--i know this just because i'm having a plenty of fun with a lot of Obxd .fxb grabs... i'm sure there are some for TALNoizeMak3r as well. ;)

hth.
cheers