Buttons - Toggle vs Momentary.

Question

I have a set of 6 buttons, all tied to a single parameter, giving 6 options.  I have them connected to a knob which is a super control for the buttons allowing only one to light up at once.  Perfect it would seem.

 The trouble is that::

• each button can still be toggled on and off individually (cosmetic)
• Toggle mode does not seem to send the data in a reliable manner (having to press the button a couple of times to get the hardware to register)
• Sending the same data with toggle on and off does not cure the above problem.
• Momentary does solve the problem and the hardware never misses a beat but nothing remains highlighted and so makes it confusing to see where you left settings.

This is all using Sysex rather than CC.  What are the differences between Momentary and Toggle with regards to sending data?

Any advice would be great.

Answer 1

If I've read your question correctly, send-on-only as an option for toggle buttons will solve this problem. This is coming in 1.4.3 (still in Alpha testing, will be out by early to mid January). Let me know if this does not make sense.

Thanks for your question and for using MIDI Designer.

Comments

All makes sense and sounds pretty good.  The more I look at the data though, the more I am convinced that it's the fact that the momentary button sends 2 instructions in-a-row rather than just the 1 with toggle and somehow the message is not taken by the hardware if you see what I mean.  It may be this reason that ensures my hardware gets the message.  It's not like it was rare either. With Toggle, I got about a 60-70% success rate on pushes and 100% on Momentary.

---

Please drop me an email and I can get you on the Alpha/Beta team. It's still the same information that you'll have, but you'll have it sooner ;)

---

Will do.

  I have discovered the reason why. When you create a flick switch using supercontrols, as it switches one off and the other on, it sends both buttons of data (kind of what you would expect for a toggle but A toggle is the only way to keep the LED's lit up on your selection).  It must be this that makes my hardware glitch and not select. Simple instructions to see and hopefully I am missing something!

1. Create 2 buttons.   A and B. Both Toggle

2. Make each Sysex and in the bytes section a simple line separate of numbers . Note that each sends the same data for 'on' and 'off'

4. Make a knob, make it a Supercontrol with each button as a Subcontrol and switch between A and B using only the buttons.

I get both buttons transmitted at the same time when switching.  If there is some sort of timing issue, I suppose this could allow the previous value to remain on the Hardware Synth.

---

Timing issues are a problem on these synths. I'm not doing it for the 1.4.3 pre-NAMM release, just because it will need a LOT to testing to make sure I haven't broken anything, but I'll be offering throttled sending soon. Rainer will be happy.

---

I bet he would.  Those templates were off the map good!

Yes, so your 'Send on only' option would make me very happy :)

---

It's actually already available to the Alpha team... let me know via midiDR.com/contact or if you've sent me an email before, you know where to find me :)

Answer 2

If I've read your question correctly, send-on-only as an option for toggle buttons will solve this problem. This is coming in 1.4.3 (still in Alpha testing, will be out by early to mid January). Let me know if this does not make sense.

Thanks for your question and for using MIDI Designer.