Super Controls, super commands

Question

From what I understand, Controls send MIDI messages, SuperControls activate Controls.  So for each message you wish to send, a Control must exist for that message.  What I would like, is to be able to script multiple messages within a control (buttons make the most sense).  Maybe have the ability to create commands without requiring a visible button (dropdown list?).

I'm trying to create a page that contains a "favorites" for different voices.  The issue is that I have to have a button for MSB, LSB, and Voice(0-127) so we are talking about potentially 135+ controls.  My work around thus far is to create this page and put the super controls on a different page, and just never use this page.  I was hoping for a sexier way to do it :)

Comments

Could you give an example of the MSB, LSB and voice messages? I'm sure it won't help me, but just for curiosity sake, and just in case you happen to be doing something we support like NRPN.

---

So to change voices, I send three MIDI commands.  For example my "Piano" voice, I first send a Bank MSB Control Change (cc1, 63).  Then send a  Bank Select LSB Control Change (cc32, 2).  Finally I send a Program Change (pc, 0).

For some reason I can't hit all of my voices though - I'm still trying to figure out why.  On my keyboard I have a Voice Mode set of voices and a Performance Mode set of voices.  I can't get the series to work unless I manually switch back and forth on my keyboard before sending the changes.  I'm guessing I'm missing a command.

---

At least the bank msb and lsb can be combined into one message, I THINK. Send me an email on this topic and we'll see if we can figure it out. That would save you some controls, I think.

---

A lot of this question can be handled with "subcontrols send current values."

Answer 1

Hi Patrick and thanks for your message.

I feel your pain. The ability to stack MIDI Messages somehow -- starting with the basic case, which is Bank Change->Program Change and ending with your case -- is very interesting to me. For now, this suggestion is noted and on the radar. It's a slightly big deal partly because it requires substantial UI work AND model work to accomodate this. There are also some small snags--what if you receive incoming MIDI data, do I have to check all the messages associated?--which are not insurmountable but a sightly big deal. But that's my problem. Anyway...

One thing that I do, which is also massively kludgey, is to put controls physically behind other controls, or "in front of" them.

Another thing that a user does is to put the hidden controls on the pedalboard (slide up the page).

Again, these solutions are pretty hacky (non-sexy), so hopefully I'll be able to provide a solution for this problem in the next few months.

Answer 2

Hi Patrick and thanks for your message.

I feel your pain. The ability to stack MIDI Messages somehow -- starting with the basic case, which is Bank Change->Program Change and ending with your case -- is very interesting to me. For now, this suggestion is noted and on the radar. It's a slightly big deal partly because it requires substantial UI work AND model work to accomodate this. There are also some small snags--what if you receive incoming MIDI data, do I have to check all the messages associated?--which are not insurmountable but a sightly big deal. But that's my problem. Anyway...

One thing that I do, which is also massively kludgey, is to put controls physically behind other controls, or "in front of" them.

Another thing that a user does is to put the hidden controls on the pedalboard (slide up the page).

Again, these solutions are pretty hacky (non-sexy), so hopefully I'll be able to provide a solution for this problem in the next few months.