New issue
Advanced search Search tips

Issue 666873 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Web Audio GainNode ignored in Chrome

Reported by roo...@gmail.com, Nov 18 2016

Issue description

Chrome Version       : 54.0.2840.99
OS Version: 6.3
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: OK
  Firefox 4.x: OK
     IE 7/8/9:

What steps will reproduce the problem?
1.

var audioContext = new (window.AudioContext || window.webkitAudioContext)();
var master = audioContext.createGain();
master.connect(audioContext.destination);
master.gain.setValueAtTime(0.01, 0);

var osc = audioContext.createOscillator();
osc.type = "square";
osc.connect(master);

osc.start(audioContext.currentTime);
osc.stop(audioContext.currentTime + 0.5);

2.
3.

What is the expected result?

The tone should play at a gain of 0.01

What happens instead of that?

The tone plays at full volume.

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

I have written several synthesizers using the Web Audio API and this is the first time I have observed this behavior, so it must be a semi-recent issue (within the last few months).

UserAgentString: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36



 
Components: Blink>WebAudio
Labels: -Pri-3 M-54 Needs-Triage-M54 Pri-2
Thanks for the report. Could you please provide us with a sample html testcase of the ease of finding regression.

Comment 2 by hdodda@chromium.org, Nov 22 2016

Labels: Needs-Feedback

Comment 3 by rtoy@chromium.org, Dec 5 2016

Cannot reproduce this with Chrome 57 (canary).  But this does exist in Chrome 55.0.2883.59 beta.

This issue is very likely caused by master.gain.setValueAtTime(0.01, 0) attempting to set the value of 0.01 at time 0, which is now in the past (because the context is running.)

I think there were some bugs in the automation timeline in M54 that were fixed in M55, with some recent further fixes to clamp the specified time to context.currentTime.
Project Member

Comment 4 by sheriffbot@chromium.org, Jan 5 2017

Status: Archived (was: Unconfirmed)
No feedback was received in the last 30 days from reporter "root66@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment