See also: IRC log
<ChrisL_> I reported it when Matt told me, and the systems team fixed it
<ChrisL_> This list was deactivated yesterday by mistake. It is now active again, but all
<ChrisL_> the mails sent between yesterday 20:04 UTC and now are lost.
<ChrisL_> Apologies about that.
<ChrisL_> Jean-Gui
thanks ChrisL_
I am on another call so will be just listening in for the first 20 mins
<padenot> hi
<joe> hey
<padenot> we're meeting now, right ?
<joe> yes, I'm just connecting
<padenot> ok
<padenot> I'll get to the room and join
<hongchan> hi all.
<joe> hi!
<joe> hongchan, are you guys able to join call this am?
<joe> https://github.com/WebAudio/web-audio-api/issues/10
joe what are the remaining decisions to be made padenot agree on features, test and write prose.
ChrisL whats the impace of implementaitons having different smoothing padenot sounds different, one property to guarantee is soft & hard knee
padenot always soft knee is fine the env is easy to spec + computation of gain.
ChrisL default values for gain and delay padenot delay is fixed ChrisL we should spec this as it will effect latency
padenot add audioparam to deactivate delay in some usecases.
padenot if there is no disagreement can continue what I am doing in #10, no disagreement.
joe who takes this forwards padenot 5 stages env, gain, pre delay. Gain computation is the main area or work.
padenot to take this forward.
<joe> https://github.com/WebAudio/web-audio-api/issues/13
joe is approach in #10 suitable for Noise/Gate/ expander - padenot is there a problem when the ratio is <1?
ChrisL 2 options - set of defaults, 2 node based on Compressor joe only thing not suppored in DC approach may be hysteresis
hongchan usecase for expander is more limited than noise gate. Hysteresis issue is more important for noisegate
ChrisL test the current proposal with Dynamics compressor, if it is not suitable then implement improved version in v.next
joe can we incoorporate negative ratio to test this.
joe add expander funtionality to compressor and push noise gate to v.next
general agreement
https://github.com/WebAudio/web-audio-api/issues/95
action to review PR off the call
<trackbot> Error finding 'to'. You can review and register nicknames at <http://www.w3.org/2011/audio/track/users>.
<joe> https://github.com/WebAudio/web-audio-api/issues/1089
<padenot> https://github.com/jernoble/Sound
padenot channel ordering is dependant on the underlying libraries used by the browser. Channel information is lost in the process. example aac ordering LCR vs SMPTE LRC
jdsmith can we normalise this just for the waapi? padenot yes we could spec to one standard
joe can we assert that when a media element is delivering a file, the channel mapping of the file will be employed
padenot spec for both media element and decodeAudioData
joe Shall we pick SMPTE? jdsmith will get feeback for next call
<joe> https://github.com/WebAudio/web-audio-api/issues/1099
<joe> https://github.com/WebAudio/web-audio-api/issues/1105
<joe> https://github.com/WebAudio/web-audio-api/issues/1079
joe can we/how do we improve on this
padenot this is informative - gc not observable. Maybe we should make it normative, there is behaviour here which would result in observable changes.
joe why can we not remove the informative label from the lifetime section.
joe same applies to baseaudio context lifetime section which is normative
next call 16th Feb
trackbot, end meeting
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: mdjp Inferring Scribes: mdjp Default Present: ray, HongChan, Matt, Joe, Paul, Chris, rtoyg_m, jdsmith Present: ray HongChan Matt Joe Paul Chris rtoyg_m jdsmith WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 02 Feb 2017 Guessing minutes URL: http://www.w3.org/2017/02/02-audio-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]