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

Re: [web-audio-api] (AudioParamSampling): AudioParam sampling is undefined (#142)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:57 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/142/24244509@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17399#8) by Philip J├Ągenstedt on W3C Bugzilla. Fri, 15 Jun 2012 15:52:03 GMT

If defined in seconds, (In reply to [comment #8](#issuecomment-24244507))
> Was it decided to specify sampling in terms of the number of samples instead of
> a time duration?

Nope, it's still an open issue here and for enforcing minimum delays in loops.

> I prefer the use of a time duration (gives the implementation more flexibility
> to be sample-rate-independent), and I thought the discussion on the mailing
> list about the minimum delay for DelayNodes was heading that way.

What do you mean by sample-rate-independent in this context?

If two implementations running at the same sampling rate don't sample AudioParam at exactly the same interval (in samples) then they won't sound the same. My favorite example is when the AudioParam is a high-frequency sine wave, where the result of sampling every n samples and every n+1 samples may be audibly different. I think that in order to define the sampling in terms of seconds, the AudioParam must also be correctly down-sampled to avoid this.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/142#issuecomment-24244509
Received on Wednesday, 11 September 2013 14:36:42 UTC

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