trackbot, start meeting

<rtoyg_m2> Issues: https://github.com/WebAudio/web-audio-api/issues?page=1&q=is%3Aopen+is%3Aissue+label%3A"Feature+Request%2FMissing+Feature"

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1427

Continuing with triage of feature requests for V2

<scribe> scribe: mdjp

<rtoyg_m3> https://github.com/WebAudio/web-audio-api/issues/1165

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1098

1165 - resolution. If required, should be proposed with use cases and considered as another node.

back to 1098

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1059

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/938

1059 - for consideration, mdjp to discuss with aes and authors

938 Under consideration for V2, requires further engagement with developers.

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/923

Under consideration for v2

https://github.com/WebAudio/web-audio-api/issues/834

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/834

Idea for option to allow direct convolution of multichannel IRs - under consideration for V2

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/786

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/786

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/785

<hoch> https://www.york.ac.uk/sadie-project/

again mdjp to contact experts to allow discussion of hrtf loading in the community group

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/543

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/496

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/468

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/373

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/371

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/313

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/301

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/296

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1662

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+milestone%3A"Web+Audio+v.next"

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/2048

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/2046

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1985

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1968

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1944

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1934

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1912

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1910

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1886

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1872

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1846

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1812

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1806

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1780

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1749

<rtoyg_m2> Same room. Kashi

<rtoyg_m2> Just got back from break

https://umenohana-restaurant.co.jp/shop-list/umenohana/%e6%a2%85%e3%81%ae%e8%8a%b1-%e7%99%be%e9%81%93%e5%ba%97/

<rtoyg_m2> ADC

<rtoyg_m2> hoch: What to do about user-selectable render size in AudioContext vs ADC

<padenot> https://github.com/WebAudio/web-audio-cg/blob/master/audio-device-client/explainer.md

<rtoyg_m2> Long discussion on what user-selectable size can do and use-cases

<rtoyg_m2> sangwhan here to overview ADC.

<rtoyg_m2> hoch: Gives overview of explainer

<rtoyg_m2> hoch: Including sample code

<rtoyg_m2> sangwhan: Looks reasonable.

<rtoyg_m2> padenot: Question is if ADC is necessary since it takes work to add a new API. But ADC is relatively small (when compared to WebAudio)

<rtoyg_m2> sangwhan: What he sees is that API is fine from TAG. Is ADC behind permission

<rtoyg_m2> hoch: Yes.

<rtoyg_m2> sangwhan: Question: Is there two permissions? One for enumeration, one for creating ADC?

<rtoyg_m2> hoch: Good question, but we ask for input, so permission is required for input access.

<rtoyg_m2> sangwhan: Do we want formal TAG review

<rtoyg_m2> hoch et al: Yes

<rtoyg_m2> sangwhan: Last question: What about WebMIDI?

<rtoyg_m2> padenot: FF has most of the code, but lacks backend code.

<rtoyg_m2> padenot: Lack resources to implement backend, but creating roadmap and potential partners. As cwilso says, a second implemention changes everything

<rtoyg_m2> padenot: Willing to ship everything except sysex due to security issue.

<rtoyg_m2> padenot: Back to user-selectable render size

<rtoyg_m2> padenot: Need more community involvement

<rtoyg_m2> ruth: Can contact more people for CG involvement

<rtoyg_m2> padenot: Really great to get diverse set of people/companies

<rtoyg_m2> padenot: Like pro audio, games, playback, teleconf

<rtoyg_m2> mdjp: What about web developers working group?

<rtoyg_m2> (Oops: web audio developers community group)

<rtoyg_m2> mdjp et al: Consider merging that group with Audio CG.

<rtoyg_m2> Back to triage v.next

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1595

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1551

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1516

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1515

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1319

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1314

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1308

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1112

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1282

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1151

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/1091

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/916

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/457

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/359

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/358

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/257

<rtoyg_m2> https://github.com/WebAudio/web-audio-api/issues/108

trackbot, start meeting

<trackbot> Meeting: Audio Working Group Teleconference

<trackbot> Date: 17 September 2019

trackbot, end meeting

trackbot, end meeting

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: (no_one)
Present: (no_one)

WARNING: Fewer than 3 people found for Present list!

Found Scribe: mdjp
Inferring ScribeNick: mdjp

WARNING: No "Topic:" lines found.


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 17 Sep 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)