- From: Doug Schepers <schepers@w3.org>
- Date: Wed, 29 Feb 2012 16:13:05 -0500
- To: "Tom White (MMA)" <lists@midi.org>
- CC: public-audio@w3.org, Philippe Le Hegaret <plh@w3.org>
Hi, folks- This looks good to me, and since it also looks good to Tom White from MMA, if we don't hear any other feedback within the next week, I will create a draft of the charter that incorporates Chris' wording for the MIDI API deliverable, and start the process of W3C team and member review. Thoughts? Regards- -Doug On 2/28/12 5:08 PM, Tom White (MMA) wrote: > Looks good to me, at first review. > Tom White > MMA > > ------------------------------------------------------------------------ > *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. > > > -Chris >
Received on Wednesday, 29 February 2012 21:13:18 UTC