User Tools

Site Tools


midi_controller_mapping_file_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
midi_controller_mapping_file_format [2018/02/12 10:40]
pegasus [Inputs] Added info on mapping pitch (0xEn) messages.
midi_controller_mapping_file_format [2018/02/12 10:41]
pegasus [Pitch controls] little-endian
Line 53: Line 53:
 ==== Pitch controls ==== ==== Pitch controls ====
  
-Some controllers send messages with a status byte of ''​0xE//​n//''​ which, per the MIDI standard (see the [[MIDI Crash Course]],) are followed by two value bytes in LSB format. These are usually pitch sliders or pitch wheels. To map these controls, do the same as above but omit the ''<​midino>''​ element.+Some controllers send messages with a status byte of ''​0xE//​n//''​ which, per the MIDI standard (see the [[MIDI Crash Course]],) are followed by two value bytes in little-endian ​format. These are usually pitch sliders or pitch wheels. To map these controls, do the same as above but omit the ''<​midino>''​ element.
  
 ==== Input options ==== ==== Input options ====
midi_controller_mapping_file_format.txt ยท Last modified: 2018/02/12 10:42 by pegasus