Prohibited running status; fixed leftover timestamp description in MIDIMessage description; detailed allowed contents of send() data.
--- a/midi/specification.html Mon Nov 19 11:43:17 2012 -0600
+++ b/midi/specification.html Mon Nov 19 11:57:29 2012 -0600
@@ -614,10 +614,13 @@
<p>
Enqueues the message to be sent to the corresponding MIDI port. The underlying implementation will (if necessary) coerce each member of the sequence to an unsigned 8-bit integer. The use of sequence rather than a UInt8Array enables developers to use the convenience of <code>output.send( [ 0x90, 0x45, 0x7f ] );</code> rather than having to create a UInt8Array, e.g. <code>output.send( new UInt8Array( [ 0x90, 0x45, 0x7f ] ) );</code> - while still enabling use of UInt8Arrays for efficiency in large MIDI data scenarios (e.g. reading Standard MIDI Files and sending sysex messages).
</p>
+ <p>
+ The data must contain a stream of valid, complete MIDI messages. Running status is not allowed in the data bytes, as underlying systems may not support it.
+ </p>
<dl class='parameters'>
<dt>sequence<short> data</dt>
<dd>
- The data to be enqueued, with each sequence entry representing a single byte of data.
+ The data to be enqueued, with each sequence entry representing a single byte of data.
</dd>
<dt>optional DOMHighResTimeStamp? timestamp</dt>
<dd>
@@ -637,13 +640,13 @@
<dt>DOMHighResTimeStamp timestamp</dt>
<dd>
<p>
- A <code>DOMHighResTimeStamp</code> signifying when the event occurred or should occur. For <code>MIDIMessage</code>s received by a <code>MIDIInput</code>, this is required to be set; for <code>MIDIMessage</code>s that are passed to <code>sendMIDIMessage()</code> on a <code>MIDIOutput</code>, this may explicitly be set to zero or null to represent "as soon as possible".
+ A <code>DOMHighResTimeStamp</code> specifying when the event occurred.
</p>
</dd>
<dt>Uint8Array data</dt>
<dd>
<p>
- A Uint8Array signifying the data the message contains.
+ A Uint8Array containing the MIDI data bytes of a single MIDI message.
</p>
</dd>
</dl>