If you want your faders, knobs, and buttons to follow the way you work, iMap is where you set it up. This guide shows you how to assign MIDI channels and Control Change (CC) messages, build useful Layers, and save a repeatable hands-on layout to your iControls or iControls Pro.

The original iControls and iControls Pro are different products. The custom MIDI setup is similar, while the iControls Pro also provides Mackie Control on Layer 1.

What you'll need

You need:

• Your iControls or iControls Pro and USB cable
• The correct iControls version of iMap
• The MIDI-mapping information for your DAW or other software

The iControls is class compliant, so it does not need a separate iCON driver.

1. Get the correct iMap

Step-by-Step Setup

1. Download Smart Install
   • Visit iconproaudio.com
   • Find your device model, click its link, go to Downloads, and select the Smart Install file.

Use the version listed for your exact device!

2. Plug in iControls and select it in iMap

1. Connect iControls directly to a USB port on the computer.
2. Open the iControls version of iMap.
3. When the device selector appears, choose iControls.
4. If your iMap version includes a MIDI Devices button, open it and select ICON iControls as the MIDI Out device.

If iMap cannot see the controller, try another USB port or a known-good USB data cable, then see [iMap does not detect your controller or keyboard link].

3. Make the faders, knobs, and buttons your own

The iControls provides nine faders, nine knobs, eighteen control buttons, transport controls, and four Layers.

Faders

Choose a MIDI channel from 1 to 16 and a CC number from 0 to 127 for each fader. The manual recommends Fader 9 for volume with CC 07. CC numbers 120 to 127 are non-linear commands, so use a different CC for a fader.

Knobs

Choose a MIDI channel and a linear CC number for each knob. Knobs work well for parameters such as pan or other continuous controls supported by your software.

Control buttons

Choose the MIDI channel and CC number required by your software for each button.

Transport controls

The front-panel transport controls can send MIDI Machine Control (MMC). Your DAW or MIDI application must support MMC and be configured for the messages sent by the controller. Check the application documentation before assigning these controls.

4. Give each workflow its own Layer

The four Layers let the same physical controls do different jobs. For example, one Layer can control your mixer while another handles an instrument or a second application. That keeps the controls you need close without rebuilding the whole setup.

Configure each Layer in iMap, then test it in the target software. DAW-specific behavior should be verified before publication because message handling can vary by application.

5. Send the mapping and save a backup

1. Click Send Data to write the current settings to the connected controller.
2. Click Save file to save the layout as an .icon file.
3. Use Load file to open a saved layout later.

How Mackie Control works on iControls Pro

On iControls Pro, Layer 1 is the built-in Mackie Control layer. Select Layer 1 when your DAW is configured for Mackie Control. No custom iMap mapping is required for that layer.

Layers 2, 3, and 4 use custom MIDI mappings. They do not extend the Mackie Control layer.

In Mackie Control mode, the Channel and Bank controls move through the mixer by one channel or eight channels. Other functions are available through the programmed function and transport buttons.

How to create a toggle or latch action

Standard MIDI Note and CC messages do not add toggle or latch behavior by themselves. Configure that behavior in the DAW or application receiving the message.

For example, Ableton Live provides clip-launch trigger modes, and Max for Live can translate MIDI messages for more specialized workflows. Verify the exact setup in the documentation for your software.

How to restore factory settings

Hold Rewind, Play, and Fast Forward together. This restores the factory settings and replaces the custom mapping currently stored on the controller.

How to connect more than one i-series controller

The iControls manual supports a chain of up to three iControls or compatible i-series controllers.

1. Connect the first unit to the computer.
2. Connect the next unit to the second USB port on the first controller.
3. Repeat for a third supported unit.

Because the controllers use USB bus power, confirm stable operation after each device is added.

Firmware update notes

If iMap offers firmware for your device, connect the controller directly to the computer and keep it connected until the update is complete.

Some original iControls units running early firmware cannot be updated by the user. If the update will not begin, contact iCON Support with the model and current firmware version before trying another file.

The project support records also identify firmware-update limits on some AMD and Apple Silicon computers. If an update cannot complete, use a supported Intel computer or base M1 Mac, or ask iCON Support to confirm a compatible update computer. This limitation concerns the update process, not normal controller operation.

Frequently asked questions

Does iControls need a driver?

No. iControls is a class-compliant USB MIDI controller and does not need a separate iCON driver.

Which iControls Pro Layer uses Mackie Control?

Layer 1. Layers 2, 3, and 4 are for custom MIDI mappings created in iMap.

Why do my iControls Pro Mackie functions not work?

Confirm that Layer 1 is selected and that the DAW is configured for Mackie Control. Then verify the MIDI input and output ports selected in the DAW.

Can an iControls button work as a toggle?

Yes, when the receiving software provides toggle or latch behavior. Configure the action in the DAW or MIDI application rather than in iMap.

What file type stores an iControls mapping?

iMap saves an iControls mapping as an .icon file.

Need more help?

If something does not work as expected, contact iCON Support with the exact controller model, operating system, iMap version, firmware version, DAW, and the step where you stopped. Those details help the team understand your setup from the first reply.