Issue metadata
Sign in to add a comment
|
Web Audio API: setValueAtTime startTime clamping from 0 to currentTime appears to be broken.
Reported by
56se...@gmail.com,
Oct 7 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Example URL: https://jsfiddle.net/eao41fyc/3/ Steps to reproduce the problem: 1. Open the JsFiddle https://jsfiddle.net/eao41fyc/3/ 2. Top button should stop the tone but does not. 3. Bottom button correctly stops the tone. What is the expected behavior? Sound should stop when doing setValueAtTime(0, 0) but does not. I've copied the relevant part of the Web Audio API documentation in the JsFiddle, and below: The time at which the exponential approach will begin, in the same time coordinate system as the AudioContext's currentTime attribute. A TypeError exception must be thrown if start is negative or is not a finite number. If startTime is less than currentTime, it is clamped to currentTime. What went wrong? 0 should become equal to context.currentTime under the hood but that apparently does not happen. Doing it explicitly with setValue(0, context.currentTime) makes it work. This used to work before the most recent Chrome update. Did this work before? Yes Chrome 52. Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 53.0.2785.143 Channel: stable OS Version: OS X 10.11.1 Flash Version: Shockwave Flash 23.0 r0
,
Oct 7 2016
The clamping of the time in automation methods hasn't been implemented yet. (But coming soon). The clamping of the time is issue 622082 and is related to issue 645776 . Duping to 645776. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kkaluri@chromium.org
, Oct 7 2016Labels: -Type-Bug M-55 hasbisect OS-Linux OS-Windows Type-Bug-Regression
Owner: rtoy@chromium.org
Status: Assigned (was: Unconfirmed)