W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

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

From: Audio Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 16 May 2012 10:07:30 +0000
Message-Id: <E1SUb8k-00027k-8Z@tibor.w3.org>
To: public-audio@w3.org
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.
Received on Wednesday, 16 May 2012 10:07:36 UTC

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