[Minutes] W3C Audio Teleconference 2013-12-19
[Minutes] W3C Audio WG Teleconference, 2013-12-19
[Agenda] Audio WG Teleconference 2013-12-19
- Re: [Agenda] Audio WG Teleconference 2013-12-19
- Re: [Agenda] Audio WG Teleconference 2013-12-19
- Re: [Agenda] Audio WG Teleconference 2013-12-19
AnalyserNode
[minutes] Audio WG Teleconference 2013-12-05
Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
- [CfC] Re: Consensus gathering for the Dezippering issue
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
Request for Agenda - Audio WG Teleconference 2013-12-05
Integer PCM sample formats to Web Audio API?
- Re: Integer PCM sample formats to Web Audio API?
- Re: Integer PCM sample formats to Web Audio API?
- Re: Integer PCM sample formats to Web Audio API?
[minutes] Audio WG Teleconference 2013-11-21
Speaker Channel Layouts
Precise control over transient effects in immediate sounds
[agenda] W3C Audio WG teleconference, 2013-11-21
Web Audio API support bug on connect.microsoft.com
[minutes] Audio WG teleconference, 7th November 2013
Call for Agenda - Audio WG teleconference 2013-11-21
- Re: Call for Agenda - Audio WG teleconference 2013-11-21
- Re: Call for Agenda - Audio WG teleconference 2013-11-21
Anyone interested in the Web Array Math API?
De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- stop()ing
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
Reminder and call for agenda: W3C Audio WG meeting 2013-11-07
- Re: Reminder and call for agenda: W3C Audio WG meeting 2013-11-07
- Regrets for Audio WG meeting 2013-11-07
- Re: Reminder and call for agenda: W3C Audio WG meeting 2013-11-07
Speakers output back as input node
ModularGrid webaudio and webmidi demo
start/stop on AudioBufferSourceNodes without a buffer?
Valid start offsets and durations for AudioBufferSourceNodes?
Corner cases on start/stop exceptions
Moz 25 released with web audio, new "song of iridium" demo
Fwd: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- RE: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
bridge between Github and public-audio list suspended (Was: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104))
- Re: bridge between Github and public-audio list suspended (Was: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104))
- Re: bridge between Github and public-audio list suspended (Was: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104))
[web-audio-api testing] Best way of testing an AudioNode output
- Re: [web-audio-api testing] Best way of testing an AudioNode output
- Re: [web-audio-api testing] Best way of testing an AudioNode output
Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
- Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
- Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
- Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
Re: [web-audio-api] Race Conditions (#66)
Re: [web-audio-api] Issue #114 - Spec argument range of createBuffer. (#245)
[demo-list] Added Mixbolt to the demo list (#4)
- Re: [demo-list] Added Mixbolt to the demo list (#4)
- Re: [demo-list] Added Mixbolt to the demo list (#4)
Re: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104)
[web-audio-api] Loop event (#267)
- Re: [web-audio-api] Loop event (#267)
- Re: [web-audio-api] Loop event (#267)
- Re: [web-audio-api] Loop event (#267)
- Re: [web-audio-api] Loop event (#267)
Wiki updates / cleanup
[web-midi-api] Add (non-normative) reference to Web Audio API (#83)
Re: [web-midi-api] MIDIPort#open() necessary? (#75)
Re: [web-midi-api] Refactor getInput, getOutput -> getPort(), inputs[], outputs[] ? (#2)
Re: [web-midi-api] Web Audio API example (#59)
[web-midi-api] Inputs and outputs now Maplike, among others - fixes issue #81, issue #59, issue #2. (#82)
Re: [web-audio-api] AudioContext.createBuffer(chan, len, rate) should accept only non-zero positive values (#114)
[web-audio-api] Behavior of source nodes on connect/disconnect (#266)
[web-audio-api] Browser support tests
[web-audio-api] Lack of support for continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts. (#265)
CFC: Web MIDI (was: Re: [minutes] Audio WG teleconference - 2013-10-17)
[minutes] Audio WG teleconference 2013-10-03
Re: Follow up on TAG feedback?
[minutes] Audio WG teleconference - 2013-10-17
Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
- Re: Questioning the current direction of the Web Audio API
[web-audio-api] Use AudioMediaStreamTrack as source rather than ill-defined first track of MediaStream (#264)
Comment on new Public Draft
Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
[web-audio-api] Questioning the current direction of the Web Audio API (#263)
- Re: [web-audio-api] Questioning the current direction of the Web Audio API (#263)
- Re: [web-audio-api] Questioning the current direction of the Web Audio API (#263)
- Re: [web-audio-api] Questioning the current direction of the Web Audio API (#263)
- Re: [web-audio-api] Questioning the current direction of the Web Audio API (#263)
Re: AnalyzerNode - magnitude/phase
[web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
Tracking our response to the TAG feedback
[web-audio-api] Naming of OfflineAudioContext (#261)
[web-audio-api] What language are the examples in Section 11 written in? (#260)
- Re: [web-audio-api] What language are the examples in Section 11 written in? (#260)
- Re: [web-audio-api] What language are the examples in Section 11 written in? (#260)
- Re: [web-audio-api] What language are the examples in Section 11 written in? (#260)
[web-audio-api] Use of param in example 4.5.4 (#259)
[web-audio-api] Return destination from AudioNode::connect() (#258)
[web-audio-api] Layering considerations (#257)
[web-audio-api] Lack of Serialization Primitives & Introspection (#256)
- Re: [web-audio-api] Lack of Serialization Primitives & Introspection (#256)
- Re: [web-audio-api] Lack of Serialization Primitives & Introspection (#256)
[web-audio-api] Explaining ("De-sugaring") the `*Node` Types (#255)
[web-audio-api] Visible Data Races (#254)
[web-audio-api] `ScriptProcessorNode` is Unfit For Purpose (#253)
- Re: [web-audio-api] `ScriptProcessorNode` is Unfit For Purpose (#253)
- Re: [web-audio-api] `ScriptProcessorNode` is Unfit For Purpose (#253)
[web-audio-api] Callbacks without Promises (#252)
[web-audio-api] Subclassing (#251)
[web-audio-api] Constructibility & De-sugaring of static methods (#250)
Audio WG teleconference tomorrow, 2013-10-17
Web MIDI spec updates
[web-midi-api] Need a boolean describing whether sysex is allowed (#81)
- Re: [web-midi-api] Need a boolean describing whether sysex is allowed (#81)
- Re: [web-midi-api] Need a boolean describing whether sysex is allowed (#81)
Re: [web-midi-api] DOMError for the system returning an error to initialize MIDI system on requestMIDIAccess (#77)
Re: [web-midi-api] requestMIDIAccess will raise "InvalidSecurityError" (#78)
OfflineAudioContext constructor question
[web-audio-api] Arguments to OscillatorNode should be optional (#249)
start/stop method for OscillatorNode
Errors when stopping a disconnected source node?
[web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
[Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
ML + GH issue tracker
Web Audio API changelog
[web-audio-api] Filter node pops when frequency parameter is modulated below 0 (#247)
- Re: [web-audio-api] Filter node pops when frequency parameter is modulated below 0 (#247)
- Re: [web-audio-api] Filter node pops when frequency parameter is modulated below 0 (#247)