I think support for Sequences would be useful (and easy to
provide), even if we are not talking about file output.
Loading sequences from files is very common in MIDI programs, and
I see no reason why that should not be done on the web. So it
would be nice to have a standard Sequence definition with which to
work. I'm not saying that Sequences necessarily have to be loaded
from SMFs, but if the Sequence definition existed, it could
obviously be given a loadFromSMF(url) member function.
Also, if we had a Sequence object, it would wrap the output
device, and play(), stop(), rewind() etc. functions could be
provided quite cheaply out of the box. That might make Web MIDI
even more attractive. :-)
But maybe I'm too close to the problem. Is there anyone else out
there who needs to send a Sequence to the output device?
A side note: the current spec has the notion of MIDIEvent as a DOM
event that occurs when MIDIMessage(s) are received.
The toolkit you're referring to deals both with MIDI files (SMF)
and MIDI devices. Our API is designed to work with just devices,
and MIDI devices are just I/O, there's no notion of high level
concepts such as tracks (although there's channels, but that's
already in the spec) or sequences, unlike SMF does. It would seem
a bit weird to me to complicate the spec with such high-level
concepts as we don't even support reading / writing SMF files, nor
do I think we should as the intent of the device is explicitly to
allow communication with MIDI devices.
On Mon, Sep 10, 2012 at 12:32 PM, James Ingram <email@example.com> wrote:
Chris Wilson said (apropos Bug 18764)
I'd like to explicitly ask for MORE feedback from developers
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.
using MIDI today on this issue.
But I'd like to open another can of worms: :-)
The current version of the API  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
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 ., so he also seems to
have thought that they were worth providing.