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
From the other, send the attached TestUMP_MT3.txt to UM-ONE.
Monitor USB OUT packets with a USB protocol analyzer.
Incorrect conversions of MT3/MT2 messages into USB MIDI 1.0 packets were observed.
As a result, some channel voice messages are lost and some SysEx messages are corrupt.
Actually, re-reading this, I don't think you will see any differences in DP8. We do not have sysex parking/blocking in place for this release. If one app sends notes while another sends sysex, they all end up in the output.
I will look more closely at what exactly happens with the data, but sysex collisions are an error condition right now, just as they are with most? all? vendor multiclient USB MIDI 1.0 drivers available today.
I verified messages sent to the driver from the/ MIDI stack, there were no mixed data bytes. Channel voice messages were simply inserted in the middle of a SysEx message.
Since the issue is not caused by the new MIDI stack, the situation is the same today.
I will try #60, when it becomes available.
Describe the bug
Sending MT3 and MT2 to USB MIDI 1.0 device simultaneously corrupt MIDI messages.
To Reproduce
Incorrect conversions of MT3/MT2 messages into USB MIDI 1.0 packets were observed.
As a result, some channel voice messages are lost and some SysEx messages are corrupt.
Expected behavior
No conversion issues.
Screenshots
Installer Name or Version
Desktop (please complete the following information):
Device information, if this is with an external MIDI device:
Application Information
The text was updated successfully, but these errors were encountered: