I only ask because usually I would use RockIt to map TO the controller.
This sounds like the opposite...the controller has the map config and lines up with PockIt...
Jim, here's how it works:
Rockit has a MIDI interface, but the controller can't tell it what to do, until Rockit knows what is what on the controller. So the Rockit mapper needs to know the MIDI code of each control on the controller. For example, here's a single MIDI command in a mapper, that tells Rockit to Play the song in deck A (controllers use different MIDI keys, this one happens to be from the Numark Total Control):
Code:
<cm action="a-play" type="button" midikey="67" rlow="0" rhigh="127" lit="2" lkey="62"/>
Let's break it down:
action = What Rockit should do, when the controller sends the following codes.
type = button in this case.
midikey = That's the code the controller sends, when you press that button.
rlow = That's when the button is released.
rhigh = That's when the button is pressed.
The lit and lkey are used for Rockit to send a code back to the controller, to turn on a lighted button.
Every controller uses different codes, hence the mappers, so you can adjust them to a certain controller.