Bug 107250 - Web MIDI API
Summary: Web MIDI API
Status: ASSIGNED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Takashi Toyoshima
URL:
Keywords: WebExposed
Depends on:
Blocks:
 
Reported: 2013-01-18 02:42 PST by Takashi Toyoshima
Modified: 2020-06-22 22:43 PDT (History)
22 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Takashi Toyoshima 2013-01-18 02:42:20 PST 
This is a master bug for implementing Web MIDI API in WebCore.

W3C TR: http://www.w3.org/TR/webmidi/
Latest editor's draft: http://webaudio.github.com/web-midi-api/

This component will be implemented in "WebCore/Modules/webmidi" with ENABLE(WEB_MIDI) flag.
Comment 1 Michael Cuthbert 2018-03-25 05:56:26 PDT 
This feature becomes much more urgent because of the change in Technology Preview 52 disabling NPAPI extensions other than Flash, because the NPAPI Jazz-MIDI plugin was previously the principal way of accessing MIDI in Safari.  Music notation related sites such as Noteflight and artusi.xyz are likely to start recommending users move to Chrome to use MIDI input in the browser.
Comment 2 Jean-Philippe Côté 2020-05-16 11:52:09 PDT 
The Web MIDI API brings tremendous value to the music world. Chrome and Edge already have support. Firefox support is in the works. It just feels natural for Safari to also provide support for this great API.
Comment 3 Jack Schaedler 2020-05-17 07:23:48 PDT 
It would be wonderful to see WebMIDI implemented in Safari. Especially if it came paired with an implementation of AudioWorklet. This would allow developers to create musical instruments and experiences in the browser on iOS with low-latency and a variety of musical input devices. Personally, I'd find an initial implementation without sysex (this is a security concern for some browser vendors) to be incredibly useful.