Should two CCs in one message be handled?

Question

I am sending a lot of CCs to MIDI Designer as quickly as possible (to set the visual control values to match my device's), and I'm finding that some are received in messages that are 6 bytes long, and seem to be ignored (the controls are not set).

An excerpt from the log:

Message In: Cmd=176|Ch=07|Data1=009|Data2=003 | Length=3: B6 09 03
Message In: Cmd=176|Ch=07|Data1=010|Data2=002 | Length=3: B6 0A 02
Message In: Length=6: B7 00 29 B7 01 7F
Message In: Cmd=176|Ch=08|Data1=003|Data2=001 | Length=3: B7 03 01
Message In: Cmd=176|Ch=08|Data1=005|Data2=029 | Length=3: B7 05 1D

The B7 00 29 & B7 01 7F in the 6-byte message do not appear to be received as MIDI messages.

I see this behaviour when using a MIDI over Bluetooth (low energy) interface with the midimittr app presenting a standard MIDI interface to MIDI Designer on the iPad. I don't see this problem with a hardware MIDI interface (iRig MIDI). So I'm not sure whether the problem is that midimittr is not packaging the messages correctly, or that MIDI Designer is not handling the 6-byte message with two 3-byte MIDI messages in it.

Would appreciate any comments.

Thanks.

Comments

Thanks. We're still working on fixing issues present in 1.7.1 and 1.7.2... once those are done, we'll move on to this one. Looking forward to getting you working as soon as we can.

---

Looking into this today. Unfortunately the code that handles this is looking perfect and responds perfectly to unit testing... still investigating.

---

Build is being submitted to Beta now. Hopefully to you in minutes. Thanks for your patience and for tracking this down. Great find!

---

Hi, I've tested the beta and it looks good. I fired loads of messages at it from the same device that found the problem in the first place, checked the log and there were no missed messages. Great!

Thanks for fixing this. Being able to go wireless makes a big difference to me.

---

Glad to hear the good news and glad to help. When we release 1.7.3, we'll mark this as fixed. Thanks!

Answer 1

Sorry about this, it's a bug. Your message is being interpreted as a 6-byte Bank Select, even though the second relevant byte (the fifth byte) is not a 0x20. Fixing it ASAP.

And thanks for the awesome find. This bug has been in MD for years.

Answer 2

Sorry about this, it's a bug. Your message is being interpreted as a 6-byte Bank Select, even though the second relevant byte (the fifth byte) is not a 0x20. Fixing it ASAP.

And thanks for the awesome find. This bug has been in MD for years.