- From: Marcos Caceres <marcos@marcosc.com>
- Date: Fri, 14 Dec 2012 20:05:39 +0000
- To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
- Cc: public-audio@w3.org
On Friday, December 14, 2012 at 7:55 PM, Jussi Kalliokoski wrote:
> Hi Marcos!
>
> On Fri, Dec 14, 2012 at 9:24 PM, Marcos Caceres <marcos@marcosc.com (mailto:marcos@marcosc.com)> wrote:
> > Hi,
> > I'm a bit confused… why does the API require a timestamp relative to some time (i.e., performance.now())? For example:
>
>
> This is to maintain symmetry with incoming messages, which have relative timestamps, e.g.
>
> // proxy
> input.onmessage = function (e) {
> output.send(e.data, e.timestamp)
> }
>
Right, but that will just result in no waiting? (ie., just means 0 as timestamps in the past don't mean anything).
What am I not getting?
--
Marcos Caceres
Received on Friday, 14 December 2012 20:06:07 UTC