Vst preset number stored in rack panel
There's different levels for preset manager,
Do you use the rack presets or your patch presets ?
and all Vst don't react the same, which one do you use ?
Do you use the rack presets or your patch presets ?
and all Vst don't react the same, which one do you use ?
I've tested it with 2CAudio Aether, Uhbik and Soundtoys,
ok,
so you can test to add an array module (display or set) this way before saving your presets:

so you can test to add an array module (display or set) this way before saving your presets:

yeah !
so, in case of multiple VSTs in the same strip, should I connect all of them to a single array ?
so, in case of multiple VSTs in the same strip, should I connect all of them to a single array ?
no, the array correspond to all the parameters of each plugin, so you need one by plugin.
Note that you need to create the array from the params output, then link to the input.
Note also that some plugin don't need this, and some plugin don't create the correct array.
Note that you need to create the array from the params output, then link to the input.
Note also that some plugin don't need this, and some plugin don't create the correct array.
Another point is that I see the presets are setting some of the strip's settings as volume, bypass and so on.
Is there any chance I can decide which information and setting to save into the preset and what no ?
Is there any chance I can decide which information and setting to save into the preset and what no ?
I'm sorry but it looks like this is not the kind of solution I was looking for.
In fact, each time I save a preset on the strip all audio settings are stored, so I cannot use the preset slot just to save Vsts' algorithms;
Vsts' interface visual position is saved as well. Violent;
Having multiple Vsts in the same strip makes the situation crazy to manage. In fact, each time I tweak a single Vst algorithm and want to update the preset I have to check all the situation is right. Not having the chance to discriminate what gets stored and what no leaves the area too wide to manage.
Are there any possible different solutions available ?
In fact, each time I save a preset on the strip all audio settings are stored, so I cannot use the preset slot just to save Vsts' algorithms;
Vsts' interface visual position is saved as well. Violent;
Having multiple Vsts in the same strip makes the situation crazy to manage. In fact, each time I tweak a single Vst algorithm and want to update the preset I have to check all the situation is right. Not having the chance to discriminate what gets stored and what no leaves the area too wide to manage.
Are there any possible different solutions available ?
most items like faders, swich, mixer ect have a "saved in preset option' on right tab (i icon) when you clic on them
Who is online
Users browsing this forum: No registered users and 29 guests
