Monday, 30 December 2013
Tuesday, 24 December 2013
Monday, 23 December 2013
- [Minutes] W3C Audio Teleconference 2013-12-19
- [Minutes] W3C Audio WG Teleconference, 2013-12-19
- Resolution on de-zippering Re: [CfC] Consensus gathering for the Dezippering issue
- Re: [CfC] Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue - blink processing
Thursday, 19 December 2013
Wednesday, 18 December 2013
Tuesday, 17 December 2013
- Re: [Agenda] Audio WG Teleconference 2013-12-19
- [Agenda] Audio WG Teleconference 2013-12-19
- Re: [CfC] Consensus gathering for the Dezippering issue
Thursday, 12 December 2013
Wednesday, 11 December 2013
- Re: AnalyserNode
- Re: AnalyserNode
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- Re: AnalyserNode
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue - blink processing
Tuesday, 10 December 2013
Friday, 6 December 2013
Thursday, 5 December 2013
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
Wednesday, 4 December 2013
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- [Agenda] W3C Audio WG Teleconference - 2013-12-05
- Re: [CfC] Re: Consensus gathering for the Dezippering issue
- [CfC] Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
Tuesday, 3 December 2013
- Re: Consensus gathering for the Dezippering issue
- Re: Consensus gathering for the Dezippering issue
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Consensus gathering for the Dezippering issue
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Request for Agenda - Audio WG Teleconference 2013-12-05
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
Monday, 2 December 2013
- 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?
- Integer PCM sample formats to Web Audio API?
Wednesday, 27 November 2013
Tuesday, 26 November 2013
Monday, 25 November 2013
- Re: Precise control over transient effects in immediate sounds
- Re: Precise control over transient effects in immediate sounds
- Precise control over transient effects in immediate sounds
Wednesday, 20 November 2013
Monday, 18 November 2013
- Web Audio API support bug on connect.microsoft.com
- Re: Call for Agenda - Audio WG teleconference 2013-11-21
- [minutes] Audio WG teleconference, 7th November 2013
- Re: Call for Agenda - Audio WG teleconference 2013-11-21
- Call for Agenda - Audio WG teleconference 2013-11-21
Friday, 15 November 2013
Thursday, 14 November 2013
- Re: Anyone interested in the Web Array Math API?
- 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: Anyone interested in the Web Array Math API?
- Re: Anyone interested in the Web Array Math API?
- Re: Anyone interested in the Web Array Math API?
- Re: Anyone interested in the Web Array Math API?
- Re: Anyone interested in the Web Array Math API?
- Re: Anyone interested in the Web Array Math API?
- Anyone interested in the Web Array Math API?
Wednesday, 13 November 2013
Sunday, 10 November 2013
Saturday, 9 November 2013
Friday, 8 November 2013
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering and the fundamental issue of target users
- 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
Thursday, 7 November 2013
- Re: De-zippering
- Re: De-zippering and the fundamental issue of target users
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- Re: De-zippering
- De-zippering
- Re: Reminder and call for agenda: W3C Audio WG meeting 2013-11-07
- Regrets for Audio WG meeting 2013-11-07
Wednesday, 6 November 2013
- Re: 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
- Re: 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
Tuesday, 5 November 2013
- Re: Reminder and call for agenda: W3C Audio WG meeting 2013-11-07
- Reminder and call for agenda: W3C Audio WG meeting 2013-11-07
- Re: Speakers output back as input node
Monday, 4 November 2013
Thursday, 31 October 2013
- Re: [web-audio-api testing] Best way of testing an AudioNode output
- Re: start/stop on AudioBufferSourceNodes without a buffer?
- Re: Valid start offsets and durations for AudioBufferSourceNodes?
- Re: Corner cases on start/stop exceptions
- Re: start/stop on AudioBufferSourceNodes without a buffer?
- Re: Valid start offsets and durations for AudioBufferSourceNodes?
- Re: [web-audio-api testing] Best way of testing an AudioNode output
- Re: [web-audio-api testing] Best way of testing an AudioNode output
- start/stop on AudioBufferSourceNodes without a buffer?
- Re: [web-audio-api testing] Best way of testing an AudioNode output
Wednesday, 30 October 2013
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Corner cases on start/stop exceptions
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Valid start offsets and durations for AudioBufferSourceNodes?
- Corner cases on start/stop exceptions
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Moz 25 released with web audio, new "song of iridium" demo
- RE: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Fwd: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
Tuesday, 29 October 2013
- 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: 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: 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))
Monday, 28 October 2013
- Re: bridge between Github and public-audio list suspended
- Re: bridge between Github and public-audio list suspended (Was: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104))
- bridge between Github and public-audio list suspended (Was: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104))
- Re: [web-audio-api testing] Best way of testing an AudioNode output
- Re: ScriptProcessorNode off the main thread (Was: Questioning the current direction of the Web Audio API)
- Re: [web-midi-api] Add (non-normative) reference to Web Audio API (#83)
- Re: [web-audio-api testing] Best way of testing an AudioNode output
Saturday, 26 October 2013
Friday, 25 October 2013
- 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: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
- Re: [web-audio-api] `ScriptProcessorNode` is Unfit For Purpose (#253)
- Re: [web-audio-api] `ScriptProcessorNode` is Unfit For Purpose (#253)
- Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
- Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
- 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: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)
- 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: [web-audio-api] Race Conditions (#66)
- 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
- 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: [web-audio-api] Loop event (#267)
Thursday, 24 October 2013
- 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)
- Re: [web-audio-api] Issue #114 - Spec argument range of createBuffer. (#245)
Wednesday, 23 October 2013
- Re: [demo-list] Added Mixbolt to the demo list (#4)
- Re: [demo-list] Added Mixbolt to the demo list (#4)
- Re: ML + GH issue tracker
- [demo-list] Added Mixbolt to the demo list (#4)
- Re: [web-audio-api] (OscillatorTypes): Oscillator types are not defined (#104)
Tuesday, 22 October 2013
- Re: Contribution Guide / Rules for new features (Was: Propose additions to AnalyserNode for getting complex data)
- [web-audio-api] Loop event (#267)
- Re: ML + GH issue tracker
- Re: ML + GH issue tracker
- Re: Wiki updates / cleanup
- Re: Wiki updates / cleanup
- Wiki updates / cleanup
- Contribution Guide / Rules for new features (Was: Propose additions to AnalyserNode for getting complex data)
- Re: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: ML + GH issue tracker
- [web-midi-api] Add (non-normative) reference to Web Audio API (#83)
- Re: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: Questioning the current direction of the Web Audio API
Monday, 21 October 2013
- Re: Questioning the current direction of the Web Audio API
- Re: [web-audio-api] Browser support tests
- 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: [web-midi-api] MIDIPort#open() necessary? (#75)
- Re: [web-midi-api] Refactor getInput, getOutput -> getPort(), inputs[], outputs[] ? (#2)
- Re: [web-midi-api] Refactor getInput, getOutput -> getPort(), inputs[], outputs[] ? (#2)
- Re: [web-midi-api] Web Audio API example (#59)
- Re: [web-midi-api] Web Audio API example (#59)
- 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] Inputs and outputs now Maplike, among others - fixes issue #81, issue #59, issue #2. (#82)
- [web-midi-api] Inputs and outputs now Maplike, among others - fixes issue #81, issue #59, issue #2. (#82)
- Re: Questioning the current direction of the Web Audio API
- Re: [web-audio-api] Lack of Serialization Primitives & Introspection (#256)
- Re: [web-audio-api] Lack of Serialization Primitives & Introspection (#256)
- 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)
- Re: [web-audio-api] AudioContext.createBuffer(chan, len, rate) should accept only non-zero positive values (#114)
- Re: [web-audio-api] AudioContext.createBuffer(chan, len, rate) should accept only non-zero positive values (#114)
- Re: [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- 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] Behavior of source nodes on connect/disconnect (#266)
- [web-audio-api] Behavior of source nodes on connect/disconnect (#266)
- Re: [web-audio-api] Browser support tests
Friday, 18 October 2013
Monday, 21 October 2013
- 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: 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.
Sunday, 20 October 2013
- Re: CFC: Web MIDI (was: Re: [minutes] Audio WG teleconference - 2013-10-17)
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: Questioning the current direction of the Web Audio API
Saturday, 19 October 2013
- 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: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
Friday, 18 October 2013
- Re: Questioning the current direction of the Web Audio API
- [web-audio-api] Lack of support for continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts. (#265)
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- CFC: Web MIDI (was: Re: [minutes] Audio WG teleconference - 2013-10-17)
- 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
- [minutes] Audio WG teleconference 2013-10-03
- Re: Follow up on TAG feedback?
- [minutes] Audio WG teleconference - 2013-10-17
- Re: Questioning the current direction of the Web Audio API
- Re: [web-audio-api] Questioning the current direction of the Web Audio API (#263)
- Re: Questioning the current direction of the Web Audio API
- Questioning the current direction of the Web Audio API
- Re: Comment on new Public Draft
- Re: Comment on new Public Draft
- [web-audio-api] Use AudioMediaStreamTrack as source rather than ill-defined first track of MediaStream (#264)
- Comment on new Public Draft
- Re: Continuous playback of javascript synthesized consecutive audio buffers causes audio artifacts when no buffer starving occurs.
- Re: [web-audio-api] Questioning the current direction of the Web Audio API (#263)
- Re: [web-audio-api] Visible Data Races (#254)
Thursday, 17 October 2013
Friday, 18 October 2013
Thursday, 17 October 2013
- Re: AnalyzerNode - magnitude/phase
- [web-audio-api] Propose additions to AnalyserNode for getting complex data (#262)
- Re: Audio WG teleconference tomorrow, 2013-10-17
- Re: [web-audio-api] Naming of OfflineAudioContext (#261)
- 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)
- [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)
- [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)
- [web-audio-api] Callbacks without Promises (#252)
- [web-audio-api] Subclassing (#251)
- [web-audio-api] Constructibility & De-sugaring of static methods (#250)
- Re: Audio WG teleconference tomorrow, 2013-10-17
Wednesday, 16 October 2013
- Re: start/stop method for OscillatorNode
- Re: ML + GH issue tracker
- Audio WG teleconference tomorrow, 2013-10-17
Tuesday, 15 October 2013
- Re: Web MIDI spec updates
- Web MIDI spec updates
- [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)
- Re: [web-midi-api] requestMIDIAccess will raise "InvalidSecurityError" (#78)
- 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)
Friday, 11 October 2013
Thursday, 10 October 2013
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: start/stop method for OscillatorNode
- [web-audio-api] Arguments to OscillatorNode should be optional (#249)
- Re: start/stop method for OscillatorNode
Wednesday, 9 October 2013
- Re: start/stop method for OscillatorNode
- Re: Errors when stopping a disconnected source node?
- start/stop method for OscillatorNode
- Errors when stopping a disconnected source node?
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
Tuesday, 8 October 2013
- Re: [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
- 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)
- [web-audio-api] Proper FFT / IFFT missing (#248)
- Re: [Buzzkill] Cleaning Up Web Audio API Spec
Monday, 7 October 2013
Saturday, 5 October 2013
Friday, 4 October 2013
- 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)
- Web Audio API changelog
Thursday, 3 October 2013
- [web-audio-api] Filter node pops when frequency parameter is modulated below 0 (#247)
- Consensus to publish a new public W3C Working Draft of the Web Audio API
- [web-audio-api] DynamicsCompressor node should enable sidechain compression (#246)
- Re: [web-audio-api] (DynamicsCompressorNode): DynamicsCompressorNode underspecified (#84)
- Re: [web-audio-api] (DynamicsCompressorNode): DynamicsCompressorNode underspecified (#84)
- Re: [web-audio-api] Specify what DynamicsProcessorNode should do (#26)
- Re: [web-audio-api] Specify what DynamicsProcessorNode should do (#26)
- Regrets
- Disregard (was: Possible Regrets: Re: Call for Agenda: Audio WG teleconference, 3rd October 2013)
- Possible Regrets: Re: Call for Agenda: Audio WG teleconference, 3rd October 2013