====== Ideas/Draft for better midi controler integration ======


.
===== Ideas =====

  - Allow external control for the transport using normal MIDI CCs
  - Allow the mixer to be controled using CCs
  - Allow selecting segments in the arranger using 2 CCs (vertical and horizontal) - is that really useful ?
  - Allow selecting the current track over CCs, maybe dis/enable record state
  - Allow to record Controler movements, in order to articulate midi tracks: expression, velo, portamento, modulation, etc..

.

===== general =====

==== general workflow ====

  - make some knobs and slider values (e.g. mixer volume) controlable (how?)
  - allow rosegarden to receive midi control messages and send them to the right slider-controls (classes ?)
  - make control messages recordable and "playable"
  - add an (UI-) interface for setting up common (hardware-) control interfaces.

.


===== implementation details =====


==== MIDI controler details ====

''
A usual midi control message has 3 Bytes :
  - $B0 (where low-nibble 0-F is the channel nr.)
  - $00 - $7F (the controler number)
  - $00 - $7F (the value (MSB))
It's possible to send a LSB controler-value-pair for fine tuning additionally.
''
  - http://www.computermusicresource.com/MIDI.Commands.html
  - http://www.midi.org/techspecs/midimessages.php
  - http://www.harmony-central.com/MIDI/Doc/table1.html
  - http://www.harmony-central.com/MIDI/Doc/tutorial.html


.


==== OSC support (?) ====

  - None yet

.


===== devices, that should be supported =====

  - All general midi controlers
  - Frontier TranzPort - http://www.frontierdesign.com/Products/TranzPort
  - Steinberg cc121 - http://www.steinberg.net/de/products/hardware/cc121.html
  - Korg Nano Control - http://www.korg.de/produkte/pc-tools/produktinfo7.html