- From: Chris Lilley <chris@w3.org>
- Date: Tue, 6 Feb 2018 13:30:46 -0500
- To: Tom Ritter <tom@ritter.vg>
- Cc: public-privacy@w3.org
On 06-Feb-18 00:42, Tom Ritter wrote: > I have a followup question - I'm curious what the intended resolution > of the timers that Web Audio will expose are. Millisecond? Nanosecond? > I'm afraid I don't really know much about audio, so while I think 'a > sample rate of 48000' can get converted to milliseconds somehow, I'm > not sure what the math is there... Audio processing works not in instantaneous single samples but on blocks of samples, because many operations require to know the previous or next values. Audio is thus processed in blocks of 128 samples, called a 'render quantum' in the spec. For a sampling rate of 48,000 this comes to 128 / 48,000 = 2.67 milliseconds. > > -tom > > On 1 February 2018 at 12:02, Chris Lilley <chris@w3.org> wrote: >> A gentle reminder about this review request. Web Audio API is on the agenda >> for the TAG f2f tomorrow; so we now hope to move to CR by the end of >> February. >> >> On 30-Nov-17 11:39, Chris Lilley wrote: >> >> Audio WG requests privacy review of the Web Audio API >> >> Specification URL: https://webaudio.github.io/web-audio-api/ >> GitHub repo: https://github.com/WebAudio/web-audio-api >> >> The major change in the last year or two is the extensibility point. We >> switched from ScriptProcessorNode (running on the main thread, now >> deprecated) to Audio worklets which are of course derived from the TAG/CSS >> Houdini Worklet. Plus a lot of detailed spec improvements and >> clarifications. Complete changes list. >> >> There is a Security and Privacy self- assessment appendix. >> >> Ideally, we would like to move to CR by the end of 2017. Please let us know >> if you would like more time to review. Review comments should ideally be >> raised as issues on GitHub. >> >> -- >> Chris Lilley >> @svgeesus >> Technical Director @ W3C >> W3C Strategy Team, Core Web Design >> W3C Architecture & Technology Team, Core Web & Media >> >> -- >> Chris Lilley >> @svgeesus >> Technical Director @ W3C >> W3C Strategy Team, Core Web Design >> W3C Architecture & Technology Team, Core Web & Media -- Chris Lilley @svgeesus Technical Director @ W3C W3C Strategy Team, Core Web Design W3C Architecture & Technology Team, Core Web & Media
Received on Tuesday, 6 February 2018 18:30:54 UTC