Frequently Asked Questions for iConnectMIDI4+

The port routing in iConfig seems overwhelming, how does it work?

Each USB Device Jack has 16 MIDI ports.

When iConnectMIDI4+ is connected to a Mac, the MIDI ports will be recognized as:

  • DIN1 - MIDI 1 DIN
  • DIN2 - MIDI 2 DIN
  • DIN3 - MIDI 3 DIN
  • DIN4 - MIDI 4 DIN
  • USB - USB 1 or 2 Device Jack
  • USB - USB 2 or 3 Device Jack
  • HST 1 - USB Host MIDI port 1
  • HST 2 - USB Host MIDI port 2
  • HST 3 - USB Host MIDI port 3
  • HST 4 - USB Host MIDI port 4
  • HST 5 - USB Host MIDI port 5
  • HST 6 - USB Host MIDI port 6
  • ETH 1 - Ethernet MIDI port 1
  • ETH 2 - Ethernet MIDI port 2
  • ETH 3 - Ethernet MIDI port 3
  • ETH 4 - Ethernet MIDI port 4


When iConnectMIDI4+ is connected to a Windows computer, the MIDI ports will be recognized as:

  • iConnectMIDI4+ - MIDI 1 DIN
  • MIDIIN2/MIDIOUT2 - MIDI 2 DIN
  • MIDIIN3/MIDIOUT3 - MIDI 3 DIN
  • MIDIIN4/MIDIOUT4 - MIDI 4 DIN
  • MIDIIN5/MIDIOUT5 - USB 1 or 2 Device Jack
  • MIDIIN6/MIDIOUT6 - USB 2 or 3 Device Jack
  • MIDIIN7/MIDIOUT7 - USB Host MIDI port 1
  • MIDIIN8/MIDIOUT8 - USB Host MIDI port 2
  • MIDIIN9/MIDIOUT9 - USB Host MIDI port 3
  • MIDIIN10/MIDIOUT10 - USB Host MIDI port 4
  • MIDIIN11/MIDIOUT11 - USB Host MIDI port 5
  • MIDIIN12/MIDIOUT12 - USB Host MIDI port 6
  • MIDIIN13/MIDIOUT13 - Ethernet MIDI port 1
  • MIDIIN14/MIDIOUT14 - Ethernet MIDI port 2
  • MIDIIN15/MIDIOUT15 - Ethernet MIDI port 3
  • MIDIIN16/MIDIOUT16 - Ethernet MIDI port 4

Or they could also be recognized as the following:

  • iConnectMIDI4+ (Port 1) - MIDI 1 DIN
  • iConnectMIDI4+ (Port 2) - MIDI 2 DIN
  • iConnectMIDI4+ (Port 3) - MIDI 3 DIN
  • iConnectMIDI4+ (Port 4) - MIDI 4 DIN
  • iConnectMIDI4+ (Port 5) - USB 1 or 2 Device Jack
  • iConnectMIDI4+ (Port 6) - USB 2 or 3 Device Jack
  • iConnectMIDI4+ (Port 7) - USB Host MIDI port 1
  • iConnectMIDI4+ (Port 8) - USB Host MIDI port 2
  • iConnectMIDI4+ (Port 9)- USB Host MIDI port 3
  • iConnectMIDI4+ (Port 10) - USB Host MIDI port 4
  • iConnectMIDI4+ (Port 11) - USB Host MIDI port 5
  • iConnectMIDI4+ (Port 12) - USB Host MIDI port 6
  • iConnectMIDI4+ (Port 13) - Ethernet MIDI port 1
  • iConnectMIDI4+ (Port 14) - Ethernet MIDI port 2
  • iConnectMIDI4+ (Port 15) - Ethernet MIDI port 3
  • iConnectMIDI4+ (Port 16) - Ethernet MIDI port 4


If you look in iConfig Port Routing, the Port window on the left is the source of the MIDI messages.
Any iOS device, or computer connected to this Jack on iConnectMIDI4+, will have 16 possible ports to output to any device connected to the iConnectMIDI4+.

