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

Re: [Web MIDI API] send() timestamp

From: Chris Wilson <cwilso@google.com>
Date: Fri, 14 Dec 2012 11:41:30 -1000
Message-ID: <CAJK2wqVLb3tx+-Xbxhxu4nhT4qJD0-aXc1_H7=HYb4Fpprpv8Q@mail.gmail.com>
To: Marcos Caceres <marcos@marcosc.com>
Cc: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, "public-audio@w3.org" <public-audio@w3.org>
On Fri, Dec 14, 2012 at 11:33 AM, Marcos Caceres <marcos@marcosc.com> wrote:

> >for example, if you're recording the MIDI messages from a live piano
> controller, you will want the subtleties of that timing recorded - you may
> have some lag when passing through to send(), but when playing back that
> recorded sequence later, your timestamps will be more precise.
> Hang on… I'm seeing what you are saying, but this seems like a strange way
> to achieve the desired outcome… if the idea is to hook device A to device B
> through some communication port (in this case we are using send), then it's
> better to do this directly. At the moment, we have basically this:
> input.addEventListener("message",function(e){output.send(e.data)})
> When what we really want is:
> input.connect(output);
> So you can bypass the JS layer and get realtime communication.

No, you're misunderstanding what I'm saying - it's rare, IMO, that you
would want to do this.  That's my point - most of the time, you will be
recording and processing that data, but frequently you'll be recording it
relative to a "sequence clock" - so you'll need high precision.
Received on Friday, 14 December 2012 21:42:03 UTC

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