Controller Mapper

The Controller Mapper Module

The Controller Mapper allows you to map the various aspects of your hardware controllers onto your MSDP parameters. To use this module, begin by selecting your hardware from the drop-down menu at the top. If you don’t see your device, press the “Refresh Controller List” button. If you still don’t see your device, check that it is connected, and try restarting the application.

Below the device selection menu you’ll see a set of four displays:

1. Active Control # - If you are sending a control message, it will be picked up and the control number will be displayed here.
2. Active Value # - If you are sending a control message, the control value will be displayed here.
3. MIDI Note # - If you are sending a MIDI note message, the pitch value will be displayed here.
4. MIDI Velocity # - If you are sending a MIDI note message, the velocity value will be displayed here.

These four displayed values at the top do not do anything, they simply display the current information coming in from your hardware. You can use this information when you are mapping your parameters. The last two values in the mapping ask whether you want to map this with control or pitch data, and then what control or pitch number you want to use. If you are not sure which information you are getting from your device, move the controller or play the note, and look at the information in this top display.

In the middle of the module we see an instruction to ‘Select Control Mapping to View’ and there is a bank of 16 squares below. Select one of the squares to display the mapping data stored in that slot.

When you select a slot, the mapping information contained within it is displayed below. To establish a mapping, follow these steps:

1. Enter the destination Module ID: This can be found above the module that you want to map to. You can easily copy/paste from one location to the other.
2. Select a module parameter: This is the number next to the UI object you want to interact with. Typically, volume is parameter 3, and often the most important parameter for the individual effect will follow at parameter 4. Just look through the module to find the number you need.
3. Choose Mapping mode: Scale is best for sliders and knobs. Toggle and Switch are better for buttons.
4. Low Value: the lowest value you want your destination parameter to go to when you use your controller.
5. High Value: the highest value you want your destination parameter to go to when you use your controller.
6. Ramp Time: If you want to automate a slide between each value, set a time for that slide (in seconds). For parameters that you’ll be controlling with sliders and pots, you’ll probably want a ramp time of 0.
7. Choose Hardware Mode: Control for controller data (sliders, knobs, buttons), Pitch for note data (like a piano-style keyboard).

Finally the “Viewing” section on the right allows you to view the function of the mapping. When the mapping receives data from the hardware, the “Active” light will flash, and the output value will be displayed at the bottom.