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

[Bug 17697] Limit total volume

From: <bugzilla@jessica.w3.org>
Date: Thu, 16 Aug 2012 18:55:25 +0000
Message-Id: <E1T25E5-0006Hl-Vp@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17697

Chris Rogers <crogers@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |crogers@google.com

--- Comment #6 from Chris Rogers <crogers@google.com> 2012-08-16 18:55:25 UTC ---
(In reply to comment #4)
> For what it's worth, we have already received bug reports that certain demos
> (like Jussi's http://niiden.com/orbisyn/ demo) cause deafeningly loud noise in
> the current shipping versions of Chrome and Safari for the Mac.  The output is
> so overwhelmingly loud that the system volume controls have no apparent effect.

This part "system volume controls have no apparent effect" seems like an
important clue to try to fix this problem.  I'm guessing that what we need to
do in the AudioDestination is to clip the final output to 0dBFS (a range from
-1 -> +1).  This is supposed to be the clipping point anyway, so I'm interested
if this helps fix the problem.  I'm guessing that the rendered audio signal is
so "hot" that even with drastic gain reductions using the system volume
control, it won't help...



> 
> So, while conceptually this is a task for the OS to regulate, UAs will have a
> great deal of pressure to add some kind of volume check to the WebAudio API. 
> The question is, will this limit be part of a spec or not.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 16 August 2012 18:55:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 August 2012 18:55:34 GMT