Can Keylab 88 receive LED on/off status from Mainstage?

[bigbadbobbyb]

I am using the Keylab 88 drum pads as Toggled, "Switched Controls" to turn on and off different instruments and effects in Mainstage 3.  However, the pad LEDs often get out of sync with the actual on/off functionality, so that the LEDs are lit up when the effect is Off and vice versa. Subsequent presses of the button still turn on/off the effect, but the LED is stuck "opposite" the actual control.  I can manually get them synced up by toggling on the representative buttons in Mainstage with the mouse, but then if I change patches, the software on/off buttons' status change on their own (to the saved presets of the next patch), while the LEDs remain in their current on/off state, even if it doesn't match the software.

Basically, can I have the Keylab somehow receive the on/off status of the LEDs from the software?

Just to be clear, the on/off button toggle switch works either way, its just really annoying that often times the physical LED is inverted from the actual control.

[Tausendberg]

I've been down this road before, unless someone tells me otherwise, I'm lead to understand that no, the switches can't be toggled by midi sent from DAW, which is a rather substantial oversight on Arturia's part, I hope they'll consider adding this functionality in a future firmware update because it's a relatively essential function on most midi controllers.

[pax-eterna]

+1

[bigbadbobbyb]

I've been down this road before, unless someone tells me otherwise, I'm lead to understand that no, the switches can't be toggled by midi sent from DAW, which is a rather substantial oversight on Arturia's part, I hope they'll consider adding this functionality in a future firmware update because it's a relatively essential function on most midi controllers.

Thanks for the reply.  And wow, you are right, that is a pretty big missing feature. Is there a way to contact Arturia directly and request this feature?

[Eric Barker]

Yeah, it's not that great. Furthermore, everything I'm lead to believe suggests that it would be possible to implement with a firmware update, they just haven't gotten around to it yet. Unfortunately, my host is Apple MainStage, and I don't think THEY have really thought it through either, what would be required is for some kind of sysex data to be transmitted during any patch change, and I don't see any way of setting that up, either.

So for now, I just use the buttons for universal, full project settings. Like I have a low-shelf on the master fader that gets my patches out of the way of the bass, except on the occasional occurrence where I'm playing the bassline ("Don't Stop Believing", etc). Then I just sync this EQ button when I first startup the project. But on a per-song basis where the control is within a single patch? Nope. Either I just don't use buttons, or I live with them being possibly out-of-sync. The other option I could do is with MainStage, I have all my Keylab buttons visible as on-screen toggles, and just use them for visual reference, and just set the hardware buttons as incidental, so they never stay lit.

[chiccorosso]

+1 on this! really a wanted feature to make the keylab 88 the perfect master keyboard!

[Emporio]

+1

[retroip]

You can achieve this through MIDI-ox software by sending SYSex message (to toggle led on the button) which is in middle of KeyLab and you DAW as sadly it is not built in Arturias Firmware.
I have response that there is no plan to fix this issue as I proposed.

Functional demo:
https://www.youtube.com/watch?v=C5MlEiedFlk

[Eric Barker]

I wonder if this can be used with the 6 Transport buttons as well? I've repurposed these keys for midi-channel changes in a Max/MSP patch. I can do SysEx calls through that, and would LOVE to have them display the midi channel (1-6) that I'm sending on. I wish whoever did this test would write a proof of concept, because I can't see diddly from his readout. Any documentation on what SysEx commands do what function?

[retroip]

That 6 buttons are like that 10, except, one thingIf you set this 6 buttons to CC toggle mode. LED will stay ON. This is correct functionality and those 10 are nto doing that :/ I needed to override in midiOX. Ok but regardles of this.


So you can light them on/off via sysex message. here it is:
Turn ON
F0   00   20   6B   7F   42   02   00   10   58   7f   F7
F0   00   20   6B   7F   42   02   00   10   59   7f   F7
F0   00   20   6B   7F   42   02   00   10   5A   7f   F7
F0   00   20   6B   7F   42   02   00   10   5B   7f   F7
F0   00   20   6B   7F   42   02   00   10   5C   7f   F7
F0   00   20   6B   7F   42   02   00   10   5D   7f   F7

Turn OFF
F0   00   20   6B   7F   42   02   00   10   58   00   F7
F0   00   20   6B   7F   42   02   00   10   59   00   F7
F0   00   20   6B   7F   42   02   00   10   5A   00   F7
F0   00   20   6B   7F   42   02   00   10   5B   00   F7
F0   00   20   6B   7F   42   02   00   10   5C   00   F7
F0   00   20   6B   7F   42   02   00   10   5D   00   F7

