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: Thu, 14 Jun 2012 01:02:06 +0000
To: public-audio@w3.org
Message-Id: <E1SeyRq-0004vS-RF@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17367

Chris Rogers <crogers@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #3 from Chris Rogers <crogers@google.com> 2012-06-14 01:02:05 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > Yes, it should be possible to change the type or call setWaveTable() at any
> > time.
> 
> Should there be any smoothing or similar applied to the change (as specified
> for delayNode, for instance)?
> 
> Should there be a minimal delay between the change and when the effect takes
> place (e.g. if an Oscillator node is connected directly to the AudioDestination
> node, how long before the change becomes audiable)?

I don't think it's essential for the change to occur with minimal delay.  In
other words, I don't think it's as critical for this change to happen as
quickly as say a call to noteOn(0) (representing playing a sound immediately). 
I'm expecting the type will be changed as a result of some user action in the
UI (changing osc-type menu from square->sawtooth).

-- 
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 Thursday, 14 June 2012 01:02:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 June 2012 01:02:10 GMT