I just tried the Arturia Mellotron — it starts at about 4% and when you play chords it goes up to about 8% (on my Mac) but as soon as I release all notes and sound stops, it goes back down to 4%
Modartt’s Pianoteq is another great example
Kontakt, when it’s not playing, basically goes down to 0%
Odd. When i loaded various arturia plugins, I didn’t even play a single note. Just loaded them and CPU went up. Then only when i bypassed them went back down.
Are you looking at GP’s Audio Processing CPU or are you looking at your operating system CPU usage?
Gig performer’s. Is that what you’re looking at? When you load arturia plugins and they’re active but you are not playing does your CPU not go up at all compared to before you loaded the plugins??
Curiosity question: What is the “Gig Performer Plugin Block”?
Take this 
Got it…just hadn’t seen it described in that term before.
Just wanted to clarify that Arturia does release CPU load when not producing audio. The slight confusion (probably on my part) was regarding CPU usage increase from loading the plugin itself (without actually playing sounds) vs the CPU increase after playing sounds. So the CPU increase that come from loading the plugin goes away by bypassing the plugin. The CPU increase that comes from playing notes goes away automatically once notes are no longer being played. Those are two different causes of CPU increase.
@David-san I just wanted to thank you for the “plugin persist” scriplet. It works amazingly! What an upgrade from using simply NOTE ON filtering (freeing up CPU) and fixes all the stuck on note issues one might have by “manually” bypassing plugins. Thanks!
Thanks for the kind words, I really appreciate your feedback. Happy it works for you.
Some unexpected behavior that I need your help @David-san to fix please. My guitar plugin is in the regular rackspaces and I have my synth plugins loaded into the global rackspace with widgets in the reg rackspace controlling/linked to the switch that controls the plugin persist. When switching between variations, the plugin persist bypass works great! Whatever the variations turn on and off are followed exactly in the global rackspace. However, when switching rackspaces, the plugins that were last active in the rackspace/variation I am leaving, do not turn off (bypass) in the global RS, even though in the new rackspace I have different plugins activated. The new rackspace plugins do activate, but the one I’m exiting do not turn off (bypass). Obviously what I’d like is only for the plugins to be active in the rackspace’s current variation.
Currently I have about 12 plugins loaded in total and with your awesome script, only a couple are ever active at the same time, so its possible to have all these loaded without eating up any additional CPU. I understand your script was written for all these plugins be in a regual rackspace, but it works so perfectly for me in the global. What seems to be needed is when switching rackspaces (exiting a rackspace) a bypass ALL would be sent. I know entering into the new and exiting the old rackspace is simultaneous so is that even possible?
Couldn’t you just make sure all 12 plugins used in the global rackspace have a bypass widget in every local rackspace? So when you move to the new rackspace, the new one would set the required bypass widgets.
I was literally just thinking that as a possible workaround. Yes, that should work! I will live with that if there is no way to address that with scripting, which would be more elegant than having about 10 extra dummy widgets that are otherwise not needed, but for sure, that’s a small price to pay. I can make them very small and out of the way… 
So yeah, that works fine. There is no way to copy and past widgets with the plugins/parameters info also copying, is there?
With all the new features offered in GP4, we will become greedy and very demanding… Developers will be overwhelmed with requests!
Personally I try to find solutions by myself before asking firmly for help, but it’s not easy… GP4 is too rich in possibilities and I am too skills-poor 
I am afraid that @rank13 is right, your use case necessitates to define the bypass state of each of the « global plugins » for each rackspace/variation.
It is always good to try to find solutions by yourself, as it improves your skills, but the GP community is also here to help and discuss things. Asking questions or sharing solutions is always interesting 
Right makes sense. Thanks
