MIDI instruments can use controller events to alter the sound they generate. A track editor's CONTR button opens/closes the Controller Editor. The editors appear as tabs, which can be added or removed using the VIEW button.
Note: the controller editor's Undo/Redo buttons do exactly the same as the main editor's, ie. both work on both note and controller edits.
The Mode buttons in the bottom-left corner offer Bar mode, to move bars up and down, and Draw mode, to draw a curve to which the bars will be adjusted.
A similar 'Note Off Velocity' editor is available as well.
All controller editors use dots to represent the controller value. They work just like Automated Fader effects.
The VIEW menu lists pitch bend, aftertouch and all MIDI controllers except for the data entry and RPN controllers (#5, #38 and #96...101).
Tip: in MultitrackStudio Instruments and External MIDI Instrument windows you can rightclick a control to make the corresponding controller editor visible.
Editors are available for NRPN parameters too.
External MIDI Instruments won't pick up the new value until the transport is restarted. Other instruments will pick up the new value when a pitch bend event appears.
Note: External MIDI Instruments and VSTi / AUi / LV2i plugins may not support changing the pitch bend range.
The picture below shows per-note pitch bend for note C5. The view changes automatically when a note is selected: if you click a D4 in the pianoroll the per-note controller editor switches to D4 for example. Alternatively you can click the down arrow on the tab below the editor and pick a note from the list.
All editors update the per-note controllers automatically: whenever notes are moved, deleted etc. the associated per-note controls are updated.
The per-note pitch bend editor has a pitch bend range setting, just like the channel pitch bend editor. This value is the same for all notes. It defaults to 48 semitones, which is the default value MPE uses.
The EDIT button pops up a list of all SysEx messages. You can modify them or add new ones. SysEx messages always start with F0 and end with F7.
Note: SysEx events aren't tied to a MIDI channel. If a certain SysEx does contain a channel field you have to update it manually if you change the track's MIDI channel in the External MIDI Instrument window.
Tip: make sure messages like "XG On" are at position 0 (the first beat of the first bar). This allows Export MIDI Tracks to put it before any other messages.
The SysEx editor also supports "Sequencer specific" meta events. These events start with FF7F. They'll be saved in (exported) MIDI files. They won't be sent to MIDI instruments (the MIDI specs don't allow for that).