MidiConfig'er - InputControlMap

DeviceType's Control Mappings List:

   But we're not quite done.
   We've NAMED all the controls your keyboard will do,
   but we haven't said what to RECORD into a track when PianoCheater sees these.

   You may want that S1 slider to record
      volume sometimes and balance at other times.
   In fact, you may want your whole SET of controls to map to
      THESE things sometimes and THOSE things at other times.
   So each MidiIn Device needs a current "CCMap"
      (picked in MidiConfiger's main screen in the MidiIn: CCMap column)
      This tells PianoCheater that all the keyboard's controls currently map
         to "THIS set of things to record into tracks".

   You can create several CCMaps and reuse your panel controls to record other
      whole sets of outbound controls.

   To edit a CCMap:
      From MidiConfiger's main screen,
      pick a MidiIn: device's CCMap: (defaulting to .) and
      hit the toolbar button with the ==> green arrow to see...

   

   This screen sets up a CCMap - mappings for all the device's controls.
      (which panel controls record which output controls into the track.)

   When you first create a map,
      JUST the controls a devicetype HAS are listed off (by panel name).

   Now we give each control a cute little cryptic 4 character "out control"
   to record into the track.
   Look through the Global Control List and pick a name to map to.

   Oops, ONE of those controls that you map to can be called...

   EDIT
      It tells PianoCheater which control puts you in "edit mode".
      Normally, PianoCheater records the notes you hit
         into the recording tracks.
         But, if you tweak the control that you mapped to EDIT,
            it'll DO STUFF when you press note keys and
            pick the current "edit track" to operate on.

         When the EDIT control has a value of zero,
            editing is off - keys just record notes as usual.

         Nonzero EDIT values will turn editing on and pop a help window.
            Moving the control through it's range of values will also
            pick the current "edit track" to mess with.
            You'll see the little > on the left side of PianoCheater's display
               scoot around picking the edit track.

         Midi controls usually have, umm, their own "way" of making values...
            But, boiling it down, if you're using a vertical slider,
            use FLIP in the map screen's ModifyCommand column.
               (so the slider matches with the edit track picking direction)
            Use BEND if you're forced to use pitchbend (due to lack of controls)
               Bending down turns edit mode on and picks tracks.
            Use STEP if you're forced to use the programchange control for EDIT.
               It'll make a value of 0=editing off, 1..#tracks=pick edit track.
            For most other controls just leave that ModifyCommand column empty.

           ModifyCommand is still "in work"...
              The idea being that you can
               - modify the channel of an inbound control, maybe device too
               - scale or otherwise alter the control's value
              But currently, there's just FLIP swap 0-127 into 127-0.
                 BEND and STEP only affect the EDIT control.

   Oh yeah, another exception is mapping controls to do_(command)
      For example, maybe you have a button control or pedal that you map to
         do_timePause
      Whenever that control's value transitions from 0 to non0, PianoCheater
         will run the timePause command (that toggles pausing time).
      You can map a control to any of the available commands.
      (See the command mapping screen above to figure out available commands.)

   The rest of the controls are recorded into the track.

   Note that anything not mapped is filtered.

   Ok, put in a first stab at what the controls should record,
   hit SAVE !!
   Make sure that CCMap is picked as the input device's CCMap
   and let's move on...
________________________________________________________________________________

Next up, output controls
   for a given devicetype