- From: Soledad Penades <hello@5013.es>
- Date: Tue, 7 Oct 2014 12:58:34 +0100
- To: public-audio@w3.org
Sorry, the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1078014 On Tue, Oct 7, 2014 at 12:57 PM, Soledad Penades <hello@5013.es> wrote: > Hello! > > I'm trying to simulate applying a DC signal to an existing signal. > Since the signal is already in [-1, 1] and I'm applying a variable > [-2, 2] value, the output should be quite clipped. > > Check demo here http://sole.github.io/test_cases/web_audio/bias/ - > you'll need web components enabled. > > In Firefox, although the analyser reports the signal being shifted > around when the range is changed, there is no audible difference. > > In Chrome, the behaviour is weirder--the analyser goes bananas and the > sound doesn't seem to change substantially either. > > I can definitely listen to the difference by generating a signal in > Audacity and shifting it manually (you can listen to the attachments > in the bug I opened in Mozilla's Bugzilla) > > I wonder if the audio engine is allowing values to go out of range > temporarily and finally clipping by the time sounds reaches > audioContext.destination, but I also wonder if this is a behaviour > that is not explicit in the API (or maybe I oversaw it > accidentally--would anyone be as nice as to point me to where is this > behaviour described in the specification?). In other words: I would > expect the output of each node to be clipped to -1, 1 > > Thanks! > > > > -- > http://5013.es -- http://5013.es
Received on Tuesday, 7 October 2014 13:29:00 UTC