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

Re: context.currentTime is not advancing on Chrome/Canary

From: Chris Rogers <crogers@google.com>
Date: Sun, 4 Nov 2012 22:27:36 -0800
Message-ID: <CA+EzO0kcduO1s1FVz2eeh2BnjMdOf73_WSB=K-08W1dhVHSFMQ@mail.gmail.com>
To: Hongchan Choi <hongchan.choi@gmail.com>
Cc: Srikumar Karaikudi Subramanian <srikumarks@gmail.com>, public-audio@w3.org
On Sun, Nov 4, 2012 at 9:39 PM, Hongchan Choi <hongchan.choi@gmail.com>wrote:

> Thank you for your attention.
>
> Just found that currentTime is increasing right after I created a node in
> the context. (Thanks Kumar! Maybe this needs to be documented as well...) I
> am using OSX and I didn't have to wait 6 seconds or so. The clock just
> started moving immediately after the node creation.
>
> Just out of curiosity, is this intentional to save resources until the
> audio graph has any node in it?
>

Yes, and it's really just a quirk of the current WebKit implementation.
 Since this is confusing people, my inclination would be to change this
behavior in WebKit.


> Best,
> Hongchan
>
>
> On Sun, Nov 4, 2012 at 4:55 PM, Srikumar Karaikudi Subramanian <
> srikumarks@gmail.com> wrote:
>
>> The "currentTime" property stays at 0 for a brief period in the webkit
>> implementation. This is most prominent on iOS6 where it can take up to 6
>> seconds for currentTime to begin updating. The way I work around this is to
>> wait using setTimeout until currentTime becomes > 0 before doing anything
>> else. On PCs, this time is negligible in most cases, but shows up as
>> multiple sounds getting triggered simultaneously on the rare occasion if
>> the page starts playing sounds at or close to load time (it is difficult to
>> get a reproducible case).
>>
>> I've just filed this -
>> https://code.google.com/p/chromium/issues/detail?id=159359
>>
>> best,
>>  -Kumar
>>
>> On 5 Nov, 2012, at 2:39 AM, Chris Rogers <crogers@google.com> wrote:
>>
>>
>>
>> On Sat, Nov 3, 2012 at 1:20 PM, Hongchan Choi <hongchan.choi@gmail.com>wrote:
>>
>>> Hello all,
>>>
>>> I was experimenting with the "currentTime" variable from
>>> webkitAudioContext but it stopped working with the newest version of
>>> Chrome(Version 22.0.1229.94)/Canary(Version 25.0.1316.0 canary).
>>>
>>> I am constantly getting "0" - is this variable going to be removed in
>>> the future?
>>>
>>
>> No, it's not going to be removed.  I just tried Chrome Canary on OSX and
>> didn't see any issues.  You might consider filing a chromium bug with more
>> platform details if the problem persists:
>> new.crbug.com
>>
>>
>>
>>>
>>> Thank you so much in advance!
>>>
>>> Best,
>>> Hongchan
>>>
>>>
>>> --
>>> Hongchan Choi
>>>
>>> Teaching Assistant / PhD Candidate
>>> Center for Computer Research in Music and Acoustics (CCRMA)
>>> Stanford University
>>>
>>> http://ccrma.stanford.edu/~hongchan
>>>
>>>
>>
>>
>
>
> --
> Hongchan Choi
>
> Teaching Assistant / PhD Candidate
> Center for Computer Research in Music and Acoustics (CCRMA)
> Stanford University
>
> http://ccrma.stanford.edu/~hongchan
>
>
Received on Monday, 5 November 2012 06:28:21 UTC

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