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

Re: Limiter on audio output?

From: <gaito@g200kg.com>
Date: Tue, 26 Sep 2017 02:36:17 +0900
To: public-audio@w3.org
Message-Id: <20170926023616.4CD5.8BE7BE0E@g200kg.com>
In my test, it behaves differently depending on the browser and output
device (USB or built-in), clip or compressor is applied.

Currently, I think that the absence of regulation about the maximum
amplitude of the signal at the destination node is the cause of variations
in the implementation of each browser.

Would you like to add the following specs?
1. The input of the destination node treats the amplitude of -1.0 to +1.0
     as the maximum amplitude (0 dBFS)
2. If a signal exceeding the maximum amplitude is input,
     (Depending on the behavior of the lower layer) or (clip to the
      range from -1.0 to +1.0) or something.
----------------
gaito@g200kg.com

> There is no limiter specced by the Web Audio API.
> 
> This is likely to be an implementation bug, please file a ticket on the
> affected web browser's bug tracker.
> 
> Thanks,
> Paul.
> 
> On Mon, Sep 25, 2017 at 4:27 PM, Andre Michelle <
> andre.michelle@audiotool.com> wrote:
> 
> > Hi,
> >
> >
> > I cannot find anything in the docs, but it is obvious that there is a
> > limiter in the end of the signal chain - probably to protect the listeners
> > from loud and ugly output if something goes wrong.
> >
> > However, is there a way to disable the limiter? I understand that for most
> > web-audio-api applications it is a nice and convenient way to have your
> > output limited automatically. But we are developing a DAW where the user
> > should have full control over the signal chain.
> >
> > ~
> > Andre Michelle
> > http://www.audiotool.com
> >
> >
Received on Monday, 25 September 2017 17:33:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 September 2017 17:33:41 UTC