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

[web-audio-api] (OscillatorTypeModification): Oscillator type modification (#136)

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

Audio-ISSUE-81 (OscillatorTypeModification): Oscillator type modification [Web Audio API]

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

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

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

This issue is related to https://www.w3.org/2011/audio/track/issues/28 but with the additional complication of internal state.

May the oscillator type and wave table (for CUSTOM) be modified at any time, or should such modifications throw an exception if playbackState > UNSCHEDULED_STATE?

It would certainly be simpler to implement if an Oscillator is "frozen" once created, but it's not clear if continuously modifying the waveform is desirable for some types of effects.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/136
Received on Wednesday, 11 September 2013 14:28:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC