Quote:
Originally Posted by MalcolmG
Geoff, following on from our earlier discussion, the second param above is not just the light state, but more specifically, the light state when turned off. The light state for ON would be the same as the first param, so it's doing double duty as both the incoming message and the message sent back for the ON light state.
Is that right?
|
100% correct.
To make matters worse, the 2 params also act as range for faders, etc.
The syntax is still in flux and should improve with age
Quote:
Originally Posted by MalcolmG
That works fine for single colour buttons, but I was just doing some testing of the Launchpad Mini, and it allows you to specify the colour, brightness and flashing state using that last hex value. So for the button I'm testing looks like this:
MyButton PressFB 90 01 7f 90 01 0f
where the 0f in the last message represents Red, non flashing and high brightness.
The behaviour is that when the button is in an off state, it's Red, and when I press it, it goes to Yellow because 7f happens to line up with Yellow, non flashing, high brightness.
Note, none of these are being set by the controller, it's all by the OUT messages of CSI.
So for this it would be handy to be able to separately specify the On and Off state colours. Same would go for PressReleaseFB.
Does all that make sense? Am I misunderstanding something, and if not, is it possible to put this as a low priority item on the backlog?
Cheers
Malcolm
|
We've discussed this concept before (like, a gajillion pages back
), it is probably a good idea to make the syntax more verbose with a dedicated feedback set of parameters.
By doing something like that, we could eliminate the Feedback variants of the controls.
Maybe syntax something like:
Code:
Play Press 90 5e 7f Feedback 90 5e 7f 90 5e 00