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

That sounds like you would like a use case around "SMF playback, but the
developer gets to select the midi port"?

I thought about another use case/requirement being to have a "create MIDI
output that's associated with a GM playback 'device', if available", just
to make it simpler to let developers find one, but I'm still on the fence
about that.  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).

On Wed, Feb 1, 2012 at 1:08 PM, Tom White (MMA) <lists@midi.org> wrote:

> > I believe that the MIDI folks would welcome such an API, based
> > on my conversations with them.  (Please correct me if I'm wrong,
> > Tom.)
>
> Yes. (As in you're not wrong <g>).
>
> FYI, our Technical Standards Board just discussed this today and
> they agree this is an excellent opportunity for the MIDI industry
> and will ask MMA members for input on the requirements...
>
> > I also think there is interest in allowing for rendering of
> > Standard MIDI Files (SMF)...
>
> Yes, and because many (but not all) web-enabled devices include
> a local General MIDI renderer, we think accessing that would be
> a good place to start, but developers will want to be able to
> use other renderers (external hardware; in the browser; etc.).
>
> Tom White
> MMA
>
>