M9 Docs   MIDI Input Routing

A MuLab project can contain hundreds, even thousands of plugin modules.
When MuLab receives MIDI input it uses the MIDI Input Channel Target map to define the target module the MIDI input is sent to.

There are several different options, for example:

  • Map all MIDI input to the event input module in the main project modular area
  • Map all MIDI input to the module you're currently working with (= Focused Module)
  • Map MIDI input channel 1 to module X, channel 2 to module Y, channel 3 to module Z, etc...
  • ...
This behavior is fully customizable via the Project menu -> MIDI Input Channel Targets.
See details below.

Explained: Focused Module and Focused Channel

To understand how the MIDI Input Channel Targets map works, lets first see what "Focused Module" and "Focused Channel" means.

Each project keeps track of the Focused Module.
That's the plugin module you're currently working with.
For example, when clicking a track or rack, MuLab will set the Focused Module to that track module or rack so that you can instantly play that module from your MIDI keyboard.

For each plugin module MuLab also keeps track of the Focused Channel which is the MIDI channel you last played on.
Imagine you have 4 tracks routed to a single instance of module X, track 1 to channel 1, track 2 to channel 2 etc.
When you select track 1, module X is focused on channel 1. So now channel 1 is the focused channel for module X.
When you select track 3, module X still is focused, but now channel 3 is the focused channel for module X.

MIDI Input Channel Targets

Using this dialog panel you can define for each incoming MIDI channel which target module is to be played.
This allows you to make flexible MIDI setups using 2 or more MIDI keyboards and/or controllers.

When target module is set to 'Focused Module', then that MIDI input channel will play the module that is currently focused.
When target channel is set to 'Focused Channel', then that MIDI input channel will play on the focused MIDI channel of the target module for that MIDI input channel.
You can also set an input channel to play a specific module and/or channel.

Via the Options button there are several functions to speed up setting up this map.

Automatic MIDI Input Focus

When this option is switched on MuLab will automatically set the Focused Module to the most relevant module you're working with in the GUI.
Often this is the most easy option but there are situations where it is better to switch it off:
Imagine you're making music with someone and you are editing on the computer and the other person is playing a MIDI keyboard.
Now whenever you click on a plugin on the screen the MIDI input focus is shifted to that plugin and so the sound on the person's keyboard will change.
That's not comfortable in that situation and so in such case it's better to switch "Automatic MIDI Input Focus" off.
Now even when switched off you can still change the Focused Module manually by drag-dropping the rack/plugin/module you want to play onto the Focused Module Keyboard at the top of the screen.

Notes

  • MuLab App and MuLab Plugin each have their own MIDI Input Channel Targets setup.
    That's due to the different context MuLab App and MuLab Plugin are working in.
    MuLab App will default to routing all incoming MIDI to the Focused Module.
    MuLab Plugin will default to routing all incoming MIDI to the Project Event Input.
    As explained above you can customize that to your needs.

Table Of Contents