Going to CR

<mdjp> rtoyg_m2 - what do we need to do to move out of CR?

<mdjp> Change log has been uploaded

<mdjp> chris close issues or bump to V.next which is almost done.

<mdjp> chris - one of the chairs needs to request any objections and that transition is requested.

<mdjp> rtoyg_m2 & mdjp call for objections to CR

<mdjp> no objections heard.

<mdjp> resolved

RESOLUTION: request updated CR for Web Audio API 1.0

<mdjp> trumpets sound

Implementation status

<mdjp> padenot - in final stages of having everything implemented, in particular AudioWorklet. Process can be called - main architectural code is finished

<mdjp> Remaining work inc error signaling, audio params and post message

<mdjp> padenot planning for FF to be completely complient by year end

<mdjp> padenot web midi, less opposition than previously. Looking for resources to ship the api (without sysex initially)

<mdjp> cwilso have we been able to get a security review - padenot, security people have looked it and it is on the roadmap

<mdjp> hoch working on spec compliance, almost done with audioworklet

<mdjp> rtoyg_m2 eveytihing in spec apart from mediaStreamTrack

<mdjp> micbuffa could not find any implementation with output latency

<mdjp> micbuffa loop handling is not consistent between browsers

<mdjp> padenot web platform tests will be the easiest way forward, to understand what is happening

<micbuffa> details about audio graph loop inconsistencies (see our WAC 2018 paper) : chrome adds a 3ms delay behind the scene, FF does not render if a delay is not present

<mdjp> rtoyg_m2 web midi on edge? Unknown

<micbuffa> in a loop

Web Midi

webmidi on edge will get updated with chromium

<mdjp> cwilso number of issues on the spec, not been dealt with as the has been no movement on ff implementation. Might be worth resolving now.

<mdjp> cwilso - happy to help with security conversations

<chris> https://www.midi.org/articles-old/details-about-midi-2-0-midi-ci-profiles-and-property-exchange

<mdjp> chris can we implement midi ci on top of web midi?

<mdjp> cwilso expect it is exposed as you can access any valid midi message.

<mdjp> chris - apple implementation status - no changes on audio/midi implementation

<mdjp> cwilso midi ci requires midi 2.0 this probably will not be possible after all

<mdjp> coffee break

<chris> https://github.com/svgeesus/MPE-notes/blob/master/MPE-final-spec-notes.md

<chris> late harvest, vine-ripened low hanging fruit.

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

V1 issues

<chris> github: https://github.com/WebAudio/web-audio-api/issues/1935

<mdjp> padnot assigned, will clarify based on #1471

<hoch> I'll take up on https://github.com/WebAudio/web-audio-api/issues/1947#issuecomment-505540807

Example for convolver buffer: https://jsfiddle.net/rtoy/syubam7z/4/

<mdjp> https://github.com/WebAudio/web-audio-api/issues/1933

chris: Go ahead and merge the changelog. Or let me do that if you want.

<chris> merged.

<chris> btw we do have 4 open issues :) https://github.com/WebAudio/web-audio-api/milestone/1

<hoch> https://github.com/WebAudio/web-audio-api/issues/1889

https://webaudio.github.io/web-audio-api/#MediaStreamAudioSourceNode-constructors

<mdjp> we have more than that...we also need to clear up https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone

<hoch> I think they are all captured in the "Ready for Editing" column. No?

<mdjp> ah, possibly - I'll update them

<mdjp> ok, everything in the project now has a milestone, we have 4 open with no milestone that we should discuss

<mdjp> https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone

mdjp: Proposes all new issues should now automatically go to v2, unless it's a critical spec issue.

https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+label%3A"High+Priority+V2"

<hoch> (heh)

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

micbuffa: disagrees with the hoch's comment about "using AudioWorklet".

chris lilley: Using blocks is a basic concept to encapsulate processing.

micbuffa: It would be great to have some way of grouping nodes in a container node or something.

Useful from modularity.

hoch: Trying to narrow down what the issue is about to focus on what we want to solve.
... This needs a new API to expose the connections and audio params.

padenot: We need an API design to see what it looks like.

hoch and micbuffa discuss how to do this and what it implies if you just import some code containing a "module". Can you inspect it? How does this work?

hoch Good to look at how other audio tools like maxmsp does this.

rtoyg_m2: What is the priority of this? Keep it as high-priority v2 or lower priority?

General consensus: Keep it high-priority but need input from users/devs on the use cases for this.

<hoch> `https://github.com/WebAudio/web-audio-api/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22High+Priority+V2%22`

<hoch> This is the correct link.

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

https://github.com/WebAudio/web-audio-api/issues/1791 Keep has high-priority; we need to define the algorithm better.

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

Consensus: Need to design/propose such a node, but not build it on top of DynamicsCompressor.

cwilso: One idea was to separate out detector part from vca.

chris Allows adding side chain easily.

padenot: Do we want a modular approach? Probably better

chris Would work well with the composite node idea.

padenot: Proposes a possible design that I (rtoyg) didn't capture.
... Go for modular approach

Concensus: General agreement. Possibly prototype in worklet.

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

https://github.com/WebAudio/web-audio-api/issues/246 to be handled in 13. Not high priority.

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

chris can't be done with existing oscillator. Need to add a new node or oscillator type

chris Important to have this to implement synths.

Concensus: Keep as high-priority

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

chris Need to be able to set the phase.

padenot Doable with current design of the oscillator node. Add additional audio param. Should work.

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

<cwilso> https://github.com/WebAudio/web-audio-api/issues/445#issuecomment-101391930

Concensus: Keep as high-prio letting ADC decide this issue.

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

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

Keep as high priority with at least uniform [-1,1] and standard Gaussian.

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

padenot: Maybe use web codec to do the streaming and a worklet to handle the audio to WebAudio

Concensus: Remove high-priority v2.

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

http://rtoy.github.io/webaudio-hacks/codec-tests/plot-audio.html

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)

Succeeded: s/coffe/coffee/
Present: cwilso chris micbuffa hoch scottlow rtoyg_m2 pauladenot mdjp (lilley)_ padenot Phillippe Milot
No ScribeNick specified.  Guessing ScribeNick: rtoyg_m2
Inferring Scribes: rtoyg_m2
Found Date: 25 Jun 2019
People with action items: 

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


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.)