ISSUE-72: (Bugzilla 17359) ConvolverNode state modification

ConvolverNodeState

(Bugzilla 17359) ConvolverNode state modification

State:

CLOSED

Product:

Web Audio API

Raised by:

Philip Jägenstedt

Opened on:

2012-05-16

Description:

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.

Related Actions Items:

No related actions

Related emails:

1. [web-audio-api] (ConvolverNodeState): ConvolverNode state modification (#122) (from notifications@github.com on 2013-09-11)
2. Re: Summary of issues (from crogers@google.com on 2012-05-22)
3. Summary of issues (from mage@opera.com on 2012-05-22)
4. Audio-ISSUE-72 (ConvolverNodeState): ConvolverNode state modification [Web Audio API] (from sysbot+tracker@w3.org on 2012-05-16)

Related notes:

Display change log