MIDIRX registration added to midi_send interface

[SukuWc]

Testing MIDIRX functionality

• See instruction SUKU midi action block updated to support rx options grid-editor#1479

Testing RTM (sync) messages.

• Set up the DAW to send midi tempo messages to Grid
• Setup grid to listen to RTM messages
• Start playback in DAW and exemine debug messages in Grid Edtior

self.rtmrx_cb = function(self, t)
  if t == 0xF8 then
    print("clock")
  else
    print("unknown")
  end
end

Expected messages:

[0,0] unknown (<--- this is the playback start message)
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock
[0,0] clock

Typical RTM values sent by MIDI devices:
0xFA=Start, 0xFB=Continue, 0xFC=Stop, 0xF8=Clock, 0xFE=Active Sensing, 0xFF=Reset.

Deprecated interfaces

Non functional legacy midirx_enabled and midirx_sync interface are now removed

Midi RX gating

Received midi channel voice, sysex and RTM messages can be gated separately to allow the user to only enable what is actually used.
By default midi channel voice messages are allowed to be transported and handled by midirx_cb, all other types are disabled by default.

grxm(rx_type, mode_bm) --minified version available currently in editor
rx_mode(rx_type, mode_bm) --human version available in next exitor release

rx_type is an integer with valid values of 0: MIDIVOICE, 1: MIDISYSEX, 2: MIDIRTM
mode is a bitmap with the following valid combinations:

Decimal 0: Binary 0b00: don't forward from USB and don't handle in Lua CB
Decimal 1: Binary 0b01: don't forward from USB, but handle in Lua CB
Decimal 2: Binary 0b10: forward from USB but don't handle in Lua CB
Decimal 3: Binary 0b11: do forward from USB and handle in Lua CB

[Greg-Orca]

Ableton sends this when I put the playheads to other positions. This messages is the Playhead positions. One message is one playhead position

[Greg-Orca]

14bit midi, we need to check the msb value and use that for the led value and multiply it

[SukuWc]

event rx?