[web-audio-api] Clarify that reading AudioParam.computedValue will return the latest computed value for the latest audio quantum (#174)

> Originally reported on W3C Bugzilla [ISSUE-19766](https://www.w3.org/Bugs/Public/show_bug.cgi?id=19766) Mon, 29 Oct 2012 23:09:12 GMT
> Reported by Ehsan Akhgari [:ehsan]
> Assigned to 

This will mean that reading computedValue twice in a row will potentially return different results if the audio thread's computations have changed the computed value of an AudioParam.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/174

Received on Wednesday, 11 September 2013 14:29:16 UTC