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 30pin connector and disables the iPad's internal speakers and headphone jack.
To change this, so that audio will sound through the iPad's headphone jack/speakers:
In iConfig, under the Audio Info section, de-select "iOS " for iCM4 USB Device port that you wish to change, then "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: 

Can I use the Apple Lightning to 30-pin connector of the Apple Camera Connection Kit?

Until we can supply our own Lightning equipped connection cables, the Apple 30-pin to lightning adaptor will indeed work with our 30-pin connection cable.
The Camera connector will not work with our unit.

FAQ Category: 

As many know, the best solution for low latency in Windows is ASIO. Many refer to it as ASIO drivers, but this is actually an inaccurate way of describing what ASIO does. ASIO is in fact a communication object that bypasses the Windows Media System (the latent part) to allow an application to directly communicate with the drivers. The device drivers are in fact the same if you use the ASIO comm object or not.

Unfortunately, although ASIO satisfied the need for low latency as best it could with Windows systems - it does have another shortcoming. Only ONE ASIO Comm object can be executing in the system at any one time.

So all of that said, creating a dedicated ASIO Comm for iConnectMIDI2+ would only solve half of the problem. There would still be the challenge of attempting to use more than one ASIO object simultaneously. We investigated solutions to this problem and discovered that the team from ASIO4ALL solved this problem quite some time ago in a fairly elegant and easy to use way. ASIO4ALL is stable and typically delivers comparable (or in some cases better) performance than device dedicated ASIO comm objects and also allows Windows users to create an aggregate ASIO device out of multiple compatible audio peripherals.

FAQ Category: 

I received your iConnectMIDI2+ and there's no power adapter with it. How am I supposed to power the device?

While the iCM2+ can be powered by the Optional Power Transformer, it is only of necessary use in having the iCM2+ charge an iOS device connected to Port 1 on the iConnectMIDI2+.

You can power the device two other ways without the Power transformer:

  • connecting to a Mac or PC USB port and connecting to port 2 on the iCM2+ to power by USB power
  • connecting from USB port 2 on the iCM2+ to a wall charger that you would normally get with an iOS device.
FAQ Category: 

You can change the port names on the iConnectMIDI2+ 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 iConnectMIDI2+ from your Mac. Open up Audio MIDI Setup and delete any iConnectMIDI2+ images that are in the MIDI window. When you reconnect the iConnectMIDI2+, 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 2, the computer will still recognize that port as DIN 1.
You would need to change it under USB Device Jack 2 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 iConnectMIDI2+ to any of the options below:

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: 

Ensure that the 5-pin midi cables connect; MIDI/IN ->MIDI/OUT and MIDI/OUT->MIDI/IN (a very overlooked issue)

if Mac, try MIDIMonitor. http://www.snoize.com/MIDIMonitor/ (free download)
Open "Sources" then "MIDI sources", the iCM-1 should be listed here.
Ensure that the boxes for these are checked. The window below should display all incoming MIDI data coming from the iCM-1.

Windows; When connecting the iCM-1 into your PC via the USB for the first time, Windows should recognize the device with a message "Installing device driver software".
Go to: "Contol Panel/Device Manager/Sound, video and game controllers" The iCM-1 should be displayed in this list, if Windows recognized it properly.

Try downloading MIDI-OX for your PC (free download). http://www.midiox.com
On the top tool bar (4th icon from the left) there is an icon: "Display Raw MIDI Input" this will display all MIDI data coming from the iCM-1.
When you engage your midi device through the iCM-1 you should see the corresponding data listed here in real time.
Open the icon next to it "Main Output Monitor". Now click "view/Device Info", this will display the iCM-1 in the Monitor-Output window as

" IN: 1) iConnectMIDI1
OUT: 2) iConnectMIDI1"

Clicking "Options/MIDI Devices", you should also see the iCM-1 listed here in MIDI Inputs and Outputs windows.
Under, "View/port status" the iCM-1 should be listed here as well.

TIP: (if you are using a Windows operating system, ensure that no other programs are running on your PC, except for the one you are trying to connect to)

If all these steps check positive, this will ensure that iCM-1 is functioning properly and that the problem could reside within the settings of your operating system or software program.

FAQ Category: 

Ensure that the 5-pin midi cables connect; MIDI/IN ->MIDI/OUT and MIDI/OUT->MIDI/IN (a very overlooked issue)

if Mac; try MIDIMonitor. http://www.snoize.com/MIDIMonitor/ (free download)

Open "Sources" then "MIDI sources", the mio should be listed here.
Ensure that the boxes for these are checked. The window below should display all incoming MIDI data coming from the mio.

Windows;
When connecting the mio into your PC via the USB for the first time, Windows should recognize the device with a message "Installing device driver software".

Go to: "Contol Panel/Device Manager/Sound, video and game controllers"
The mio should be displayed in this list, if Windows recognized the mio properly.

Try downloading MIDI-OX for your PC (free download). http://www.midiox.com

On the top tool bar (4th icon from the left) there is an icon: "Display Raw MIDI Input" this will display all MIDI data coming from the mio.
When you engage your midi device through the mio you should see the corresponding data listed here in real time.

Open the icon next to it "Main Output Monitor".
Now click "view/Device Info", this will display the mio in the Monitor-Output window as

" IN: 1) mio
OUT: 2) mio"

Clicking "Options/MIDI Devices", you should also see the mio listed here in MIDI Inputs and Outputs windows.
Under, "View/port status" the mio should be listed here as well.

TIP: (if you are using a Windows operating system, ensure that no other programs are running on your PC, except for the one you are trying to connect to)

If all these steps check positive, this will ensure that mio is functioning properly and that the problem could reside within the settings of your operating system or software program.

FAQ Category: