- From: Marcos Caceres <w3c@marcosc.com>
- Date: Tue, 25 Dec 2012 23:22:41 +0000
- To: Chris Wilson <cwilso@google.com>
- Cc: Marcos Caceres <marcosscaceres@gmail.com>, Florian Bomers <Florian.Bomers@bome.com>, "public-audio@w3.org" <public-audio@w3.org>
On Tuesday, 25 December 2012 at 23:04, Chris Wilson wrote: > The main reason send( status, data1, data2 ) didn't make it in was simply that I didn't see a strong enough need (over send( [ status, data1, data2 ], optional timestamp )). If more than one person thinks its valuable, I'm happy to add it. FWIW, I'm personally really happy with just using an array now. And I also really like that the internal behaviour is just to cast to Uint8Array. It makes everything much simpler and predictable. However, in the spec, we should add the justification that Jussi gave as a non-normative note (splits the data from the timestamp), as well as some text describing how the length of messages vary from 1 to many bytes in lots of cases (and why that is). I think that will help people like me: which don't have a strong background in MIDI but are nonetheless interested in making use of this API to either control things or just make sounds (e.g., in games, etc.). -- Marcos Caceres http://datadriven.com.au
Received on Tuesday, 25 December 2012 23:23:13 UTC