Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify that reading AudioParam.computedValue will return the latest computed value for the latest audio quantum #174

Closed
olivierthereaux opened this issue Sep 11, 2013 · 2 comments
Closed

Clarify that reading AudioParam.computedValue will return the latest computed value for the latest audio quantum #174

olivierthereaux opened this issue Sep 11, 2013 · 2 comments

Comments

@olivierthereaux
Copy link
Contributor

Originally reported on W3C Bugzilla ISSUE-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.
@olivierthereaux
Copy link
Contributor Author

Original comment by Chris Rogers on W3C Bugzilla. Wed, 14 Nov 2012 00:04:07 GMT

Fixed:
https://dvcs.w3.org/hg/audio/rev/48e0d9d7ff61

@olivierthereaux
Copy link
Contributor Author

Original comment by Olivier Thereaux on W3C Bugzilla. Tue, 18 Dec 2012 13:08:28 GMT

Changeset looks good. No objection heard. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@olivierthereaux