You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I'm unable to use system exclusive on any Android device. All of the standard Midi works fine, and sending sysex is fine, but the sysex response is missing bytes.
I've tested on emulators and hardware using Android 4,5,6 and 7.
When expecting a sysex reply of 144 bytes, it often returns 141. The 3 missing bytes are at the start.
It's completely random, so sometimes it gives an incorrect response immediately, other times after no more than 5 correct responses.
I've tried increasing the thread priority in the MidiInuptDevice file, changing the sleep time, and increasing the ready buffer size, to no avail.
The comments and suggestions in this issues (#58) doesn't help.
Is sysex given less priority than standard midi messages? If so, how do I get the sysex messages to use the same priority? I only need sysex, so I'd like it to be the main priority.
Thanks
The text was updated successfully, but these errors were encountered:
Hi. I'm unable to use system exclusive on any Android device. All of the standard Midi works fine, and sending sysex is fine, but the sysex response is missing bytes.
I've tested on emulators and hardware using Android 4,5,6 and 7.
When expecting a sysex reply of 144 bytes, it often returns 141. The 3 missing bytes are at the start.
It's completely random, so sometimes it gives an incorrect response immediately, other times after no more than 5 correct responses.
I've tried increasing the thread priority in the MidiInuptDevice file, changing the sleep time, and increasing the ready buffer size, to no avail.
The comments and suggestions in this issues (#58) doesn't help.
Is sysex given less priority than standard midi messages? If so, how do I get the sysex messages to use the same priority? I only need sysex, so I'd like it to be the main priority.
Thanks
The text was updated successfully, but these errors were encountered: