<li>

Receiving short messages from [=MIDI devices=] - this

enables getting input from keyboards, drum pads,

</li>

<li>

Sending short messages to [=MIDI devices=] - it’s

devices, [=System Exclusive=] messages are

required. Some common MIDI commands are also sent as

Universal [=System Exclusive=] messages, such as MIDI

</li>

</ul>

<p>

<ul>

<li>

Sending short messages to a [=MIDI device=] - sending

&lt;audio&gt; or Web Audio. Some attached devices might

be professional lighting control systems, so it’s

possible to control stage lighting; however, this is

</li>

<li>

Receiving short messages from a [=MIDI device=] -

not cause information exposure or security issues, as

there is no identifying data being received, just a

stream of controller messages - all of which must be

initiated by the user on that MIDI device (except

clock-type messages). This is analogous to listening to

input or gamepad events; there is no additional

information exposed, and all messages other than clock

signals must be initiated by the user.

to transfer data - it has to transcode into 7-bit - so

it’s unlikely you could listen in for long periods. More

explicit fingerprinting is a concern, as the patch

uniquely identify the system. Again, this requires much

device-specific code; there is not standardized “grab

all patches and hash it” capability. This suggests that