New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 613353 link

Starred by 2 users
Status: Fixed
Owner: ----
Closed: Aug 2016
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

linear or exponential ramp after setValueCurveAtTime outputs wrong value for short time on AudioParam

Reported by yotamm...@gmail.com, May 19 2016 
Chrome Version       : 50.0.2661.102 (64-bit)
URLs (if applicable) : https://jsfiddle.net/yotammann/hqf5ctgb/7/
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK 9.1.1

What steps will reproduce the problem?
(1) setValueCurveAtTime on AudioParam
(2) setValueAtTime after end of value curve
(3) (linear|exponential)RampValueAtTime after the set value

What is the expected result?

The AudioParam automation should first output the value curve then ramp to the given value.

What happens instead?

The AudioParam outputs a short blip after the setValueAtTime where it jumps up to a higher, unscheduled value. See the linked jsfiddle. The output graph shows the value of the AudioParam automation. There is a small unexpected jump in the output to a value of 1.5 at 1 second for a duration of a of about 2ms. 

Please provide any additional information below. Attach a screenshot if
possible.

Comment 1 by brajkumar@chromium.org, May 20 2016

Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Tested this issue on Windows 7 using chrome latest stable M50-50.0.2661.102 and observed the result which is shown in the first screen-shot.

Tested the same issue on previous version of chrome M45-45.0.2446.0 and observed different result which is shown in second screen-shot.

yotammann@ - Could you please confirm is the second snap-shot result is the expected one? 

Thanks!
50.0.2661.102.jpg
19.2 KB View Download
45.0.2446.0.jpg
18.5 KB View Download

Comment 2 by yotamm...@gmail.com, May 20 2016 

The expected result is the first picture without that spike at 1 second. The second image does not have the spike, but is clearly an older implementation of setValueCurveAtTime which does not interpolate between values as the Web Audio specification now describes. So the ideal outcome would be a combination of the two: the first second from the top picture and the rest from the second image.
Project Member

Comment 3 by sheriffbot@chromium.org, May 20 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by brajkumar@chromium.org, May 23 2016

Labels: -Needs-Review M-52 OS-Linux OS-Mac OS-Windows
Owner: ----
Status: Untriaged (was: Unconfirmed)
As per comment #2, Considering this is a non-regression issue seen from past M35-35.0.1849.0 across all OS platforms. Hence marking it as untriaged.
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 9 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by cbiesin...@chromium.org, Jul 21 2016

Components: Blink>WebAudio

Comment 8 by rtoy@chromium.org, Jul 21 2016

Labels: Needs-Feedback
Status: Available (was: Untriaged)
I can confirm the erroneous graph using Chrome 52.  With Chrome Dev (53.0.2785.21), the graph doesn't have the glitch at time 1.

Please try out Chrome 53.

Comment 9 by rtoy@chromium.org, Aug 17 2016

Status: Fixed (was: Available)
Based on c#8 and no feedback, I'm marking this as fixed.

If this is incorrect, please re-open or file a new issue, adding Blink>WebAudio as the component.
►

Sign in to add a comment