See also: IRC log
<trackbot> Date: 27 March 2014
http://www.w3.org/2011/audio/track/agenda
action-97 due in 2 weeks
<trackbot> Set action-97 Start spreadsheet to triage issues for webaudio api due date to 2014-04-10.
We will be using https://github.com/w3ctag/spec-reviews/blob/master/2013/07/WebAudio.md - also split into issues in https://github.com/WebAudio/web-audio-api/issues?labels=TAGFeedback&page=1&state=open
<slightlyoff> sorry for being late
<slightlyoff> sgtm
https://github.com/WebAudio/web-audio-api/issues/254
https://github.com/WebAudio/web-audio-api/issues/66
https://github.com/WebAudio/web-audio-api/issues/268
<slightlyoff> yes
https://github.com/WebAudio/web-audio-api/issues/113 Worker-based ScriptProcessorNode
recent discussion at https://github.com/WebAudio/web-audio-api/issues/16
<slightlyoff> interesting
<slightlyoff> why is that scarrier?
<slightlyoff> both seem productive
<slightlyoff> isn't it desireable to run script audio processing in the high-priority thread from a latency perspective?
<slightlyoff> isn't that glitchy?
<slightlyoff> I see
<slightlyoff> so what?
cwilso: explains how processing works in blink ATM
<Domenic> there have been requests for that on some list somewhere...
<slightlyoff> thanks....
<slightlyoff> sorry to fill the channel
<slightlyoff> I'm not following...we're giving people power...if we need to set limits on it, shouldn't it be to cap processing time slices?
<slightlyoff> I think I need to go...will try to come back if my other meeting ends early
<Domenic> makes sense, thanks very much.
<slightlyoff> I'm sorry
<Domenic> good question
<Domenic> (maybe record that question in https://github.com/WebAudio/web-audio-api/issues/113 for posterity; it's a very helpful clarification IMO)
<Domenic> what about with complexity-in-worker AudioContext; would ScriptProcessorNode be able to run in that worker thread?
<Zakim> cwilso, you wanted to respond to Alex's cap processing time slices question
https://github.com/WebAudio/web-audio-api/issues/256
https://github.com/WebAudio/web-audio-api/issues/164
<joe> 1+
<Domenic> sounds good :)
<Domenic> agree that misunderstanding seems prevalent. love the pixels analogy.
Domenic explains the general approach about layering issue
scribe: "treat it as if it were built in javascript"
https://github.com/WebAudio/web-audio-api/issues/257
cwilso: 2 ways of looking at
layering
... is audio tag built on top of webaudio?
... and question of how webaudio itself is built
<padenot> oops, I think I messed up the timezone calculations
Domenic: agree - they are separate
<Domenic> woah that's awesome
jernoble: have draft which explains audio element in terms of webaudio
(nice!)
olivier: would that be informative? not sure how it could be made normative
Domenic: what happens under the hood should be undistinguishable
<joe> sorry, must go
<scribe> ACTION: jernoble to share draft explaining HTML audio in terms of webaudio [recorded in http://www.w3.org/2014/03/27-audio-minutes.html#action01]
<trackbot> Created ACTION-98 - Share draft explaining html audio in terms of webaudio [on Jer Noble - due 2014-04-03].
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/into/in/ No ScribeNick specified. Guessing ScribeNick: olivier Inferring Scribes: olivier Default Present: gmandyam, Doug_Schepers, +44.303.040.aaaa, Domenic, olivier, cwilso, rtoy, rtoyg, kawai, +1.617.455.aacc, Joe, jernoble, +1.415.254.aadd, slightlyoff Present: gmandyam Doug_Schepers +44.303.040.aaaa Domenic olivier cwilso rtoy rtoyg kawai +1.617.455.aacc Joe jernoble +1.415.254.aadd slightlyoff WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 27 Mar 2014 Guessing minutes URL: http://www.w3.org/2014/03/27-audio-minutes.html People with action items: jernoble[End of scribe.perl diagnostic output]