W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] Setting audioparam value while there is an automation curve will cancel that automation curve and set value immediately (#172)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:48 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/172@github.com>
> Originally reported on W3C Bugzilla [ISSUE-18662](https://www.w3.org/Bugs/Public/show_bug.cgi?id=18662) Thu, 23 Aug 2012 09:59:39 GMT
> Reported by Olivier Thereaux
> Assigned to 

Discussed during the group's teleconference on 22nd August 2012:

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.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:29:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC