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. All controllers are supported except 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.
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.
Note Velocity EditorThe editor that appears by default actually doesn't control a MIDI controller but note velocities instead. Note velocities are represented by vertical bars which can be moved up or down with the mouse. A halo appears around the corresponding note in the pianoroll/score/drum editor so you can easily see which note the bar belongs to.
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.
Note Velocity Editor
All controller editors use dots to represent the controller value. They work just like Automated Fader effects.
The Pitch editor features a small button labeled R in the bottom left corner. It pops up a window which lets you change the pitch bend range. Valid values are 0..24 semitones. "0" prevents MTS from sending pitchbend range messages, you can use this if these messages interfere with a plugin's MIDI implementation.
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 plugins may not support changing the pitch bend range.