iConnectivity mio10, Owner'S Manual

Page: 18 / 21

14
Using mio MIDI Management to Optimize Your Rig
The factory setup for your mio10 connects “everything to everything,” so you can quickly get
gear connected, use your controllers, and listen to your sounds.
Once you have your gear connected and working, and you’ve become familiar with the mio10’s
MIDI management features, we recommend you spend some time tweaking your settings to
improve efficiency, minimize latency, and avoid potential data loss.
Here are some recommended guidelines for optimizing your setup, to be done in the order
shown. Don’t forget to save your new configuration to the mio10 for next power-up:
1.
Reserve controllers on USB host ports.
When devices are connected to the USB host jack they are assigned MIDI ports on a “first come first serve”
basis. To ensure a consistent, optimized system you need to ensure that hosted devices always appear on the
same MIDI port every time they are connected. You can reserve a port on the USB host jack for a certain
device by choosing that device from the drop-down list on the MIDI Info page. Devices are recognized by the
manufacturer and model only. If you have two of the same controller and they have different setups, ensure
that they are always connected to the same port on your USB hub, then when mio4 powers up it will
enumerate the controllers in the same order every time.
2. Disable MIDI outputs for controllers that only send MIDI data.
Many controllers send MIDI data but ignore any MIDI data that is sent to them. Good examples are Korg
nanoKey/microKey or the multitude of Akai MPK controllers. Suppose you have eight of these controllers
connected to the USB host jack: every time you press a key on any one of these controllers that key event is
sent to the other seven controllers, which wastes data bandwidth because they don’t respond to key events.
You can use your mio to save seven times the bandwidth and processing simply by disabling the MIDI outputs
for those eight controllers. The easiest way to do this is to go to the
MIDI Info Page in iConfig and uncheck
the “output enable” box. This will prevent any MIDI events from being sent to those controllers. If you have
MIDI controllers on the USB host jack that need to receive MIDI input of some kind (e.g. because they
generate sound or you need to send sysex dumps to them) then don’t uncheck the “output enable” box.
These we can optimize in a different way (explained later).
DIN ports are a bit different in that you can separate the MIDI IN and MIDI OUT signals for each port to
different boxes. For example, you may have a MIDI controller attached to DIN 1 IN and a sound module
attached to DIN 1 OUT. In this case you wouldn’t want to uncheck the “output enable” box for DIN 1 port.
These we can optimize in a different way (explained later).
3.
Disable MIDI inputs for controllers that only receive MIDI data.
Perhaps you have a sound module that never sends MIDI data, or a sound module that sends MIDI data that
you don’t need. It’s best to remove that module as a source of MIDI data. The easiest way to do that is to go
to the
MIDI Info Page in iConfig and uncheck the “input enable” box. If you have MIDI controllers on the USB
host jack that need to send MIDI data of some kind then don’t uncheck the “input enable” box. These we can
optimize in a different way (explained later).