See also: IRC log
<padenot> hi
Aloha!
present rtoyg_m
<joe> joe: let's start with lifetime issue https://github.com/WebAudio/web-audio-api/issues/475
<scribe> scribenick: rtoyg_m
hongchan: Active reference is easy to understand, spec, and implement
joe: Any comments? This is the last major thing for AudioWorklets.
<joe> https://github.com/WebAudio/web-audio-api/issues/475#issuecomment-256781404
<joe> rtoy: say you have a worklet and the developer returns nothing from process() (no return value)
<joe> rtoy: you connect an input to it and process runs
<joe> joe: process() will still run as soon as inputs are connected
<joe> rtoy: now we don't need a way to handl tailTime independent of the active source proposal
rtoyg_m, joe: General agreement on active source idea.
<hongchan> https://github.com/WebAudio/web-audio-api/issues/990
rtoyg_m: Let's not do tailtime, because there will then be two ways to do it.
joe: /summarizes the issue
... Probably not desirable to do properties.
... Still be necessary to hand-code property getter/setters for
fancier things.
... The best way is sendData messaging for implementing
properties.
... But what about AudioParams? Advantage of map-like is no
namespace collision.
... So proposal is no map-like for properties, map-like for
AudioParams
padenot: After further reading, it should be fine.
<joe> https://github.com/WebAudio/web-audio-api/issues/988#issuecomment-253140436
joe: Bottom line: hard for developers to implement detection and notification of property change.
padenot: Not hard, but kind of a regression in capability.
hongchan: map-like for AudioParam makes sense to group together.
hongchan, joe: Postpone decision until next week; hongchan to follow up with Elliot.
<joe> https://github.com/WebAudio/web-audio-api/issues/1067
<joe> https://github.com/WebAudio/web-audio-api/issues/95
<hongchan> ABSN loop subsample: https://github.com/WebAudio/web-audio-api/issues/336
<hongchan> Our answer was 'NO'.
For start, see https://github.com/WebAudio/web-audio-api/issues/915
<joe> joe: Actually 915 shows that we revised our answer to YES
<joe> https://github.com/WebAudio/web-audio-api/issues/1067
<hongchan> https://github.com/WebAudio/web-audio-api/pull/1051
<ghaudiobot> [web-audio-api] padenot pushed 1 new commit to gh-pages: https://github.com/WebAudio/web-audio-api/commit/a9f028fa229e2babb72bf19e978440e24daeddc1
<ghaudiobot> web-audio-api/gh-pages a9f028f Raymond Toy: Fix #713: Specify clamping of automation times....
joe: WebAudio rechartered!
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) Found ScribeNick: rtoyg_m Inferring Scribes: rtoyg_m WARNING: No "Topic:" lines found. Present: rtoyg_m hongchan padenot joe jdsmith WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 10 Nov 2016 Guessing minutes URL: http://www.w3.org/2016/11/10-audio-minutes.html 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[End of scribe.perl diagnostic output]