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

[web-audio-api] (ConvolverNodeState): ConvolverNode state modification (#122)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:27 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/122@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17359](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17359) Tue, 05 Jun 2012 11:48:20 GMT
> Reported by Philip J├Ągenstedt
> Assigned to 

Audio-ISSUE-72 (ConvolverNodeState): ConvolverNode state modification [Web Audio API]


Raised by: Philip J├Ągenstedt
On product: Web Audio API

When buffer and normalize are modified, when does it take effect? If modifications are not applied atomically, it's possible to get spikes (or dropouts) depending on the order of setting and the previous state.

Related: https://www.w3.org/2011/audio/track/issues/28

Further, setting normalize to true is defined using the phrasing "when the buffer atttribute is set", which implies that the order of setting the attributes matters. However, no such order-dependence exists when setting normalize to false.

If an order-dependence is intended, it ought to be changed to either commit atomically after the script thread has finished, or we should have a setter taking both a buffer and a normalize flag.

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

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