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

[Bug 17367] (OscillatorTypeModification): Oscillator type modification

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Jun 2012 23:03:06 +0000
To: public-audio@w3.org
Message-Id: <E1SffXm-0001dT-KT@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17367

--- Comment #7 from Marcus Geelnard (Opera) <mage@opera.com> 2012-06-15 23:03:06 UTC ---
(In reply to comment #5)
> I think it's important to support changing the oscillator type and to be able
> to set the wavetable after creation, because these are features of the
> oscillator that are important to control.  Even basic analog synthesizers allow
> this.

I agree that it's a powerful tool to be able to change the waveform type and
wavetable over time. For instance, you can use it to simulate real string
instruments, and of course for doing funky synth effects (such as Fairlight CMI
style changing-harmonics-over-time synthesis, as mentioned by Ray on the list).

However, the problem right now is that the spec does not really say anything
about timing accuracy.

I'm not opposing having the attributes modifiable - I'm just saying that IF
they are modifiable, we need to specify the behavior in more detail, including
upper and lower limits to how long it may take for an attribute change to take
effect and possibly things such as transition method (e.g. cross-fade or not)
and internal phase preservation (or not).

In other words, a Web developer must know what to expect, and similarly we must
be able to write tests for testing this behavior.

An easy-way-out here would be to make the attributes read-only, which IMO would
actually make the interface more logical, especially w.r.t the setWaveTable
method & type attribute interaction. And I believe you could implement the
mentioned examples anyway (just with a few more lines of code).

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 15 June 2012 23:03:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 June 2012 23:03:17 GMT