First Send Broken in MD 2.5! #fixed

Question

Email from user yesterday

Hello, for heavens sake, what did you do???  Today I updated MD to version 2.5.0 and now all of my Programm Change buttons (and there are a lot of them) don't work properly any more. After loading the App all of the Prog Change Buttons do not send any message by the first touch, I have to touch the button a second time.  After doing so the button then turns back to its "normal" funktion, meaning that from then on a PC message is sent by a single touch. This I did with all of my PC buttons and everything behaved as expected. However closing the MD and starting the app again, I got the faulty behaviour again.  This makes MD totally unusable!!! Do something!

Answer 1

2017-01-04 11:22 Update
2.5.2 fixes this issue for automatic send-on only controls (momentary program change buttons, for instance).  See the Change Log

---

2016-12-15 10:59 Update
Fixed and pushed with 2.5.1

---

2016-12-14 10:39 Update
Fix is now in review for App Store release for MDP2! See the Change Log entry here.

---

2016-12-12 14:09 Update
First fix sent to Beta today.

---

2.5 includes a fix to avoid the first send (on start) of all controls. However, judging from your message, there's a mistake in the fix. What you've said makes sense given the implementation details of the fix (all controls get marked as "don't send next" and then they all get unmarked on first send, which apparently never happens to your controls)

(Side note: All PC buttons are automatically (and forcibly) send-on only.)

We're working on a fix that should be out by Friday. In the meantime, you've got these workarounds:

1. Tap Config -> MIDI -> Send All
2. You can make a regular button on your layout that does this, too (subtype)

These are just workarounds. A fix is coming soon.

Comments

It's a boy! This page is just those broken controls extracted from your layout:  http://mididesigner.com/blah/QA-5416-again.mididesignerpage

I still don't know what's up, but I'll see what I can find. I might have to actually look at the code if this black-box stuff fails, but I'll try not to.

Thanks!
Dan

---

Okay, so if you make the PC button a toggle instead of a momentary, it works. Please confirm that this "fix" works in your layout, too. Thank you.

---

Yep, that works! Because of the toggle status of the PC button, I get a PC0 when each previous supercontrol button is "unpressed" in the array, but the subsequent CC0 + PC then goes through (on the first button press). It causes the receiving app (Thumbjam in this case) to load the first preset in between each PC message (because it receives what it sees as a "PC 0" command). Luckily, Thumbjam doesn't pop or squeak as it changes presets, so this isn't a problem. Just FYI, it could be a problem for situations where that PC0 message causes the receiving app/hardware to do something weird.

Thanks for the help!

---

Thank you. I'm going to put this on the "maybe fix someday" side... The problem with making a platform -- which this has become, but the idea was to just make a MIDI controller back in 2011 -- is that fixing one person's use-case might break another. But this might have an obvious fix, but at least: 1) you're up and running and 2) the fix is definitely not urgent (because it doesn't affect too many users, methinks).

Remember to CONSIDER leaving an amazing review for 2.5.1, but most importantly, enjoy and happy holidays!

Thanks!
Dan

---

Doh, toggling "Send On Only" on the PC buttons stops the extraneous "PC0" messages as each previous button toggles off. As you mentioned, the PC buttons didn't default to "Send On Only", so I needed to change them all

Answer 2

2017-01-04 11:22 Update
2.5.2 fixes this issue for automatic send-on only controls (momentary program change buttons, for instance).  See the Change Log

---

2016-12-15 10:59 Update
Fixed and pushed with 2.5.1

---

2016-12-14 10:39 Update
Fix is now in review for App Store release for MDP2! See the Change Log entry here.

---

2016-12-12 14:09 Update
First fix sent to Beta today.

---

2.5 includes a fix to avoid the first send (on start) of all controls. However, judging from your message, there's a mistake in the fix. What you've said makes sense given the implementation details of the fix (all controls get marked as "don't send next" and then they all get unmarked on first send, which apparently never happens to your controls)

(Side note: All PC buttons are automatically (and forcibly) send-on only.)

We're working on a fix that should be out by Friday. In the meantime, you've got these workarounds:

1. Tap Config -> MIDI -> Send All
2. You can make a regular button on your layout that does this, too (subtype)

These are just workarounds. A fix is coming soon.