W3C home > Mailing lists > Public > public-audio@w3.org > January to March 2012

Re: audio delay node max delay time

From: Yotam Mann <yotammann@gmail.com>
Date: Wed, 15 Feb 2012 17:55:21 -0800
Cc: public-audio@w3.org
Message-Id: <200F88BD-DCA3-40DB-B606-11FF28A4F7EB@gmail.com>
To: Chris Rogers <crogers@google.com>
Thanks for the reply Chris. 

Seeing as how the delayTime is an AudioParam node, why not just expose some of the attributes of that node to allow developers to tweak the maxValue, minValue, defaultValue, etc?

The AudioParam is turning out to be one of the most crucial nodes for my work with web audio, so I would personally like to see more functionality come out of that. 

As far as an upper limit on delays, I don't see a need given that you have some performance monitoring written into the spec and i could see potential uses for really long delays.

Thanks again for your work on web audio. it's turning out to be really useful and exciting. 

On Feb 15, 2012, at 4:01 PM, Chris Rogers wrote:

> On Wed, Feb 15, 2012 at 11:30 AM, Yotam Mann <yotammann@gmail.com> wrote:
> I am wondering why the maximum delay time allowed is 1 second for the DelayNode object. There is a note that says that time is arbitrary.
> is there anyway to get around that limitation other than stringing a series of delay nodes together?
> Hi Yotam, we could potentially fix this limitation by allowing the maximum delay time to be specified in the "constructor":
> So the AudioContext createDelayNode() method could take an optional max delay time which is greater than 1 second.  Although this value could be somewhat greater than 1 second, we mChris Rogers <crogers@google.com>ay want to consider some reasonable (but large) upper limit, since it does consume memory.
> Chris
Received on Thursday, 16 February 2012 01:55:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:57 UTC