Re: inbound MIDI system exclusive processing
Posted: 04 Apr 2013 01:45
Thanks for the response.nick_liine wrote:Hi guys,
I've done a few tests. Did not experience the Lemur app freezing however, but I can confirm there seems to be some issues with long SysEx messages with certain hardware interfaces.
iRig MIDI — Confirmed that receiving SysEx is also problematic. SysEx messages are truncated to the first 2 bytes.
iConnect MIDI — Inconsistently truncated, especially with long messags (over 200 bytes).
Lemur Daemon — SysEx messages received flawlessly, up to 248 bytes (included 240 and 247 bytes),
Best,
Nick
I have heard reports that the iRig MIDI provides 100% reliable incoming SysEx communication if the MidiBridge IOS app is used to pass messages between the Lemur app and the iRig interface. I don't have an iRig otherwise i would try the combination.
Why would this make a difference? My theory is that MidiBridge buffers the incoming SysEx message, and once MidiBrige has the complete message in the buffer, it sends the complete message to Lemur. Lemur sees the full message because it arrived in a very short interval of time.
Finally, I should mention that when using the Lemur Daemon there still is a problem if there is a MIDI interface and MIDI cables somewhere in the path between the Lemur app and the hardware it is controlling. It seems the Lemur Daemon passes the USB MIDI messages at the rate they are received, even if the message is a fragment of the larger sysex message.