Like pretty much everything I use in performance, my Supa-Trigga lives in a Rack. There are two particular reasons for this.
The first reason is that SupaTrigga is a buffer-based effect, meaning that it has to have a bit of audio stored in memory before it can begin processing it. This means that it won’t take effect right away if you simply turn it on and off using the device activator.
Instead, there will be a gap of silence as the buffer is filled.
This same problem occurs when using the chain selector, as discussed in Mapping The Activator. The solution in this case is essentially the same. SupaTrigga is placed into a rack with two chains, an empty one for the dry signal and another for the effect. Then, the chain mute switches are toggled back and forth using a macro knob.
This way, the effect is running all the time and takes effect the instant it’s un-muted.
Notice that next to the Trigga!! macro, there’s also one called granularity. This knob doesn’t get used in performance – it’s here to work around a bug. I found that when loading my set, the SupaTrigga would not recall the granularity parameter correctly (it would be set to 4 slices instead of 16).
By mapping this parameter to a macro knob, the rack forces the parameter to it’s right value when loaded. (Don’t forget that to map macros for AUs and VSTs you’ll need to Configure Parameters for the plug-in first.)
