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
The device that MIDIPort represents has not been opened, or has been explicitly closed. Until a MIDIPort has been opened either explicitly (through <code><ahref="#widl-MIDIPort-open-Promise-MIDIPort">open()</a></code>) or implicitly (by adding a <ahref="#widl-MIDIInput-onmidimessage">midimessage</a> event handler on an input port, or calling <ahref="#widl-MIDIOutput-send-void-sequence-octet--data-double-timestamp">send()</a> on an output port, this should be the default state of the device.
405
+
The device that MIDIPort represents has not been opened, or has been explicitly closed. Until a MIDIPort has been opened either explicitly (through <code><ahref="#widl-MIDIPort-open-Promise-MIDIPort">open()</a></code>) or implicitly (by adding a <ahref="#widl-MIDIInput-onmidimessage">midimessage</a> event handler on an input port, or calling <ahref="#widl-MIDIOutput-send-void-sequence-octet--data-DOMHighResTimeStamp-timestamp">send()</a> on an output port, this should be the default state of the device.
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).
The data to be enqueued, with each sequence entry representing a single byte of data.
775
775
</dd>
776
-
<dt>optional double timestamp</dt>
776
+
<dt>optional DOMHighResTimeStamp timestamp</dt>
777
777
<dd>
778
778
The time at which to begin sending the data to the port (as a <ahref="#DomHighResTimeStampDfn">DOMHighResTimeStamp</a> - a number of milliseconds measured relative to the navigation start of the document). If <code>timestamp</code> is set to zero (or another time in the past), the data is to be sent as soon as possible.
<p>A <code>DOMHighResTimeStamp</code> specifying when the event occurred.</p>
798
798
<pclass="note">The DOM4 <aclass="externalDFN">Event</a> object has a timeStamp member in the event object that will be filled out with the current time, but that it is lower precision (DOMTimeStamp is defined as an integer number of milliseconds), has a different zero reference (DOMTimeSTamp is the number of milliseconds that has passed since 00:00:00 UTC on 1 January 1970), and therefore is less suitable for MIDI applications.</p>
0 commit comments