Patch Persist VS Mute Note On Messages

[zfw]

Hello,

To prevent stuck notes I’ve been adding the MIDI Filter plugin between my MIDI In block and Synth VST, and muting note-on messages whenever I’m done using the synth. Previously, when a song finished using a particular synth, I would simply bypass the synth. But stuck notes would happen and I found muting note on messages worked better to effectively “turn off” a synth.

The downside to this is that it’s a little more programming, and the VST’s are remain on and take up CPU. If I reverted to my old method of simply bypassing plugins when I’m done using AND engaging patch persist, is it the same exact thing?

What is the best practice for this scenario?

[schamass]

Have a look at this example… could be what you want. May eventually need a little tweaking though.
But the general functionality should fit.

2 Keyboards / 4 Plugins / Auto Bypass (V5)

This rackspace is designed to use two keyboards or one split keyboard (for which is set up now) to vary between two sounds (totals 4 plugins involved) for each LOWER and UPPER keys. Which one of the two plugins is enabled can be set with an “ACTIVE” pad. So all in all it just enables you to set one, two or no sound for each keyrange/keyboard, and the unused plugins will be bypassed to save resources. The clue is that i not only used MIDI-filters to avoid stuck notes because of “missing” NOTE-…

[David-san]

As you mentioned patch persist, with patch persist you don’t need to care about anything, GP will do the job for you when switching between Rackspaces.

For switching between variation with a similar behavior, there is this Scriptlet:

[Gig] Plugin Persist 2.0

This gig file contains the Plugin Persist 2.0 Scriptlet, the major overhaul of the Plugin Persist Scriptlet now with auto-sleep and fade out features. [Plugin-Persist-v2-by-David-san] Introduction: Many Gig Performer users build rackspaces in which they use button widgets to bypass/unbypass instrument plugins in the variations. As plugins themselves may not behave as you would expect when they are bypassed or unbypassed, this scriptlet adds more stability if a plugin is poorly implemented. N…

Tell us what works best for you.

[zfw]

Thanks for sharing @David-san. I just explored the scriptlet and definitely see it’s benefit, and how effective it is in saving CPU. I have a slightly different need that I’m wondering if you can help me with.

For each song, I use one rackspace and variations for each song part. For Variation A, I use Synth A and moving forward in the song, for variation B I want to (1) play the same exact keyboard, (2) Activate Synth B and Deactivate Synth A (3) avoid stuck notes.

Assigning widgets to MIDI filters and blocking note-on messages when I switch variations seems to do the trick but it doesn’t take care of bypassing unused VSTs and saving CPU.

I suppose I could simultaneously block note-on messages and bypass unused VSTs each time I change variations, but I’m hoping for a simpler and quicker-to-program solution. Not sure if that’s possible though.

[David-san]

@zfw

For each song, I use one rackspace and variations for each song part. For Variation A, I use Synth A and moving forward in the song, for variation B I want to (1) play the same exact keyboard, (2) Activate Synth B and Deactivate Synth A (3) avoid stuck notes.

Well, that’s exactly what the Plugin Persist Scritptlet allows… What did I miss here?… Or perhaps you missed this in the Plugin Persist 2 instructions:

@npudar

insert any GP switch widget and assign it to the Plugin Persist “enable plugin” parameter

But, you could also simply use two Rackspaces with Patch Persist and it would do the job.

[zfw]

From experimenting with the scriptlet, it seemed as tho the auto bypass engages whenever it does not receive MIDI. But if I continue to use the same keyboard, wouldn’t that just de-bypass the VST? How do I auto bypass Synth A and move onto play Synth B, without de-bypassing Synth A?

[David-san]

@zfw

the auto bypass engages whenever it does not receive MIDI

Yes, if you use it - it is optional - it works like that.

@zfw

But if I continue to use the same keyboard, wouldn’t that just de-bypass the VST?

If it is bypassed by the auto bypass option and you play again it will unbypass the plugin.

@zfw

How do I auto bypass Synth A and move onto play Synth B, without de-bypassing Synth A?

Did you read my previous post regarding the Plugin Persist 2 instructions ? And did you test the demo gig file of Plugin Persist 2 ? Using the « enable plugin » parameter mapped to a widget, you can… well… enable or disable a plugin. If you need it in a variation, you enable it, if you don’t need it, you disable it.