MIDI FX

The MIDI FX menu in T1 Config is where you configure how incoming MIDI is routed and filtered before it is used by the T1.
Use it to:
- choose how incoming MIDI is routed to tracks
- limit MIDI input to the currently active track when needed
- select a fixed MIDI input channel
- pass incoming Control Change and Pitch Bend messages through to the output
Routing
The Routing setting determines how incoming MIDI is assigned to tracks.
Available modes are:
- omni
- same
- fixed
Omni
In omni mode, incoming MIDI is accepted broadly rather than being limited to one fixed channel-to-track path.
Use this when you want a more open MIDI input workflow.
Same
In same mode, MIDI input follows a same-channel style routing approach.
Use this when you want incoming MIDI to stay aligned with matching channel behavior.
Fixed
In fixed mode, MIDI FX uses a specific MIDI input channel that you choose manually.
When this mode is selected, the MIDI input channel control becomes relevant.
Use this when you want predictable input from one dedicated MIDI channel.
MIDI Input Channel
The MIDI input channel setting selects which channel is used when Routing is set to fixed.
Available values are:
- 1 to 16
Choose the channel that matches the controller, sequencer, or other MIDI source you want to use with MIDI FX.
If incoming MIDI is not behaving as expected in fixed mode, first verify that the external device is transmitting on the same channel selected here.
Active Track Filter
The Active track filter setting determines whether only the currently active track or tracks should receive MIDI input.
When enabled:
- only the active track selection receives MIDI input
When disabled:
- MIDI input follows the current routing mode without that extra restriction
This is useful when you want tighter control while editing or performing, especially if you do not want incoming notes to affect other tracks.
Control Change / Pitch Bend Thru
The Control change / Pitch bend thru setting determines whether incoming Control Change and Pitch Bend messages are passed through to the output.
When enabled:
- incoming Control Change messages are passed through
- incoming Pitch Bend messages are passed through
When disabled:
- those messages are not forwarded onward through this path
Use this when you want the T1 to preserve expressive controller data for downstream MIDI devices.
Practical Examples
Playing a Single Track from One Controller
A focused setup might use:
- Routing set to fixed
- MIDI input channel set to the controller’s transmit channel
- Active track filter enabled
This makes it easier to direct performance input only where you want it.
Matching a Channel-Based Setup
A channel-oriented setup might use:
- Routing set to same
- Active track filter disabled
This is useful when the rest of your MIDI rig already depends on channel-based organization.
Passing Expressive Data to External Gear
If you want controller gestures to continue downstream, use:
- Control change / Pitch bend thru enabled
This can help preserve modulation wheel, knobs, sliders, or bend gestures in a larger MIDI chain.
Best Practices
- Use fixed routing when you want the most predictable input behavior
- Enable Active track filter when you want to avoid affecting non-active tracks
- Double-check the selected input channel when using fixed mode
- Enable Control change / Pitch bend thru only when you want those messages forwarded onward
- Test routing behavior with a known MIDI controller before using it in a larger setup