This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18662 - Setting audioparam value while there is an automation curve will cancel that automation curve and set value immediately
Summary: Setting audioparam value while there is an automation curve will cancel that ...
Status: CLOSED FIXED
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL: http://www.w3.org/2012/08/22-audio-mi...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-23 09:59 UTC by Olivier Thereaux
Modified: 2012-10-16 14:01 UTC (History)
0 users

See Also:

Attachments

Description Olivier Thereaux 2012-08-23 09:59:39 UTC 
Discussed during the group's teleconference on 22nd August 2012:
http://www.w3.org/2012/08/22-audio-minutes#item03

The group discussed the desired behaviour in the following scenario:

1) an AudioParam automation curve is set (via e.g linearRampToValueAtTime() or exponentialRampToValueAtTime()) 
2) during the course of the automation curve, the value is set via AudioParam.value

The question was whether 
1) the setting of that value should be ignored, or
2) the setting should be equivalent to cancelScheduledValues() (cancelling the automation curve) and setting the value

We resolved towards option 2.
Comment 1 Chris Rogers 2012-10-05 19:49:45 UTC 
Fixed in:
https://dvcs.w3.org/hg/audio/rev/79d44e3f3ced
Comment 2 Olivier Thereaux 2012-10-16 14:01:55 UTC 
New text reads well, no objection since the changeset or the discussion at the group teleconference. Closing.