-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle real-time MIDI SysEx messages #8119
Comments
Commented by: rryan A real-time sysex message can come in the middle of a non-real-time sysex message? Also, you said "F0 7F ... F0" -- I think you meant: " F0 7F ... F7". The page you linked terminates every message with EOX -- realtime or non-realtime. If sysex messages cannot interleave then we already interpret the real-time ones as a sysex blob since we match F0 .. F7 pairs. If they can interleave that's pretty surprising because it implies a stack or at least some slush memory -- which for MIDI processors built onto an ASIC would complicate the circuit quite a bit. |
Commented by: Pegasus-RPG Oops, yes I meant ending in F7. Typing too quick and not enough sleep last night. :) |
Commented by: rryan To follow up -- we determined that PortMIDI delivers realtime messages as a separate PmEvent, not in the middle of a message body. There's now a unit test that verifies we interact correctly with PortMIDI's API/convention. |
Issue closed with status Fix Released. |
Reported by: Pegasus-RPG
Date: 2015-06-22T14:30:52Z
Status: Fix Released
Importance: Low
Launchpad Issue: lp1467549
Tags: midi
According to http://www.midi.org/techspecs/midituning.php, universal real-time MIDI SysEx messages are of the form:
F0 7F ... F7
Add to Mixxx's MIDI handling the ability to accept these at any time (such as in the middle of any other non-real-time message, SysEx or otherwise.)
The text was updated successfully, but these errors were encountered: