19976 2012-11-16 00:13:27 +0000 Allowed contents of send( data ) needs to be detailed. 2012-12-11 09:42:17 +0000 1 1 1 Unclassified AudioWG MIDI API unspecified All All CLOSED FIXED P2 normal TBD 1 cwilso cwilso jussi.kalliokoski olivier.thereaux public-audio oldest_to_newest 78378 0 cwilso 2012-11-16 00:13:27 +0000 I realized I had not explicitly detailed what can go in the data bytes in a send() call. I believe this should be effectively what can go in a MIDIPacket in CoreMIDI: A variable-length stream of MIDI messages. Running status is not allowed. In the case of system-exclusive messages, a packet may only contain a single message, or portion of one, with no other MIDI events. The MIDI messages in the packet must always be complete, except for system-exclusive. 78400 1 jussi.kalliokoski 2012-11-16 12:20:51 +0000 (In reply to comment #0) > I realized I had not explicitly detailed what can go in the data bytes in a > send() call. I believe this should be effectively what can go in a > MIDIPacket in CoreMIDI: > > A variable-length stream of MIDI messages. Running status is not allowed. In > the case of system-exclusive messages, a packet may only contain a single > message, or portion of one, with no other MIDI events. The MIDI messages in > the packet must always be complete, except for system-exclusive. Sounds good to me. 78476 2 cwilso 2012-11-19 18:00:16 +0000 Fixed by https://dvcs.w3.org/hg/audio/rev/e0f3c5871603. I actually made it "complete messages only" - i.e. sysex messages must be complete as well. Without this stricture, we would have to be more explicit about the state of the MIDI message handler (i.e., if a partial message was the last thing received, we would need to know that the next message has no valid MIDI header byte). From previous discussion, I don't believe we decided we really needed partial sysex; if so, please open another bug to track. 79907 3 olivier.thereaux 2012-12-11 09:42:17 +0000 Seeing no objection. Closing.