From M4l I could not achieve to send SYSex message.
The easiest would be to create custom control script from which you can send sysex easily.

[Eric Barker]

Thanks! That did it! The buttons are actually a little out of order, but pretty easy to figure out.

As for Max (if it's anything like M4L, which it probably is), I figured out how to send the SysEx messages. You used the "midiout" object with the correct device selected (keylab). The weird thing is that midiout want to see sysex data formatted as a DECIMAL list, not hex. I looked up a way of converting a hex list into a decimal list, and found that "sprintf 0x%s" converts a single hex value into decimal. You can format multiple values by just adding more "0x%s" strings. So in this case, a 12-item hex list would use an object with:

"sprintf 0x%s 0x%s 0x%s 0x%s 0x%s 0x%s 0x%s 0x%s 0x%s 0x%s 0x%s 0x%s"

Throw this object between whatever is generating the hex lists (message objects in my case) and the midiout object, and you're golden!

Anyway, THANKS, this is going to be AWESOME! Here's what I'm using it for. For my keyboard performance, I've worked out a system where I run all my midi data from my keyboard to a max patch, which then splits off the notes to an IAC bus on any number of different channels. In Apple MainStage, in a particular "patch" (song), I have my different sounds set to different midi channels. That way, at the touch of a button, I can change between totally different setups of sounds, while staying within the same MainStage patch. This channel router Max patch floats on top of all other windows in a little box in the corner of the screen, and displays which setup I'm currently on. But, the problem is I always have to look at my computer screen to see which setup I'm on, I have no feedback from my keyboard. I've setup the 6 Transport buttons on the keylab to issue "program change" commands to toggle the setup change, but now I can have them light up and stay lit for the correct setup I'm on! I dunno if this makes any sense, kinda hard to explain.

[retroip]

Glad to help.
Your suggestion is not working. I'm max newbie.

<code>
----------begin_max5_patcher----------
748.3ocyV0raaCCC9bJPeGD74rBKY2XmgcYE8RA1dBFJJbroaTgsjgrbV5J1
69jo7eI0IMIKsaWjrHok93mHE4KWdwDmEx0PoC4yjePlL4EijInrZISZELwI
OZcbVTIZni.9obwSNSazog0ZTdgBJ.QBoDzcJkU5LPqet.rmgiC49Vck5myP
wNclySv0ls+ST+NohpbtvrM3wSakVDoiWxEO9fBh01c2mN+J2oDJkUOMKndj
4dka+YZ1JKjr6EJ82WdQ8rYZ5AyAY7UvUKpzZonClqhThnbXm52GWLvwCOd+
lEhtp+0n22MtS2teqTF.qA0CfHZg8xnSYYzJH4gHsVwMNBz+UYCwzxL0ddVE
HSak2oX3IjIEOtO5YCiKWJU5C15VJkMlxby8F5WFVYD0fgZZtNjooNSMSBy8
RikMgF8ebJwJ6JeorPwE5TBy2k3R7XDpa.gxBHylQXFIzYjvPT.yO3LjQ4c7
AVdy8w.KWLSh499kPEKyyAg90rzWH2TwyRHOKqTjue2s2QfzTC.IKAEzYdFW
.wxJgdXbvX7QpTzGX8UEOJibiLKYL95Dd.Z9L7gGjzBw7P17cyVtCAUI+W17
OC8d9YwagU7XfrBTZdrwmy347dyFgmVxSR.wF96qotwXs4GOqggUz.6DMDmB
+uf1v3Msj7MyKPanMVlIUsn2aZ8fe8nYfND4GdDH4NcTFOdLJM3DRbw.QpW8
qdj.ObwQGIRe2nzTkL+eLoN6DH0lHTL6N7imS2UgjbdB2bvNmmm8XGOwPu11
ygMpy+M6657mAuOpgumVv30ULt+7PbzSngULJxiMnHq6Az21aPa1+GqItcq8
HFpUrEYVZptF2RJsseSFfjDnTyEQZtTLvJ1lF0Wzn6FNgWV2YIxR6458fwk2
g.qsA+G.tBODb48WAqlq0nhBSY7xlc1hHSxvS1mNClZWyE10d10JS8+1eoQT
jxDMpMghUJaz85vl2DcxkIfRTwaaoCwfY3O.jMJLx.
-----------end_max5_patcher-----------
</code>

This should light up first button on my keylab

My plan is to send text of actual selected scene name to my Keylab during scene changes.