add-circle-bold add-circle add-square add alarm-bell-1 alert-diamond analytics-pie-2 archive archive arrow-down-1 arrow-down-2 arrow-left-1 arrow-right-1 arrow-up-1 attachment-1 bin-paper-1 book-star button-record check-1 check-circle-1 close close-quote close cog-1 cog common-file-stack copy-paste credit-card-1 diagram-fall-down disable time-clock-midnight download-thick-bottom drawer-send envelope-letter envelope-letter expand-6 expand-6 file-code filter-1 floppy-disk flying-insect-honey folder-file-1 headphones-customer-support hierarchy-9 hyperlink-2 information-circle keyboard-arrow-down keyboard-arrow-up layout-module-1 list-bullets lock-2 lock-unlock-1 love-it messages-bubble-square move-to-top multiple-circle multiple-neutral-1 multiple-users-1 navigation-menu-horizontal navigation-menu network-browser open-quote pencil-1 pencil-write pencil-1 print-text rating-star rating-star remove-circle remove-square-1 search send-email-1 shield-warning single-neutral-actions single-neutral smiley-sad-1 smiley-unhappy smiley-indifferent smiley-smile-1_1 smiley-happy smiley-sad-1 smiley-unhappy smiley-indifferent smiley-happy smiley-thrilled social-media-twitter synchronize-arrows-1 tags-double ticket-1 ticket-1 time-clock-circle undo view-1 view-off view wench

Demystifying MIDI filtering in iConfig

"Be the Ball"

A common phrase heard in coaching movies and now a way to look at filtering in iConfig: Be the interface.

Taking the view of the interface when looking at the left column in the MIDI Routing, MIDI Filtering, MIDI Remapping in iConfig is the best way to understand what data you are controlling.

Input vs. Output

On the MIDI filtering tab in iConfig you will notice a dropdown menu in the top left of the page where it says Input and the dropdown can be used to switch to Output.

For illustration:

  • We have a MIDI foot controller connected to the USB-MIDI Host port on a mio4. This controller is reserved into HST1 port.
  • We also have Computer A on USB Device Jack 1 and Computer B on USB Device Jack 2.
  • The MIDI controller sends both a Program Change and Note on/off Data at the same time.

Using a MIDI monitor on Computer A we see this:

Example 1:  We want to filter all note data coming from the foot controller into the mio4 so the note information does not go to anything (Comp A and Comp B specifically)

In this example we will block Note On/Off Events only.

If we remember our new motto , be the interface, we will want to filter the MIDI data from the controller to the interface Input. 

In the left column we will now select HST1 under USB Host Jack. See image below:

Now when we run the MIDI monitor on Comp A we see only the Program change, as we have successfully filtered the note data.

Example 2: We want to filter all note data going from the foot controller to Computer B only. We want Program Change to go to both Comp A and Comp B but only Note data going to Comp A.

In this example we will block Note On/Off Events only.

This time we will select Output in the dropdown because we cannot block the notes from getting to the interface or it will block both anything from getting that data. We will need to specifically block the Note data from going Out to the computer port.

In the left column select HST1 under USB Device Jack 2:

We keep Computer A/USB 1 with the default: No filtering.

Now when we run the MIDI monitor on Computer A we see the same thing:

On Computer B we will see the change:

Hopefully these examples will help you understand MIDI Filtering in iConfig a little better.