W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 19975] Promote data and timestamp onmessage/MIDIEvent, get rid of MIDIMessage altogether?

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Nov 2012 19:08:08 +0000
To: public-audio@w3.org
Message-ID: <bug-19975-5429-9bW2cxBoRC@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19975

--- Comment #6 from Chris Wilson <cwilso@gmail.com> ---
(In reply to comment #5)
> > when on at least some systems (Windows), you'll only ever receive (and thus,
> > dispatch to the Web MIDI API) one message at a time.
> 
> Like I said, this may not be true even for Windows, because you might
> receive several messages during the main thread being blocked, so these can
> be stacked into a single event.

How are they stacked into a single event?  We must not be looking at the same
MIDI APIs.  AFAICT, even in the questionably-deprecated DirectMusic MIDI API,
short (non-sysex) messages are sent back one at a time:
http://directmidi.sourceforge.net/documentation/creceiver.htm#CRRecv2.  Note
that I haven't developed Windows MIDI s/w for a long time, though, so if I'm
missing the right API, please point me in the right direction.

(In the old-school Windows MIDI APIs, messages are sent via MM_MIM_DATA
messages - also one at a time.)

> Yeah, it's probably not something we should worry about right now. Although,
> even without any interesting APIs you can do stuff like arpeggiating MIDI
> messages, which would be more reliable if it's done in a worker.

That's an excellent example!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 29 November 2012 19:08:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:14 UTC