The following tools are self-contained web applications which interact with attached MIDI instruments using the Web MIDI API. Each tool runs entirely client-side, depends on no resources outside the single static HTML file which implements it, and is MIT licensed for ease of code reuse.
Choose MIDI input and output ports from the drop-down selectors in the header bar, then enter complete MIDI commands in hexadecimal byte format at the prompt to send them. Received messages will be logged to the screen in green.
f0 7e 00 06 01 f7 will send a universal identity request,
which should trigger an identity reply from a compliant instrument.
The shell supports basic command-line editing including history, and the
clear command clears the log of received messages but leaves the command
The display filter drop-down narrows the recorded data to system exclusive messages, all system common and channel data, or all messages including real time bytes. Note that if enabled, real time chatter from active sensing bytes and time clock messages can result in a very large log in the browser.
transmit with an array of MIDI bytes to send that command to the
selected output. Call
receive with a listener function and an optional
timeout in milliseconds to subscribe to inbound messages as arrays of MIDI
receive is asynchronous, returning a promise which resolves when
the timeout expires or the listener returns true to signify completion.
Alternatively, add a handler manually to
subscribe to all message events, then remove it with
raw are provided to convert hex strings
to/from raw byte arrays, as passed to
receive handlers and expected by
transmit. Invalid byte representations like ‘??’ are translated by
into null entries in the array, which is useful for constructing
match(pattern, data) returns true if the start of the message in
matches the pattern array
pattern, where each element of
either a literal byte to match, or null for a wildcard byte.
A higher-level interface building on these facilities is also provided as
dump(request, start, filter, finish, timeout). This sends
request, waits for a response matching
start, then logs all responses
pattern up to and including a terminator that matches
resolving to the list of received messages after either the terminator or
timeout milliseconds have elapsed. If
start is null, logging of messages
begins immediately. If
finish is null, logging of messages continues until
reception times out.
request = raw("f0 43 20 7f 1c 02 0e 25 00 f7"); start = raw("f0 43 00 7f 1c ?? ?? 02 0e 25 00"); filter = raw("f0 43 00 7f 1c ?? ?? 02"); finish = raw("f0 43 00 7f 1c ?? ?? 02 0f 25 00"); response = await dump(request, start, filter, finish, 1000);
will request a dump of the performance edit buffer from an attached Yamaha
Montage, giving up after one second if the dump hasn’t completed. Use
response.map(hex).join("\n") to pretty-print a hex dump of the bulk data,
response.forEach(transmit) to restore the dump to the instrument.
A demonstration of automatic instrument detection, this page sends universal
identity requests on each available output in turn, monitoring every input
for a corresponding reply from a Yamaha Montage or MODX synthesizer. The
When an instrument is found,
montage.output are the
connected input and output port,
montage.model is the model detected (e.g.
“Montage 8”) and
montage.version is the firmware version (e.g. “3.0”). The
page header is updated to show the model and version detected.
As above, call
montage.transmit to send a command to the synthesizer, and
call asynchronous function
montage.receive with a listener and timeout to
receive messages from it. The corresponding higher-level
interface also exists; for example:
request = raw("f0 43 20 7f 1c 02 0e 25 00 f7"); start = raw("f0 43 00 7f 1c ?? ?? 02 0e 25 00"); filter = raw("f0 43 00 7f 1c ?? ?? 02"); finish = raw("f0 43 00 7f 1c ?? ?? 02 0f 25 00"); response = await montage.dump(request, start, filter, finish, 1000);
will request the performance edit buffer from a Montage. (A MODX would need group/model ID “7f 1c 07” rather than “7f 1c 02”.)
If no instrument is found, this is indicated in the header and the page
continues to rescan once a second. In this case,
montage.receive do nothing, and all of
montage.version are set to null.
The page will automatically initiate a rescan when the instrument’s ports are disconnected. However, it does not continuously poll when the detected ports remain up. In practice, this means that unplugging a USB MIDI cable will be detected but unplugging a DIN MIDI cable will not. Click on the status message in the header to forget the existing instrument and force a rescan.
Web MIDI has been fully supported by Google Chrome/Chromium/Blink since version 43 in May 2015, running on Android, Chrome OS, Linux, macOS and Windows. It also works on derivative browsers such as recent Microsoft Edge, Brave and Opera.
Mozilla Firefox/Gecko does not support Web MIDI as of February 2020. A third-party extension is available, enabling the API using the Jazz plugin. Work towards native Web MIDI in Firefox is slowly progressing, despite an alarming RFP discussion complete with hysterical claims that hardware MIDI users are incapable of informed consent to sysex access.
Apple Safari/WebKit also has no support as of February 2020. Unfortunately, WebKit lags behind other browser engines in implementing far more mainstream web standards, suggesting the outlook for Web MIDI is bleak. Worse, all alternative browsers on iOS must use the system-provided WebKit; Apple abuse their monopoly position as platform gatekeeper to exclude competition from better-maintained browser engines.
Plugins and extensions are not supported on iOS, so unless Mobile Safari itself switches to Blink as rumoured, Web MIDI is likely to remain locked out from Apple iDevices for the foreseeable future. The macOS build of Safari is less restricted: in theory the Jazz plugin and extension could be employed there as with Firefox, but other current WebKit deficiencies are likely to break these Web MIDI tools too.
The Web MIDI tools and this documentation are distributed as Free Software under the terms of the following MIT licence:
Copyright © 2020 Chris Webb <firstname.lastname@example.org>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
The Software is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use or other dealings in the Software.
Feel free to raid this code for useful spare parts when putting together your own Web MIDI hacks.
Please send comments, bug reports or proposed patches to Chris Webb <email@example.com>.