W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Comments on draft MIDI API

From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Date: Wed, 27 Jun 2012 02:06:31 +0300
Message-ID: <CAJhzemW70c+tXo-vE+7todnZ0iKYCQPvcSF2TqYxcXWdWAy7yw@mail.gmail.com>
To: TJ <zoomclub@gmail.com>
Cc: Adam Goode <agoode@google.com>, Dominique Hazael-Massieux <dom@w3.org>, public-audio@w3.org
AFAICT, MIDI Tuning [1] defines tuning messages as SysEx messages, which
are quite supported by the API. So it's up to the synth in question (or
framework) to decide whether it implements this feature or not. Hopefully
it will, because I'm a world music lover myself (I particularly enjoy the
Esfahan scale).

Cheers,
Jussi

[1] http://www.midi.org/techspecs/midituning.php

On Tue, Jun 26, 2012 at 10:18 PM, TJ <zoomclub@gmail.com> wrote:

> How are microtonal scales being supported?
>
> One would hope that the W3C will build an API worthy of all world music,
> see all the Scala scales available :
>
> http://www.huygens-fokker.org/scala/
>
> Oh, yeah, using pitchbend messages is poor way to handle this. The MMA has
> worked out the right way to do this in their tuning spec eons ago. Its
> likely the opportune time to support it.
>
> Thom
>
>
>
> On 2012-06-26, at 1:43 PM, Jussi Kalliokoski wrote:
>
> I've made a few changes based on the feedback [1]. I didn't yet add any
> events to the MIDIAccess interface, I'll need to think more about what
> events it should have and what don't make sense in the context of web apps.
>
> I'm also thinking about changing the MIDIMessage into a dictionary as Dom
> originally suggested. Dom, wouldn't it actually mean that for example with
> sendMIDIMessage(MIDIMessage msg); you could use an EcmaScript Object that
> would have those properties instead of it having to be an actual instance
> of a MIDIMessage? I can see added ease of use in this, but then again, it's
> used in the MIDIEvent as well, so it's a bit problematic.
>
> Cheers,
> Jussi
>
> [1] https://dvcs.w3.org/hg/audio/rev/563ce3b94a68
>
>
>
Received on Tuesday, 26 June 2012 23:07:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 26 June 2012 23:07:20 GMT