Web Audio API delayNode.delayTime limit on very short delays

[JanesConference]

Hi to everybody,

I'm currently using Web Audio API and, specifically, working with delayNodes.

If you look at this stackoverflow question, it seems that a delayNode can't handle "tight" delays (i.e. delays with < 128 samples, translated in seconds, of delayTime):

Here's what I think is the problem. I don't think the DelayNode implementation is designed to handle such tight feedback loops. For a 441 Hz tone, for example, that's only 100 samples of delay, and theDelayNode implementation probably processes its input in blocks of 128 or more. (The delayTimeattribute is "k-rate", meaning changes to it are only processed in blocks of 128 samples. That doesn't prove my point, but it hints at it.) So the feedback comes in too late, or only partially, or something.

I need to use such tight delays. So, my questions are:

• Is there a limit on delayTime under which delays are incorrectly / partially applied?
• What exactly happens when such a low delayTime is set?
• If there is such a limit under which the delayNode doesn't behave like it's expected, could this behaviour be filed as a bug?

Thank you,

Cristiano.

[JanesConference]

Any answer here?

[JanesConference]

Reported bug here: https://code.google.com/p/chromium/issues/detail?id=281230&thanks=281230&ts=1377770899

On Thursday, February 28, 2013 10:43:04 AM UTC, JanesConference wrote: