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

[Bug 17366] (OscillatorTypes): Oscillator types are not defined

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Sep 2013 21:03:14 +0000
To: public-audio@w3.org
Message-ID: <bug-17366-5429-hcEb327iq0@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17366

--- Comment #6 from Ralph Giles <giles@mozilla.com> ---
(In reply to comment #4)
> Paul, I think that specifying the amplitude (i.e. time-domain signal) the
> way you suggest requires that an implementation does not deal with frequency
> folding.

Of course there need to ripples. But do we need to pre-duck the waveform to
avoid clipping during naive playback, or can that be a problem for content
authors? This API uses float samples, so there's no problem with excursions
beyond 1.0 in the oscnode output; it can be adjusted later by a gain node, etc.

> Also, I think that we should decide whether or not it's OK for
> implementations to use different signal generation methods (e.g. trade
> quality for performance), or if all implementations must use a specific
> signal generation method.

This is a more serious question. Do we mind if synths sound slightly different?
What about using an oscnode as an lfo, or an animation driver, like Chris
suggested? Definite values are more important then.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 3 September 2013 21:03:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:23 UTC