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

Re: Time coordinates and audio-visual synchronization ... again

From: Chris Wilson <cwilso@google.com>
Date: Thu, 3 Jul 2014 09:05:28 -0700
Message-ID: <CAJK2wqV6Ee5D1mDwBC+oYpgGQ+SNnCYSuiVWpWB5FX6__7rrMA@mail.gmail.com>
To: Joseph Berkovitz <joe@noteflight.com>
Cc: "Srikumar K. S." <srikumarks@gmail.com>, Audio WG <public-audio@w3.org>
I agree with Joe - Performance.now() is the standard for system time.


On Thu, Jul 3, 2014 at 8:53 AM, Joseph Berkovitz <joe@noteflight.com> wrote:

> Hi Kumar,
>
> My read on this is since the Web Animations draft appears to correlate
> animation timelines to Performance.now(), this issue would be resolved by
> whatever action Web Audio takes to address the current difficulties in
> relating audio context time to Performance.now().  That issue is captured
> in:
>
> https://github.com/WebAudio/web-audio-api/issues/340
>
> Best,
> …Joe
>
> On Jul 2, 2014, at 2:16 PM, Srikumar K. S. <srikumarks@gmail.com> wrote:
>
> I just came across a Google I/O talk about a proposed draft of a “Web
> Animations 1.0”
> API which already comes with a polyfill for all major browsers.
>
> http://dev.w3.org/fxtf/web-animations/
>
> How should developers go about coordinating sound precisely in relation
> to animations as declared using this API?
>
> Best,
> -Kumar
>
>
>
>
> .            .       .    .  . ...Joe
>
> *Joe Berkovitz*
> President
>
> *Noteflight LLC*
> Boston, Mass.
> phone: +1 978 314 6271
> www.noteflight.com
> "Your music, everywhere"
>
>
Received on Thursday, 3 July 2014 16:05:55 UTC

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