Introduction > Different kinds of scripts

As we briefly alluded above, as of Gig Performer 4, there are several different script targets available.

Rackspace scripts

You can create individual rackspace scripts for each rackspace in a gig file. To open a rackspace script for a particular rackspace, make sure that rackspace is selected and then press CMD/Ctrl-Shift-1 or select Current Rackspace Script Editor from the Gig Performer Windows menu.

Global Rackspace script

There is a single Global Rackspace script available. The global rackspace can respond to many events including changes in rackspace, variation, songs and song parts. It can also respond to certain global events such as a notification when a gigfile has finished loading. You can open this script editor by pressign CMD/Ctrl-Shift-5 or by clicking Global Rackspace Script Editor from the Windows menu.

Song scripts

Similar to rackspace script, you can associate a song script with individual songs. Song scripts have callbacks that can be triggered when you switch from one song part to another so you can do some song specific processing. Press CMD/Ctrl-Shift-2 or click on Song Script Editor in the Windows menu when you have a song selected.

Gig file script

You can define a single "top-level" script that can be used to control Gig Performer itself. The Gig file script has some interesting "superpowers". For example, you can intercept incoming MIDI from devices, modify them, block them or even redirect them so that those events will appear to other parts of Gig Performer to have been received from different devices. The Gig file script can also respond to key sequences on your computer keyboard and used to trigger actions.

Scriptlet script

Gig Performer 4 allows you to create your own plugins to perform specialized MIDI processing. You can define parameters that can be controlled by rackspace widgets, respond to incoming MIDI events, process them and pass them on. Scriptlets are inserted into the wiring view just like any other plugin. Double-clicking on a Scriptlet block will open its plugin editor (just like any other plugin) from where you can see any scriptlet parameters you have defined. Click on the Edit Script icon (the first icon in that plugin editor window) to open the scriptlet's editor window.

Be aware however that there are some important differences between scriptlet and other scripts since scriptlets are essentially custom developed plugins that live in Gig Performer's wiring view just like any other plugin and receive MIDI Messages directly through their MIDI input port. In particular, this means that a) callbacks do not reference MIDI In blocks and b) the functions used for sending out MIDI messages (SendNow, SendLater, etc) do not require a MIDI In block as their first parameter.