Nuzzlet
I noticed certain controlers have functions such as "Get_numark_waveform"
What kinds of midi messages does this send?
What kinds of midi messages does this send?
Posted Wed 25 Sep 19 @ 8:20 pm
PhantomDeejay
These actions are "special" actions that work only with the specified/supported controller.
Usually waveforms on controller screens require specific SYSEX (System Exclusive) messages with specific format to be sent form the software.
That's what these actions do.
An example would be:
F0 XX XX .. XX | 00 00 | 00 00 | 00 00 | 00 00 | ... | 00 00 | F7
F0 specifies the type of the message (SYSEX)
XX XX XX ... XX is the message identifier (device specific)
Then on this particular example each column of the waveform needs two bytes of data. First byte is the height of the waveform, and the second is the color of the column.
Other devices require 3 bytes per column. (height, color, intensity)
Other devices don't use an entire byte, but they wrap the values they need inside specific bits. (So that for instance 5 first bits are color, then rest bits are height, or an other attribute e.t.c.)
Since different devices usually require different coding, once the protocol gets decoded a special action for that display is created.
Usually waveforms on controller screens require specific SYSEX (System Exclusive) messages with specific format to be sent form the software.
That's what these actions do.
An example would be:
F0 XX XX .. XX | 00 00 | 00 00 | 00 00 | 00 00 | ... | 00 00 | F7
F0 specifies the type of the message (SYSEX)
XX XX XX ... XX is the message identifier (device specific)
Then on this particular example each column of the waveform needs two bytes of data. First byte is the height of the waveform, and the second is the color of the column.
Other devices require 3 bytes per column. (height, color, intensity)
Other devices don't use an entire byte, but they wrap the values they need inside specific bits. (So that for instance 5 first bits are color, then rest bits are height, or an other attribute e.t.c.)
Since different devices usually require different coding, once the protocol gets decoded a special action for that display is created.
Posted Wed 25 Sep 19 @ 8:44 pm