SM example

[SounDuke]

I'm really amazed by the great work Jim and Thorsten made with the matrix handling application. Just a thought: is it possible to enhance the code to map each single button of the matrix to send to different channels (split zones) or that would cause too much latency? I noticed that Thorsten eliminated display update in 2nd example because of the latency determined by it.. so could a button events editor be unreachable?

[TK.]

Hi,

it doesn't matter which MIDI events are sent, due to the large MIDI output buffer which is provided by MIOS (a FIFO), the timings are very relaxed once an (button toggle) event has been determined

Best Regards, Thorsten.

[SounDuke]

In which way it is possible to assign a midi event/channel to each button in the matrix? 

[TK.]

There is a SM_NotifyToggle function which works like USER_DIN_NotifyToggle, this means that up to this point you can generate MIDI events like shown in the examples and big applications (e.g. table method, calculated events, programmed events or whatever)

Best Regards, Thorsten.