W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

MIDI Tracks and Sequences (was [Bug 18764] MIDI messages don't all have a channel, and status should be part of data.)

From: James Ingram <j.ingram@netcologne.de>
Date: Mon, 10 Sep 2012 11:32:12 +0200
Message-ID: <504DB39C.4060703@netcologne.de>
To: public-audio@w3.org, Chris Wilson <cwilso@google.com>
Hi Chris, all,

Chris Wilson said (apropos Bug 18764)
> I'd like to explicitly ask for MORE feedback from developers
> using MIDI today on this issue.
I'm following the Bug 18764 debate very closely, but don't have the 
in-depth knowledge of MIDI's finer points to contribute much to the 
subject.  All I want as a future user of this API is that it is going to 
be succinct, work as efficiently as possible and be clearly documented. 
Whether functions are overloaded or not is not really crucial. If I want 
to use the Web MIDI API, then I'm going to have to learn it one way or 
the other.

But I'd like to open another can of worms: :-)
The current version of the API [1] supports MIDIMessages and MIDIEvents. 
Would it be possible for it to provide Sequence and Track objects as 
well? I've written my own versions of these for my current project (in 
Javascript), but think there must be people out there who know much 
better how to write them than I do. They are prime targets for 
optimization. We should not all have to re-invent the wheel.
Interestingly, there are versions of these objects in Leslie Sanford's 
popular C# MIDI Toolkit [2]., so he also seems to have thought that they 
were worth providing.

Any thoughts?

Best,
James

[1] 
https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.html#callback-navigatormidiaccesssuccesscallback-parameters
[2] http://www.codeproject.com/Articles/6228/C-MIDI-Toolkit
Received on Monday, 10 September 2012 09:32:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 September 2012 09:32:52 GMT