W3C home > Mailing lists > Public > public-audio@w3.org > January to March 2012

RE: ACTION-33: MIDI charter proposal

From: Tom White \(MMA\) <lists@midi.org>
Date: Tue, 28 Feb 2012 14:08:27 -0800
To: <public-audio@w3.org>
Message-ID: <229C68ECFB434EE286A59D0FE10BC1BD@TWTHINK>
Looks good to me, at first review.
Tom White


From: Chris Wilson [mailto:cwilso@google.com] 

My goal in proposing a MIDI API was to provide the web platform's analog to
CoreMIDI on MacOS/iOS, or the Windows MIDI api.  Here's a proposal for
charter proposal text: 

MIDI Device Communication

Some user agents have connected music devices, such as synthesizers,
keyboard controllers and drum machines.  The widely adopted MIDI protocol
enables electronic musical instruments, controllers and computers to
communicate and synchronize with each other. MIDI does not transmit audio
signals: instead, it sends event messages about musical notes, controller
signals for parameters such as volume, vibrato and panning, cues and clock
signals to set the tempo, and system-specific MIDI communications (e.g. to
remotely store synthesizer-specific patch data).  Additionally, MIDI has
become a standard for show control, lighting and special effects control.

This deliverable defines an API supporting the MIDI protocol and MIDI device
input and output selection.  This API should be defined at such a level as
to enable non-music MIDI applications as well as music ones.

Received on Tuesday, 28 February 2012 22:09:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:58 UTC