Auto-sleep on MIDI unactivity

[salomao]

I use the KORG Triton Extreme plugin in most of my songs/rackspaces. So, in order to save system resources (avoiding to load countless instances of the TE plugin) I placed in in Global Rackspace.

However, the TE plugin is a hungry CPU eater. For the songs I don’t use it at all I can set it as inactive/bypassed (which is easily doable using a simple widget to bypass it when I don’t need it at all). However, in some songs, I need the TE plugin but only to play a few notes from time to time. I would like to have the plugin active when I need to play it, but need it to by bypassed when the keyboard region where it is placed is not being used.

Plugin Persis 2.0 has that ability. I can set to ON the feature “auto-sleep on MIDI unactivity).

However, for some reasons I couldn’t figure out, I cant use Plugin Persist 2.0 on my TE plugin placed in Global Rackspace as it messes up with another script created by @LeeHarvey to control the program/combination changes on my TE plugin. When I use both scripts, I get several bugs which lead me to serious embarrassments in live performance, either because the TE controller script fails randomly not changing the program as expected or because Plugin Persist 2.0 hangs and get stuck ON and then the TE plugin will be always ON.

To be honest, the “auto-sleep on MIDI unactivity” was the main and only reason I was using PP 2.0 so, to reach my point here, I would like to know if is there a chance I can have a script that ONLY uses the “auto-sleep on MIDI unactivity” as seen in Plugin Persis 2.0.

I know nothing about scripting, so If my wish is achievable, I would appreciate the help of anyone who can be available to do so.

Thank you all for your attention and help.

[edm11]

I don’t think Plugin Persist 2.0 will work if your plugin is in the Global rackspace.
This has been discussed in another thread:

PluginPersist 2.0 not working on GLOBAL Rackspace?

There is a kontakt brass patch that I use often on my rackspaces, so IIplaced it in GLOBAL Rackspace and from then on I use it in the rackspaces I need. In the various rackspaces, I have been successfully using the “PluginPersist 2.0” scriptlet, however, in GLOBAL Rackspace it apparently does not work. I’ve already reviewed all the configurations, more than once, I’ve selected a different Local GP controller (110) than the one I use in the individual rackspaces, but it doesn’t work! What am I …

[edm11]

You could try this AutoBypass scriptlet:

AutoBypass scriptlet

This is a modification of a great scriplet created by @David-san that can be used to automatically bypass a plugin after a short (or zero) time delay when no MIDI activity is detected. A little bit of work is required to set it up Connect a MIDI In block to an AutoBypass scriptlet and then connect the AutoBypass scriptlet to your plugin [screenshot_6902] Create two buttons (e.g. LEDs) and put them in the same linked widget group [screenshot_6903] Map one of the buttons to the Plugin …

[David-san]

You sent me a PM about this and I requested the smallest possible gig file which reproduces your issue using only GP instrument plugins. It would help if you could provide one and even post it here or in your other topic (mentioned by @edm11).

In your other topic, you are using the MIDI In Omni block which is never a good choice for a production gig file. Are you sure there is no MIDI activity in the Plugin Persist 2.0 Scriptlet? Did you use a GP MIDI monitor there? Are you sure there is never a missing Note Off because of a bypassed or missing MIDI In block?

[salomao]

@David-san, I am currently on tour and have no chances to make anything right now.
As soon as I can I will try to do what you asked me.
For now, I just removed PP 2.0 and am trying to deal with the CPU usage.

I am immensely grateful to all those who are helping me.