iConfig MIDI routing

Port Routes (Destinations) on the right, are the chosen destination for these MIDI messages created from the iOS device/computer that is connected to that USB Device Jack.
For example,
If DIN 1 is selected under USB Device Jack 1 in the Port window, in Port Routes (Destinations) window, DIN 1 for DIN Jack 1 is enabled (grey).

iConfig MIDI routing

This will enable any MIDI messages created from the connected iOS Device/computer ……

iConfig MIDI routing

to pass to a MIDI Device connected to MIDI 1 DIN Jack of the iConnectMIDI4+.

iConfig MIDI routing

*Please note, concerning the device connected to USB Device Jack 1, the MIDI Preferences/Settings for the applicable computer application/iOS app would need to have iConnectMIDI4+ DIN 1 enabled for MIDI output.

If that same MIDI Device Connected to MIDI 1 DIN jack on the iConnectMIDI4+ were to pass MIDI messages to the USB 1 Device Jack, (For example, to act as a controller in a synth app on a connected iOS device)
In iConfig, select DIN 1 under the Port window & you’ll notice on the Port Routes (Destinations) window, every MIDI Jack is enabled to receive MIDI from DIN 1 except for itself.

iConfig MIDI routing

Disabling all ports and then enabling only the necessary port destination will show the path for the DIN connected device to pass MIDI messages to an iOS device connected to USB 1 Device Jack on iConnectMIDI4+.
*As long as the MIDI Preferences/Settings in the iOS app has iConnectMIDI4+ DIN 1 enabled for input, MIDI created from that MIDI DIN device will control the synth app.

iConfig MIDI routing

iConnectMIDI4+ USB Host Port.

I’ve connected a class-compliant USB MIDI keyboard to the iConnectMIDI4+ USB Host Jack.
* The USB Host Jack will support up to 8 class-compliant USB Devices when connected through a powered USB hub.

iConfig MIDI routing

In MIDI Info of the iConfig application, under the Port Information window, there is USB HOST Jack 1 & this one jack has 8 MIDI ports (HST 1-8).
You can see that the Akai is recognized in Port 1 (HST 1).
First device connected will populate the 1st port, second device connected will populate the 2nd port (when connected through a powered hub) and so on.

iConfig MIDI routing

If you want specific controllers to be reserved on specific ports, you can do this under the Reserved menu for each port.

iConfig MIDI routing

I will reserve the Akai to always populate Port 2 (HST 2).

iConfig MIDI routing
iConfig MIDI routing

Commit Changes to Flash.

iConfig MIDI routing
iConfig MIDI routing

Reset the device & confirm the change.

iConfig MIDI routing
iConfig MIDI routing

Now Akai will always populate USB Host Port 2, even after disconnecting the device.

iConfig MIDI routing

In Port Routing, select USB Host Jack 1 – HST 2 in the Port window.
You will see that any MIDI outputted from the Akai (HST 2) will route to every Jack on the iConnectMIDI4+ except itself.

iConfig MIDI routing

I will clear all routing and then enable the correct Port to route Akai MIDI messages into an iOS device connected to the USB 1 Device Jack.

The 8th MIDI port for USB Device Jack 1 is the destination for the Akai’s MIDI data, this will let the Akai control the iPad app (again, if iPad’s MIDI settings/preferences are enabled for input from that port (HST 2)).

iConfig MIDI routing

If I had a computer connected to the USB 3 Device Jack on the iConnectMIDI4+ & wanted the Akai to control a software instrument in a DAW, I would enable the 8th port for USB 3 Device Jack.
And again, as long as the DAW on the computer has the HST 2 port enabled for MIDI input in it’s MIDI Settings/preferences.

iConfig MIDI routing

FAQ Category: 

When connecting the iConnectMIDI4+ to my iPad, I can't hear the audio through the iPad speakers or headphone jack.

