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

[Bug 18662] New: Setting audioparam value while there is an automation curve will cancel that automation curve and set value immediately

From: <bugzilla@jessica.w3.org>
Date: Thu, 23 Aug 2012 09:59:39 +0000
To: public-audio@w3.org
Message-ID: <bug-18662-5429@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18662

           Summary: Setting audioparam value while there is an automation
                    curve will cancel that automation curve and set value
                    immediately
           Product: AudioWG
           Version: unspecified
          Platform: PC
               URL: http://www.w3.org/2012/08/22-audio-minutes#item03
        OS/Version: All
            Status: ASSIGNED
          Severity: normal
          Priority: P2
         Component: Web Audio API
        AssignedTo: crogers@google.com
        ReportedBy: olivier.thereaux@bbc.co.uk
         QAContact: public-audio@w3.org


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 23 August 2012 09:59:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 August 2012 09:59:41 GMT