TriggerBox is a creative MIDI-effect which interprets note-on, note-off, and continuous-controller (CC) events in unique ways. It was designed primarily to allow combining multiple Guru Sampler instances to create realistic acoustic-piano performances (see Example below), but it's generic enough to support other, more creative uses as well.
NOTE: TriggerBox has been designed for highly specific uses. If all you need is a basic MIDI delay, use JitterBox.
TriggerBox has been designed primarily for tracking the state of the MIDI sustain-pedal (CC#64), to enable use of multiple Guru Sampler layers to create realistic piano sounds. You can also use it experimentally with other MIDI CC's, but you are basically “on your own” in doing so.
TriggerBox is a MIDI-effect. It monitors the stream of incoming MIDI event data, and can modify it in certain ways. TriggerBox can do two very specific things, which are unique to this plug-in:
As mentioned above, TriggerBox has been designed primarily for tracking the state of the MIDI sustain-pedal (CC#64). The main things TriggerBox can do are:
When you first open TriggerBox, you will see a simplified GUI like this:
The CC in range indicator at the very top-right of the TriggerBox GUI lights up when TriggerBox considers the selected CC to be “in range”. Of course, a newly-created TriggerBox instance cannot know the “current value” of the MIDI CC until it actually receives a CC message with the appropriate CC number. Therefore, the CC in range indicator also acts as a button—you can click it to toggle whether TriggerBox should consider the current value in- or out-of-range.
TriggerBox supports named presets. The name of the currently-loaded preset (or “None”, if no preset has yet been loaded) is shown in large white text at the top.
Clicking the Load Preset button pops up a menu of available presets; click on any preset to load it. Note that TriggerBox's presets are simply .xml files in a folder called TriggerBox Presets, which you will find in the Presets sub-folder of the main Unify data folder.
If you wish to add your own new preset to the list, click the Save Preset… button. Unify will present a standard file-save dialog, which should already be prepared to save a new .xml file into the TriggerBox Presets folder. Simply enter a name for your new preset (you don't have to add “.xml” at the end) and click Save.
You should always save new TriggerBox presets somewhere under the TriggerBox Presets folder. You may create sub-folders if you wish; these will become sub-menus in the pop-up presets menu which appears when you click Load Preset.
Clicking the Show Details button “opens” the full GUI, which looks like this:
The full GUI includes everything in the simplified GUI, with numerous additional controls below. These additional controls are divided into five sections labeled Note Triggering, Velocity Curve, Input Notes, When CC Enters Range, and When CC Exits Range, which are discussed separately below.
The controls in the Note Triggering and Input Notes sections affect how MIDI note-on events received by the plug-in (e.g., notes you play on the keyboard) trigger corresponding output notes. The Note Triggering controls specifically affect which MIDI CC is used to govern triggering, and also the probability that a given input note-on event will trigger a corresponding output note.
Clicking the MIDI CC button pops up a menu of all 128 MIDI CC numbers, with their standard functional names where appropriate. Choose from this menu to select which CC number TriggerBox should monitor to affect note triggering.
Below this button are two number-boxes which allow you to specify an exact range of values of the selected CC to watch for. As will be explained, TriggerBox can be set up to respond differently, based on whether the most-recently seen value of the selected CC is within or outside the specified range.
Just to the right of the two number-boxes is a small green in-range indicator, which lights up when a MIDI CC message is received which matches the selected CC number AND whose value is in the specified range.
The Pass CC to output checkbox allows you to specify if the monitored CC messages are passed through to the plug-in to downstream plug-ins or suppressed. The default behavior is to suppress them.
The Probability knob at the right of the Note Triggering section controls how often input note-events trigger corresponding output notes. The knob is calibrated from 0% to 100%. For every MIDI note-on event, TriggerBox will randomly choose whether or not to trigger a corresponding output note, and will do so for the specified percentage of input-events. The default is 100%, so there is no randomness at all; every input note-on event will trigger a corresponding output event (provided this is what the Input Notes controls specify; see below). Reduce this to 25%, and only one input note in every four will trigger an output note.
The velocity graph works just like the velocity graph controls on Unify's INST and MIDI layers. Click on the graph to pop-up a velocity-curve editor to adjust the curve shape. The default shape is an “identity function” which does not change velocity values at all.
The first two pop-up menus on the left effectively “spell out” whether or not, and if so how, output notes are triggered. Options on the upper menu are:
Options on the middle menu are:
The third menu will only be enabled when the first menu is set to Note-OFF triggers output note. Otherwise, it will be greyed-out and set to “Use Input Note-ON velocity”.
When input note-OFF events are used to trigger output notes, there are two possible options for setting the output note velocity. The third menu allows you to choose:
The two knobs at the right of the Input Notes section allow you to adjust the start delay and duration (aka “gate time”) of generated output notes. Each has a bpm checkbox to allow specifying tempo-based durations (triplet 64th up to whole-note) instead of times in milliseconds (0 to 1000).
These controls work quite similarly to the delay-time controls in Omega Delay.
TriggerBox can also trigger output notes when the selected MIDI CC enters and/or exits the specified value-range. This functionality is entirely separate from input note-triggering as described above.
The two sections at the bottom of the GUI are substantially identical, and so are described together here. The only difference is that the section on the left applies when the specified CC enters the range, and the one on the right applies when it goes out of range.
The large button at the top of each section pops up a menu with four choices, as follows:
The two Note boxes work very similarly to the note-boxes in Unify's INST and MIDI layers. Note you can right-click (or hold down CTRL and left-click) a note box to put it into “MIDI learn” mode:
Note another useful trick for finding the right note-number is to simply bypass the TriggerBox plug-in temporarily, so you can simply play different notes until you find the one you want, then un-bypass it and set the note box as described above.
The “Send note-ON” and “Send note-OFF” options are treated a bit specially, to avoid “stuck” notes. Whenever you set either the “enter” or “exit” sections to “Send Note-ON”, the opposite event will automatically generate a corresponding MIDI note-OFF message, before performing the selected function. This may not be sufficient to eliminate stuck notes entirely; use the MIDI Panic button (exclamation-mark icon) at the bottom of the Unify GUI if necessary.
This section is a bit of a placeholder. I will update it to reflect whatever demo patches you create.
The default settings in TriggerBox have been chosen to be very close to what is needed to set up a two-layer patch like the one illustrated below, where
To download this patch, click on this link: triggerbox_demo_patch.zip
The TriggerBox instance on the INST1 (pedal UP) layer is set as shown below.
The TriggerBox instance on the INST2 (pedal DOWN) layer is set as shown below.