What you see
Drop Control Mapper into your project and point MIDI In or OSC In at your input. Pulse Open Editor to see every mapping in one list.
Control Mapper also comes built into Parameter Morpher and Scene Launcher, so mapping works the same way there.
Connect your controller
These live on the Settings page. Fill in the protocols you use and leave the rest empty.
- MIDI In: the CHOP your MIDI arrives on.
- MIDI From Range: the lowest and highest values your MIDI device sends. The default is 0 to 127.
- OSC In: the CHOP your OSC arrives on.
- OSC From Range: the lowest and highest values your OSC messages send. The default is 0 to 1.
Find your controls
Control Mapper only offers controls it knows about. Each one carries a small marker with a tag, and a scan finds them.
Find every tagged control under Map Root and make it ready to map.
- Map Root: where to look for controls. Leave it empty to use the component's own parent, which is right when Control Mapper sits inside the thing you are mapping.
- Target Tag: the tag the scan looks for. The default is mapTarget.
Map a control
Mapping takes three steps: turn on map mode, click a control, then move a fader or knob on your device or send an OSC message.
Show every control you can map.
Arm it. It blinks while it waits for your device.
Bind it to the armed control. The move you teach with does not also change the value.
Disarm it without mapping anything.
Move the mapping to the new control. Its range and takeover stay as they were.
Stop learning. Your mappings now move their parameters.
Edit your mappings
Pulse Open Editor to open the list. It updates on its own whenever a mapping changes.
Change that mapping's channel or range.
Switch that mapping between jump and pickup.
Re-arm that row. The next channel that arrives replaces its old one.
Remove that mapping.
Change the order of the list.
Prune dead mappings, clear all of them, or refresh the list.
Ranges and takeover
Each mapping has its own min and max, taken from the parameter when you map it. Narrow them to use only part of the parameter's range.
- jump: the default. The parameter snaps straight to wherever your control sits.
- pickup: nothing happens until your control passes the parameter's current value, then it takes over. Use it when a fader is not where the scene left the parameter, so nothing jumps.
With pickup, if something else moves the parameter later, such as a preset recall, a morph or a hand edit, your control waits again until it reaches the new value. A menu is picked up when your control reaches the selected item.
Missing and driven mappings
A mapping never breaks silently. The list marks it so you can see what is wrong.
Delete every mapping marked missing. Driven ones stay.
Delete every mapping. It asks first.
- (missing): the control or parameter is gone, for example after a rename. The mapping is kept until you prune it.
- (driven): the parameter is now set by an expression or an export, so the mapping leaves it alone. It works again once the parameter is a plain value.
Colours and info
Colour the mapping list: Carbon, Verdigris or Mono.
Put the skin's colours back after you changed one by hand.
- Number of Mappings: on the Info page, how many mappings you have.