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: Mon, 03 Dec 2012 21:31:36 +0000
To: public-audio@w3.org
Message-ID: <bug-19975-5429-qZmoNCPFts@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19975

--- Comment #12 from Florian Bomers <w3c_bugz@bome.com> ---
Hi Jussi,

OK, I see the point. In particular, it can make sense to coalesce control
change messages (for many MIDI receivers, only the last control value is
significant, so you can skip previous, late, messages). But for any such
removal of messages, you must know how the receiver is interpreting the data.
For example, if the control change is interpreted as a relative movement
(delta), as rotary encoders send, you better don't coalesce such messages.

Still, it's quite an advanced usage, I'd say. Rather than cluttering up all
webmidi receivers, we could provide a method in MIDIInput like
"getQueuedMessageCount" which tells you if there are still messages immediately
following the current one. Now the basic webmidi receivers will not use it and
benefit from the simplifications proposed by Chris. And the advanced
applications can cache all queued messages until there are no queued messages
anymore, and then process them at once, possibly eliminating redundant or
outdated messages.

Would that be a solution?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 3 December 2012 21:31:39 UTC

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