By default when connecting an iOS device to the iConnectMIDI4+, it will enable the iOS’s digital audio to pass through the iOS device's dock connector and disables that iOS device's internal speakers/headphone jack. To change this, so that audio will sound through the iOS device's headphone jack/speakers: In iConfig, under the Audio Info section, de-select "iOS " for the iCM4 USB Device Jack that iOS Device is connected to and then perform a "Commit & Reset".

FAQ Category: 

You can change the port names on the iConnectMIDI4+ within the MIDI Info section of the iConfig application. After changing the names you will need to select “Commit Changes to FLASH” in iConfig and then disconnect iConnectMIDI4+ from your Mac. Open up Audio MIDI Setup and delete any iConnectMIDI4+ images that are in the MIDI window. When you reconnect the iConnectMIDI4+, the Mac will retrieve the new names. To have the custom names reflect on your iOS device, you need to reset the iOS device. You can do this in Settings/General/Reset/Reset All Settings. The “Reset All Settings” option will not delete any of your media or data. Do NOT tap the "Erase All Content and Settings", that setting will remove all data and media on your iOS device. After doing this, the new custom port names should be displayed on your iPad. Unfortunately at this time, PC’s are not able to reflect these changes. Something to be aware of: when changing the names under the specific USB Device Jack, it is how the computer or iOS device connected to that specific Jack will recognize it. For example, if you change the name for DIN 1 under USB Device Jack 1 and you connect a Mac to USB Device Jack 3, the computer will still recognize that port as DIN 1. You would need to change it under USB Device Jack 3 for that connected device to see the new name for that port.

FAQ Category: 

Using the iConnectivity iConfig application, you can change the audio configuration for the iConnectMIDI4+. Here is a list of the possible Audio Channel options: 44100Hz, 4 Channels, 16bit 48000Hz, 4 Channels, 16bit 96000Hz, 4 Channels, 16bit 44100Hz, 8 Channels, 16bit 48000Hz, 8 Channels, 16bit 44100Hz, 4 Channels, 24bit 48000Hz, 4 Channels, 24bit

FAQ Category: 

When attempting to update the firmware with the iConfig application, the status declares that it’s rebooting to boot-loader mode, then a pop-up notifies of a communication error, and nothing happens. No firmware update actually takes place.

For successful firmware upgrades on the iConnectMIDI4+, the computer performing the upgrade (via iConfig) has to be connected to the 3rd USB Device Jack on the rear of the device.

FAQ Category: 

My PC no longer recognizes my iConnectMIDI4+ In device manager, the iConnectMIDI4+ is not recognized in “Sound, video and game controllers”, but the USB port it is connected to has a yellow exclamation point with a “This device cannot start. (Code 10)” error in it’s properties.

This seems to be an issue where disabling the Mac/PC Audio passThru for the USB Device Jack that a PC running Windows is connected to, will no longer communicate properly with the PC. To regain connectivity, re-enable the Audio passThru using the iConfig application on a connected iOS device, or if you haven't disabled the Mac/PC audio passThru for the remaining 2 USB Device Jacks on iCM4, connect to one of these jacks and connect to iConfig to re-enable the audio passThru. Don't forget to save your changes to FLASH.

FAQ Category: 

My “Class Compliant” controller does not seem to work with the iConnectMIDI4+ host port as stated it should in the user manual and specifications.

iConnectivity has recently discovered that some models of controllers by some manufacturers that advertise “Class Compliant” are in fact not class compliant as defined by the USB IF specification for “Device Class Definition for MIDI Devices”. iConnectivity basis their claim on Class Compliant as per this specification. iConnectivity also recognizes that the controllers in question have a large user base and have started taking measures towards supporting these controllers with our USB host enabled products by making adjustments to our drivers to support these non-class compliant devices like Mac OS and Windows have done. In the meantime, if you have issues with a controller that is supposed to be class compliant, please contact our Support team to confirm if it is one of these controllers.

FAQ Category: