Momentary Supercontrols Not Forcing Subcontrol Buttons To Be Momentary (1.4.2)

Question

I have a Supercontrol button set to "momentary." It activates two subcontrol buttons. When the momentary supercontrol button is tapped, both subcontrols behave as toggle buttons, staying on. Tapping the subcontrols turns them back off. I read that subcontrols take on the properties of the supercontrol, but I can't make that happen. Even manually setting the subcontrols to "momentary" doesn't work. What am I missing? Thanks.

Answer 1

Hi and thanks for your question. This is the first report of this bug we've gotten, and we did not notice it in testing. It is not working correctly in 1.4.2. 

The Workaround

The workaround is to select "force not stepper" to be ON for the supercontrol momentary button.

This will be fixed in 1.4.3. If you find other problems (or questions), please let us know.

Thanks!

Comments

I have the same problem even after upgrading to 1.4.3. The workaround does not work for me either. In my case I am chaining three deep and momentary in the middle which turns 12 faders off. Then a super control momentary that enables the middle momentary. Tapping the top momentary leaves the middle momentary "on", which also leaves it in a state where it won't work again until I press the middle momentary to turn it "off" again.

---

Do you have any other ideas for workarounds?  This bug is blocking me from using Midi Designer in my live show and the workaround suggested here is not doing the trick for me....

---

Hi hmorgan, sorry I missed this first comment. Please email me via the contact page at midiDR.com/contact and we'll figure out the bug you're having in your layout. If I have to get you into the alpha program and make a special build for you I will (though this week is tight because of NAMM).

---

also be sure to send your layout (using config->actions->mail layout) with a description of how to replicate the problem. You can use bugs [at] midiDesigner.com. Thanks for your patience as we figure this out.

---

I've just tried a bunch of variations based on your description, all of which worked well. THIS IS NOT TO SAY THAT YOUR BUG DOESN'T EXIST, but rather that I'm having trouble replicating it. Looking forward to tracking down and squashing this bug.

---

I wanted to post your suggestion which you sent by email so that others can benefit.  I changed the momentaries so that the "Snap subs to value" is none instead of 0 ms, and that fixed my problem.

---

Although thinking about this I have to wonder why that setting matters. It works fine that way, but the product would be more user friendly and less confusing if it didn't matter.  Not complaining, just trying to make a suggestion to help improve it. :)

---

You're correct. Snap subs to value shouldn't have a 0ms setting. That comes from it being a repurposed "snap to default value" slider (it's the same code). At some point I'll remove the 0ms option for snap to value.

---

Thank you much for your persistence, patience, and for following up here on the Q&A site. Best!
Dan

Answer 2

Hi and thanks for your question. This is the first report of this bug we've gotten, and we did not notice it in testing. It is not working correctly in 1.4.2. 

The Workaround

The workaround is to select "force not stepper" to be ON for the supercontrol momentary button.

This will be fixed in 1.4.3. If you find other problems (or questions), please let us know.

Thanks!