Hi all, a few questions:
If I want to add or remove plugins, can this be saved as a variation or does it have to be a new rackspace?
If I make a variation, can I alter some plugin parameters/presets and save that as a new Variation that is recallable? Or must I create widgets that are tied to plugin parameters in order for variations to actually switch parameters?
Thank you
Yep. If you want to add a new plugin, you need a new rackpace.
But, you can sort of get around that by adding the plugin to the rackspace and then, using a widget, bypassing that plugin when you are not using it. So that way, variations can function as if a plugin was removed/added.[Edit: in order to avoid hanging notes, it is often better to block ānote onā messages instead of bypassing the plugin, as Paul mentions in a later comment in this thread].
One benefit of this is it reduces the number of different instances you might need of a particular plugin. Especially in the case of ram heavy plugins, this helps control ram use.
Variations allow you to change things before and after the plugin, through widgets.
You can also used widgets and variations to change sounds/presets/parameters within a plugin. But, as I understand it, this is not officially supported because it can cause instability. For example, if you use a widget to change a memory intensive preset/sound, this will take time to load. So, this could cause a problem.
If you instead use another rackspace, the developers put a lot of work into making sure enough was loaded into memory so you can seamlessly switch rackspaces, even if you are using different ram intensive plugins.
I think you always (?) need a widget if you are going to change something in variations.
I hope this is a bit helpful.
Is it common for you to bypass plugins with widgets in variations? I have avoided this for fear of maybe a plugin not activating fast enough when moved from deactivated to activated going into the variation. Iāve also wondered if notes would somehow get āstuckā if still held when a plugin goes into a deactivated state when switching variations.
From an effeciency standpoint, I see significant value in activating/deactivating plugins in variates (via widgets of course). Is this considered a safe approach?
X
I do never activate/deactivate plugins.
I use the MIDI Filter plugin and block NOTE ON messages.
And in case of demanding plugin I resample them (when possible) via the Autosampler and use Kontakt for playing.
I have to get used to doing this instead of bypassing a plugin.
If you want to reduce CPU, is there any downside of blocking the ānote onā message and bypassing the plugin? Or will that negate the benefit of blocking the ānote onā message?
But, I have to say I (too often) have issue with hanging notes that are not related to changing variations/bypass. V Collection synths often seem to be the culprit (maybe because I use them so much) (Kontakt does not seem to have this issue as often in my experience).
I was thinking it wasnāt a good strategy, but I figured someone else who had used that strategy might know more than me.
X
Honestly, CPU overhead isnāt much of an issue for me since realizing my mistake and installing the Intel version of GP 5.5 on a M1 Max MacBookā¦
On another note, are there particular Arturia plugins that seem to hang notes more than others in your experience? If so, which ones. This might help me nail down a consistent hanging note issue Iāve had for awhile.
X
Iāll try to keep track and let you know.
It dependsā¦ I actually use that technique in some cases, but only if it isnāt time critical with changing sounds.
You might get some ideas on how to avoid stuck notes and such if you have a closer look at this rackspace i made
Duplicate the rackspace (If you want to keep most of it in place, just want to make minor changes, otherwise, create a new one from scratch) add or remove plugins as desired, give it a new name and youāre good to go. You canāt add add take away plugins from variations. All plugins are in the rackspaces themselves. Variations are meant to save different states of the widgets.
As far as bypassing plugins, I do this a LOT! No issues whatsoever, but I do take precautions. I use the @David-sanās plugin persist 2 script that delays the bypasses that ensures not only a more natural way of turning off the sound, but I also turn off the note on and make sure that all note offs arrive before the bypass.
This is nice and simple. But, the downside is every time you create a new instance of the same plugin/same sound, you are increasing the amount of ram needed for the Gig file. This is particularly relevant with ram heavy plugins/sounds. (I generally do not worry about this for physically modeled sounds).
If you are always using Predictive Loading, I suppose it does not matter much.
In my case I like to have everything one big Gig File (even though I create gig files from setlists that have the setlist and all songs I play with a particular band and (usually) use them for each show). (And I do not use Predictive Loading).
So, I try to avoid duplicating ram heavy plugins/sounds in different rackspaces if I can avoid it. In some case I put them in the Global Rackspace. In other cases, I try to reuse rackspaces (bypassing plugins I do not need).
Also, there are strategies, like Kontakt purging that can reduce ram use.If I am using a Kontakt sound just on one rackspace, I try to use the purge tool.
Not so much if they use DFD playback like Kontakt, for example. So does Omnisphere, as far as I know.