Learning a MIDI event to a text label widget

[David-san]

@Solomon

What is the purpose of being able to assign a MIDI control to a text label?

I have a control surface with touch sensitive faders and I want to know via a GPScript callback when the user touch the faders (e.g. to display a submix name on the control surface LCD when the fader is touched). So, as I don’t want to see a button or switch widget for this, I use the TextLabel Widgets which numbers the slices of the mixer panel which represents the control surface.

A more advanced use is to MIDI learn a TextLabel Widget to a Local GP Port message generated by a Scriptlet (it is away to « bridge » a Scriptlet MIDI output to a plugin parameter) like in the PluginPersist scriptlet:

[Gig] Plugin Persist (or Patch Persist for Variations)

Many Gig Performer users build rackspaces in which they use button widgets to bypass/unbypass instrument plugins differently in the variations. With that approach it can be unsafe to change the variations while playing, i.e. the benefit of patch persist is lost. Note: there is an improved version of this scriptlet, which you can download here. This gig file includes a scriptlet which simulates the Patch Persist feature for instrument plugins which are bypassed when switching to another variati…

Example of using the transparency to display which Pad is triggered ([Gig] NotesConverter for MIDI pads):

NotesConverter Scriptlet for Gig Performer: a plugin for MIDI pads