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 17369 - (OscillatorDetune): Oscillator.detune attribute not defined
Summary: (OscillatorDetune): Oscillator.detune attribute not defined
Status: CLOSED FIXED
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:54 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:54:31 UTC 
Audio-ISSUE-83 (OscillatorDetune): Oscillator.detune attribute not defined [Web Audio API]

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

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

https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#Oscillator

The behavior of the Oscillator detune attribute is not well defined. It seems superfluous, since the base frequency can simply be set to the desired (detuned) frequency instead of being calculated from frequency and detune.

Suggestion: drop the detune attribute.
Comment 1 Chris Rogers 2012-10-10 00:22:36 UTC 
Fixed:
https://dvcs.w3.org/hg/audio/rev/cb14c7445a27

The .detune attribute is important because common synthesis algorithms require controlling both the base frequency and a pitch offset.
Comment 2 Philip Jägenstedt 2012-10-12 12:42:59 UTC 
Question answered by computedFrequency(t) = frequency(t) * pow(2, detune(t) / 1200)
Comment 3 Olivier Thereaux 2014-10-28 17:17:29 UTC 
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.