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

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 12 Sep 2012 20:05:12 +0000
Message-Id: <E1TBtBQ-0008Ep-Ed@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18764

--- Comment #39 from Florian Bomers <w3c_bugz@bome.com> 2012-09-12 20:05:09 UTC ---
(In reply to comment #37)
> BTW, I don't think the short form is going to be very useful for libraries,
> because it'll seriously restrict their use cases if the library doesn't support
> timestamps.

I wouldn't say that, either. Timestamps for sending is only useful for a
certain type of apps. For all interactive and realtime MIDI, it's mostly
useless. Also, you could argue that timestamps for sending data is high level,
because you can easily handle scheduling of MIDI messages in a user lib. 

Of course for receiving data, it is essential that it's submitted with a
timestamp.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 12 September 2012 20:05:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 September 2012 20:05:15 GMT