MIDI DESIGNER
The only MIDI controller for iPad, iPhone, and Mac


Talk to other MIDI Designer users about MIDI Designer, iOS MIDI and related topics. Or share layouts, pages, and ideas.

Check out our Facebook Group.

Of course, if you want to send us an email, feel free.

Open problem reports

Summary of user requests

Add new MDP feature to deactivate response from subcontrol

0 votes
asked Aug 1, 2021 in Suggestions (Implemented) by dsabou2062 (3,570 points)
To generalize, the proposal is for each control of type button, knob, slider, picker, crossfader, to a new option for "super control disable" - which allows selecting a button from the current page (similar to show / hide for panels).  When the selected button is active, then super controls will not impact that specific sub control.  The control is still active for manual control or midi receive.

I too would find this a very useful enhancement.
I prefer your approach since it is not tied to a panel, but can be hidden by a Show and Tell panel if so desired.
Love this suggestion and I think the utility/complexity ratio (i.e, implementation "cost") is very high. Also love the diagram in all ways.

@JK your proposal is notably different in that it's JUST super-control disable and manual would still work, as well as MIDI receive.

Don, this still covers all of your use cases, JUST blocking supercontrol-ininitiated work?
Definitely.
 Thanks,
Don
Okay got it, thank you.

Random note about this site: if you delete the name of your image (in the question) it'll be called "Image 1."
A simple question (and a simplification from a dev perspective):

What about "mute MIDI output and subcontrol downstream if a button is ON?"

This would be ONE button per control at most, but you could control those buttons from a supercontrol of course.

Thoughts?
I messaged Ulli Shenker to review your suggested approavch. I was developing the Design for him. I will also look at it and get back.
With the disable button operated by a named ticks supercontrol, this will enable advanced logic approaches.  And this is exactly parallel to the approach to show/hide.
JK so that's good, correct?

Historically speaking, the OG here is "Button off sets to default" which I use a lot, personally.
This is great! I like the wider Design Prop panel in Beta, too.
What dies OG mean? I am looking at MD Next and TestFlight. I don't see how to implement the disable button. What option has been added and to what control? Can you provide a simple layout? Thanks.
Look in the relationships tab.  You will see a new option for Disable Button.
OG is slang. Let me know if you can't find it using Google!
Thanks all, we need testing around this feature in the new Beta please. It's pretty simple but bugs do happen.
How can I add an Image and layout file to this question. If I edit it looks like it creates a new question. Is that what I need to do? Or should I create a video on youtube and add the link here?

I reported my test and pasted the image in TestFlight.

I created a layout using both the "Button off Sets to Default" and "Disable Button" features. It performs the function I originally requested, that is being able to enable and disable a MIDI Output Stream. The example layout uses one input and 3 outputs, each output being controlled independently. The only issue I have is the Control button is off when the output is enabled and on when disabled. This is the opposite to what I normally expect, button on when output is enabled. My example added an inverse button to achieve a normal button on is enabled function.
Please do NOT start a new question, you need to "Answer" instead of "Comment" for a picture or other attachment.
I agree with Don that the sense of the button should be reversed - when a disable control is selected - on = enabled.  To me, this matches the sense of show / hide - when a show / hide control is selected - on = show.  In many instances, you will need an extra INVERT button, as Don's example shows.
From an engineering perspective, this early in the game while the feature is still in beta, this is trivial to do in either way. However, I can't call it a disable button and have it turn on and enable. So the semantics need to make some better sense. Thoughts?
I guess we could do something like button off disables this control. Though that sounds ridiculous, there is some precedence for it. Which is button off sets this to default.
Since the idea is a button will enable/disable or disable/enable, rename "Disable Button" to "Enable/Disable Button". Then change the sense so enable = on as suggested by jkhiser above.

1 Answer

0 votes

Implementation of "Button off Sets to Default" and "Disable Button" features in beta


Here is the image and layout for my most recent comment.
Downloads: 155
Propoed Layoutl to switch MIDI Stream On and Off - Design described on Page 1.
Downloads: 409
Images
Proposal to switch MIDI Stream On and Off
Proposal to switch MIDI Stream On and Off
answered Mar 24, 2023 by dsabou2062 (3,570 points)
...