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

[minutes] Audio WG teleconference 2013-09-19

From: Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>
Date: Fri, 20 Sep 2013 07:57:57 +0000
To: Audio WG <public-audio@w3.org>
Message-ID: <AFC03050-837B-4F74-8652-77F2E854A0DB@bbc.co.uk>
Dear all,

The minutes of the W3C Audio WG teleconference on 19 Sept 2013 are online:
http://www.w3.org/2013/09/19-audio-minutes.html

I would like to NOT thank Zakim for crashing, and then picking me when asked to pick a random scribe. Bots these days have no respect for the authority of a chair. :)

The topics of the teleconference were:

* Routine admin:
All action items were kept open, and the only recent change to specs was trivial and needed no in-depth review

* Github web-audio-api Issue 127 https://github.com/WebAudio/web-audio-api/issues/127#issuecomment-24507931
There was a discussion on this issue. Paul had suggested a solution where filtering out high frequency would not be a MUST but a SHOULD, so as to avoid unwanted filtering when using mathematical oscillators. The group raised issues with this proposal, and an alternative solution was found and adopted: keep filtering required, and add an option for oscillators to be audio or mathematical.

* Behavior of source nodes on connect/disconnect http://lists.w3.org/Archives/Public/public-audio/2013JulSep/thread.html#msg1812
This is a tricky question with no obvious consensus yet. We will track it as an issue.

* ScriptProcessorNode behavior without JavasScript references http://lists.w3.org/Archives/Public/public-audio/2013JulSep/thread.html#msg1897
There was agreement that the current solution in the spec is probably the least problematic, and that we should mention in the spec (as well as in developer evangelism material) what the best practice is and how to avoid creating memory leaks in this situation.

* DynamicsCompressorNode.reduction is read-only AudioParam ? http://lists.w3.org/Archives/Public/public-audio/2013JulSep/thread.html#msg583
Chris W explained the use case for side chain compression and how it affects needs around the Compressor node. We agreed to split the solution in two: officially make DynamicsCompressorNode.reduction a read-only float, and open an issue to track the discussion around a possible future solution for side chain compression.

* Next meeting
October 3rd, same time and place.


--
Olivier





-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------
Received on Friday, 20 September 2013 07:58:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC