Update MDP features to improve Hauptwerk Organ MIDI Controller development

0 votes
asked May 20, 2022 in Suggestions (Reviewed) by dsabou2062 (3,570 points)
“ There are quite a few iPad apps that hide the swipe button in such a way that it takes 2 swipes to activate”

Do they allow for side by side? I think we made a deal with the devil when we allowed all multitasking features but I could be wrong
See https://mididesigner.com/qa/9135/in-ipados-hide-swipe-up-bar-at-the-bottom-of-the-mdp-screen?show=9135#q9135

You provided an Apple approach, but there is a better approach IMO used in other apps that wouldn't require remembering  extra iPad steps to turn on and off.
On other apps, the first swipe (up or sideways) activates the Swipe line and then swipe up or sideways will work normally.
What is the cheapest of these apps so that I can try it out first hand?
MIDISpy is free
Just playing with MIDISpy, it does appear to do this. Strange. I'll see what I can find.
Now in Beta (from 2.3300 (202303171316)). Thanks Don for the patience and push. It was possible all along!
Hi Don,
I can understand that this solution in the new Beta is an advantage for your live-situation. But for me it is exactly the opposite. I find it annoying, if it takes 2 swipes to access the dock, for instance. I have always been happy that MD does not defer this gesture like some other apps.
For instance AUM, which is fantastic, no question. But as soon as I am in AUM, I feel like in prison. It is very safe inside, but almost impossible to switch to another app without danger. This is my experience in a live-situation.
If this feature will be implemented in the next version, it is ok for me, because there are obviously advantages in it, but I would prefer that it stays like it is.
Thanks. Right now we’re still sorting some things out with the beta.

Once we do, will decide whether to make it optional or what

Personally, I think performance time concerns take precedence here. It’s a slight annoyance to have to swipe up before you swipe, but with a Bluetooth keyboard you could use command tab and have all the advantages

We’re still considering all the angles
all right, I understand, thanks!
I worry about putting buttons too close to the swipe bar. Personally, it doesn't matter since I do not do live performances. Is there a way to make it configurable? There is an apple option to disable it completely and reenable. So this could be an approach to use in a live performance scenario, as long as there is a way to inform such users.
We are working out some kinks in our interaction with Ableton link. Then will have this feature finalized on the beta. Then we can play with it and see what we think.

Thanks everybody for the input.
I use one app requiring a double swipe once or twice a day. I got used to it and automatically double swipe. As an alternative, is a two finger swipe feasible? That should also be easy to get used to but may not be as obvious to new users.
Long story short, the only options are to turn this thing on or to turn it off. we could also have it on Just for play mode, or for both play and Design mode. as you might know by now, I rarely want to introduce options for anything, as it just adds complexity to the app. I think the right thing to do here is either play mode only, or perhaps both play and Design mode.

We'll see how it feels in the next Beta later today
The Play mode only would be great. That's the one that concerns me. Thanks.
In the latest beta 2.3300 • Allow "return" for multiline control labels (midiDR.com/qa/9185, Don again!) for Buttons works great. Saves from having to add 4 to 6 spaces or more to get a line break.

However, that was not the feature I requested. I wanted creating multiple lines using Return in a Label. Can this be done exactly as you have implemented the feature in Buttons? While the text entry appears to accept a Return for Knobs and Sliders no text appears other than the first line.

I realize there is a Multiline Label, but the font does not match the Button Label, making it unusable in my overlay scenario. Perhaps if you can make the font identical in the Multiline Label, the issue I have will go away. In fact this will be a better solution than what I originally recommended. I don't think the text entry Return approach needs to be implemented in any control other than the Button.
You know there is a multiline text toggle for buttons. Right?
Yes, but my request was to add multiline capability to "Labels" (not Multiline Labels). Your implementation allows using the return key in controls, such as buttons. The reason is Multiline Labels use a different font and don't match button labels to change the white button color to a selectable color (such as yellow) using an overlay approach.

An alternate and better approach for my scenario is to add a text color property to Buttons (and/or other controls?). This eliminates the need for an overlay, which is difficult to create and maintain during Design. This also will not affect existing designs.
What if the text color were the same as the LED color? For both on and off states?

 What if the multiline label had an option to match the font of the regular label?
Actually. For buttons it would have to be the LED color for off state and the regular color for on state.
Text color options will not work in my scenario since usually common button colors are grouped for VPO Organ Divisions. All text across divisions should be the same color.

Multiline Label with text option will be GREAT. It means one label per button instead of 2 or 3.
You list for the latest beta "Add Display Option for Bold Multiline Labels (midiDR.com/qa/9185, thanks Don)" I don't see that option. I didn't request it. I agreed to having an option to use the same font used for button labels for a Multiline Label. There is a Supersize option. Can a Std Text option be added as well to duplicate the button font?
Please wait for the explanatory video for all the new features coming in this version. Thanks.
OK, Will do.
...