W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

Re: Feature request and a Chrome 22 bug?

From: Chris Rogers <crogers@google.com>
Date: Tue, 6 Nov 2012 12:06:02 -0800
Message-ID: <CA+EzO0kacsTXkD2QUcG89_xCMjn57e29ZA+b+HGzaw0ST-MaTA@mail.gmail.com>
To: Joseph Berkovitz <joe@noteflight.com>
Cc: Ray Bellis <ray@bellis.me.uk>, public-audio@w3.org
On Tue, Nov 6, 2012 at 11:02 AM, Joseph Berkovitz <joe@noteflight.com>wrote:

> Hi Ray,
>
> The feature request is an interesting point and it has come up before on
> the list:
>
> On Oct 3, 2012, at 10:23 PM, Srikumar Karaikudi Subramanian <
> srikumarks@gmail.com> wrote:
>
> > A gain node's gain parameter effectively serves as an envelope node if
> you feed a unity signal to the gain node. This has gotten really expressive
> particularly after connect() began supporting AudioParams as targets. Do
> you have a use case in mind that cannot be covered by such a gain node that
> would be covered by an envelope node?
>
> The suggested approach in that discussion was to do exactly what you have
> done: create a looped BufferSourceNode with a unity signal.  It only really
> needs a single sample, not 1024.
>

Actually, in WebKit, a single sample is very much less efficient than a
larger buffer like 1024.


>
> Offhand I don't know why this should not work on Chrome 22 and I don't
> know if there is a bug or not. Perhaps one of the Google folks will chime
> in.
>
> …Joe
>
>
>
>
Received on Tuesday, 6 November 2012 20:06:32 UTC

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