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

Re: [web-audio-api] Mandate a useful accepted sampling rate ranges for buffers created through AudioContext.createBuffer (#119)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:44 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/119/24244344@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=21223#5) by Marat Tanalin | tanalin.com on W3C Bugzilla. Sun, 10 Mar 2013 16:37:32 GMT

"At least" should not be confused with "limited to". These are totally different things.

Current spec says "must", not "should":

"An implementation must support sample-rates in at least the range 22050 to 96000."
(https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#dfn-sampleRate_2)

That does require that the range of sample rates must be supported, but does not prevent implementations from supporting more wide range if they want / need / are able to.

There is no sense to _limit_ sample-rate range unless there are corresponding technical limitations in a specific implementation. This is completely out of the spec scope.

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

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