Is there a way to send subcontrols only when super control is activated?

Question

I have some crossfaders that are subcontrols to a button. I'd like to be able to adjust the crossfaders without sending any values until their supercontrol button is tapped.

Is there a way to do this? I'm not sure I understand all the "options as subcontrol" or "B Control" elements. Is that where I might find the solution?

Comments

Hi, right now there's no way to do this. However, you can set the supercontrol so the subcontrols sends the current value (either set the sub or set the super). This will do some of what you need, but not all. What do you want this for, to understand the feature request?

Thanks!

---

Thanks. I have set them to send current value, so at least I was on the right track there.

I'm using these as customizable cue buttons for a lighting system. The system receives three CC messages (bank, cuelist, cue step) to run a cue, and I've set up the sliders to "dial in" any bank, cue, or step I need. Problem is as soon as I set the step the cue is activated. I'd like to be able to set them, and later run the cue with the push of a button.

I'm getting around it now simply by disconnecting, setting my custom sliders, then connecting again and I'm good to go. The question was more of a "am I missing something" question than anything else.

---

No matter how much I think about this, I cannot find a solution in MIDI Designer as it is currently. I think I might need to add an option.  And I hate options. This one would be particularly ugly, because it has to be, "subcontrol only sends value on supercontrol movement." I'd be open to better suggestions ;)

---

Actually, scratch that. I might also consider making an "off" switch for controls. Kind of like "button off sets this to default" but probably using the supercontrol-sub paradigm.

---

My workaround is not a problem and it's definitely not a limitation of the app. After all why wouldn't a control send the message when you use it?

I really appreciate your responsiveness to user suggestions and questions. Don't knock yourself out with extra options you don't think a good number of users would take advantage of.

---

Surely it would be quite easy to add a toggle to a Supercontroller to delay sending any data from it or any of its child controls until the toggle is released? This would work well with Supercontrollers that have complex arrays of child controls assigned, especially where convoluted sysex strings need to be sent.

---

Thanks for that, muckleberry. I like this suggestion. It would be something like a "send lock" toggle super...

---

Since we're talking about adding options (which you mentioned you hate) I'd prefer something a bit simpler, similar to what you mentioned in your earlier post, such as "Only Supercontrol triggers subcontrols"

The toggle idea sounds OK, and it could be useable in several situations, but setting and releasing a toggle wouldn't quite fit what I was hoping for. I don't necessarily want to delay sending data until a toggle is released. Instead I'd just prefer only the supercontrol to trigger the subcontrols. In other words, tell a subcontrol not to send at all unless its supercontrol is manipulated.

If a toggle is used, a button setting that simply turned on/off sending MIDI would be easier than my workaround of disconnecting/reconnecting.

---

So I'm back to request this one more time, bumping this thread. I've thought about where it would work best, and think it would be great if "Option as Sub" included a "Send Only with Supercontrol" setting. As I said, I'm working around this, but it would be nice to be able to set multiple sliders and knobs to desired settings, then send with a push.

---

So it's like "send current value" but it's "only send current value" or something? If you don't mind, please check "send current value"

http://i.imgur.com/kcyM7W3.png

and let me know if that's the idea except that it's:
1) for buttons too
2) ONLY for when the supercontrol changes

Thanks!

---

"Send current value" is already selected, and that works as expected. That's actually half the equation, since without that option I don't think my request would work. It's predicated on the idea that a slider is first set to a value, then that value is sent later by a supercontrol.

What I'm hoping for is option 2 in your last comment. An option for subcontrols to be sent ONLY when the supercontrol changes or is tapped.

In other words, the subcontrols can be manipulated but no message sent yet. Then, (in my example) a supercontrol button sends the subcontrols with one tap.

A choice within "Options as Sub" seems to me the place that this option would make the most sense.

Here's a lighting example: I may have several lights each receiving values from a slider subcontrol. I'd like to set each light's slider to a specific value without the lights changing, then change the scene to those values on cue with the push of a supercontrol "Go" button.

I appreciate your kicking this around. I just hope what I'm saying makes sense. If it's something you decide is not worth it or worthy, I've got no problem with that. This app has more than delivered.

---

As luck would have it, we have TONS of room on the Options as Sub page, and that is a thing we consider strongly when adding options.

What your saying makes perfect sense, and with the lighting example even moreso.

Thinking out loud here: is this separate from Send Current Value, or an add-on to it (e.g., can this work without Send Current Value being on)?

Also: this is only for knobs, sliders, etc., right?

---

Okay, this is coming in for MIDI Designer 1.6.6 Beta 02 (in about five minutes). #inspired