Wow, thank you very much for this information @Silver! I’m going to investigate this issue, see if I can get it to work with the colors and intensity of my PADs on the Akai MPD232 I didn’t know all this yet. Apparently, the brands manage to hide all this information on purpose to maintain control and that the end user ends up paying more::
Changing individual pads
It seems that FL Studio sends the entire pad array in a single SysEx message, which is probably a good thing as then all pads change color in unison. But it doesn’t need to.
To construct a SysEx message that changes the pad colors:
F0 – System Exclusive
47 – Akai Manufacturer ID (see the MMA site for a list)
7F – The All-Call address
43 – Fire Sub-ID
65 – Write Pad Array command
hh – High length byte, bits 7 through 13 of following payload
ll – Low length byte, bits 0 through 7 of following payload
Repeat for pads you want to change {…
ii – Pad index, 00 top left through 3F bottom right
rr – Red level, 00 through 7F
gg – Green level, 00 through 7F
bb – Blue level, 00 through 7F
…}
F7 – End of ExclusiveSimple as that! To make it super-real, we can change pad 4 of row 2 to full-intensity blue by sending the following SysEx message:
F0 47 7F 43 65 00 04 23 00 00 7F F7
I can easily use my MIDI Universal Controller tool to test all of this.