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 20:48:56 +0000
To: public-audio@w3.org
Message-ID: <bug-19975-5429-MrMIwosb4C@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19975

--- Comment #8 from Chris Wilson <cwilso@gmail.com> ---
(In reply to comment #7)
> What I was referring to has nothing to do with how many messages the
> underlying API gives the implementation. Let's say there's a layout
> operation that takes 250ms. During that time the underlying API relays the
> implementation multiple messages. Now the implementation can decide if it
> fires these messages in separate events or batches the messages into one

Hmm, I see. I'm not sure if letting the MIDI implementation increase the
granularity like that is a plus or a minus; you should be able to drive
multiple messages through before releasing, anyway.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 29 November 2012 20:48:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:03 UTC