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

RE: Adding MIDI APIs to Audio WG Charter (was: MIDI enumeration (was: Re: getUserMedia use cases))

From: Tom White \(MMA\) <lists@midi.org>
Date: Wed, 1 Feb 2012 13:51:07 -0800
To: "'Chris Wilson'" <cwilso@google.com>
Cc: "'Doug Schepers'" <schepers@w3.org>, "'Joseph Berkovitz'" <joe@noteflight.com>, "'Robin Berjon'" <robin@berjon.com>, <public-audio@w3.org>, "'Dom Hazael-Massieux'" <dom@w3.org>, <jussi.kalliokoski@gmail.com>
Message-ID: <F9235AD4DFEC4561A44BE59A658948AD@TWTHINK>
>>> It seems like most of the "use GM" cases have been reduced in importance
by the easy use of audio files (i.e., streaming or pre-loading a
high-quality audio file isn't crazy in terms of bandwidth like it used to
be).  <<<
Yes, GM was once seen as a way for content developers to distribute music
across large platforms with minimal bandwidth... but I'm not suggesting it
for that purpose. 
I'm thinking about applications that use MIDI because they want MIDI, such
as music creation programs, music scoring programs, music training/education
programs, etc. Some of those may need custom sound renderers, but others
have been able to get by just fine with GM... and since GM renderers already
exist on hundreds-of-millions of Macs and PCs (including all new ones being
sold) I think browsers should expose them.
Tom White
Received on Wednesday, 1 February 2012 21:51:50 UTC

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