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: Chris Wilson <cwilso@google.com>
Date: Thu, 2 Feb 2012 13:03:04 -0800
Message-ID: <CAJK2wqWJbsgZAj2Zz+X5MRs-0_0X9ZsDV_sO7tVWuJJosyjfww@mail.gmail.com>
To: "Tom White (MMA)" <lists@midi.org>
Cc: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>, 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
On Thu, Feb 2, 2012 at 11:32 AM, Tom White (MMA) <lists@midi.org> wrote:

> **
>
> That's what I meant about other browsers - all the other major browsers
> ship on OSX (and many on Linux, etc), where they couldn't rely on an SMF/GM
> component being available.
>
> Right... the GM component (synth) is available, just not the SMF component
> (file player). (Just want to be clear about that.)
> So if I was in a problem-solving mode, I'd be looking for some way to get
> the SMF file-player code into browsers, if not into OSX and Linux
> distributions themselves.
>

The GM (synth) component doesn't seem to be available in an easy
programmable form (e.g. as a MIDI device) on OSX (or Android, for that
matter).

Obviously, if we have the right MIDI API, a Javascript synth could install
itself in a background process and create a virtual instrument.  I don't
think I've seen any JS-implemented GM synths yet...  :)
Received on Thursday, 2 February 2012 21:03:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 2 February 2012 21:03:35 GMT