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

[web-audio-api] (WaveTableNormalization): WaveTable normalization in createWaveTable not clearly defined (#91)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:17 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/91@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17370](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17370) Tue, 05 Jun 2012 11:55:13 GMT
> Reported by Philip J├Ągenstedt
> Assigned to 

Audio-ISSUE-84 (WaveTableNormalization): WaveTable normalization in createWaveTable not clearly defined [Web Audio API]

http://www.w3.org/2011/audio/track/issues/84

Raised by: Philip J├Ągenstedt
On product: Web Audio API

https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#dfn-createWaveTable

"The created WaveTable will be used with an Oscillator and will represent a normalized time-domain waveform having maximum absolute peak value of 1. Another way of saying this is that the generated waveform of an Oscillator will have maximum peak value at 0dBFS. Conveniently, this corresponds to the full-range of the signal values used by the Web Audio API. Because the WaveTable will be normalized on creation, the real and imag parameters represent relative values."

This does not clearly define what normalization must be performed. Should/can the normalization be performed analytically, or should one period be generated and the maximum (absolute) value in that period be found? These approaches may not arrive at the exact same normalization level, so a sample-exact test suite would not be possible.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/91
Received on Wednesday, 11 September 2013 14:28:45 UTC

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