This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17340 - (DelayNodeSmoothing): DelayNode smoothing
Summary: (DelayNodeSmoothing): DelayNode smoothing
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 11:33 UTC by Philip Jägenstedt
Modified: 2014-10-28 17:17 UTC (History)
2 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2012-06-05 11:33:16 UTC
Audio-ISSUE-47 (DelayNodeSmoothing): DelayNode smoothing [Web Audio API]

http://www.w3.org/2011/audio/track/issues/47

Raised by: Philip Jägenstedt
On product: Web Audio API

The spec requires that "the implementation must make the transition smoothly" but does not define how.

For example, if the delay value is a sinusoid (AudioNode connected to AudioParam) or an even a linear ramp (linearRampToValueAtTime), what must happen? If the value changes fast enough, does the sound play backwards?

Related to https://www.w3.org/2011/audio/track/issues/42
Comment 1 Olivier Thereaux 2012-06-07 16:00:23 UTC
Comment from Chris Rogers, 19 May 2012:

Agreed, there are several nuances relating to this. There are several interpolation approaches (linear, cubic, sinc) and also whether to interpolate delay changes using a "doppler" approach where the delay times are interpolated, or if the interpolation is a "cross-fade" interpolation. EA has asked for the "cross-fade" technique in addition to what I consider to be the standard "doppler" technique.

I have no strong opinion if we should include the "cross-fade" approach right now, or hold that technique off for a later version of the spec (where we can add an .interpolationTechnique attribute (which will default to the standard "doppler") thus remaining backwards-compatible
Comment 2 Olivier Thereaux 2014-10-28 17:14:35 UTC
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 3 Olivier Thereaux 2014-10-28 17:17:30 UTC
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.