Well then you will need to create a bunch of global variables, one for each pad and then associate that pad number with what you want to send. This would need to all be done in rules. I’m not sure exactly what you want the pad to send. Do you want to change the note, number that pad sends to the application, the value, or both?
Also there needs to be some way to tell whether your pushing the pad for programming the color vs pushing the pad for sending a note. (programming mode vs running mode).
I can model it if you explain better how you want it but I would do it for just a few pads and you would need to follow that model from there to complete it unless you are looking for paid services as this would be beyond the scope of free support.
I assume that once the pad has a color programmed it stays that way and until a version of Bome MIDI Translator Pro comes out that can save variables, every time you restart the project, all of the pad color programming would be lost. I believe that persistent variables is in the works but don’t know when it will be available.
There are a total of 710 global variable that can be used, so there is plenty of space to program 128 pads.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz