- From: Olivier Thereaux <notifications@github.com>
- Date: Wed, 11 Sep 2013 07:29:30 -0700
- To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Received on Wednesday, 11 September 2013 14:32:54 UTC
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=21545#5) by Ehsan Akhgari [:ehsan] on W3C Bugzilla. Tue, 16 Jul 2013 21:19:30 GMT (In reply to [comment #5](#issuecomment-24244132)) > (In reply to [comment #4](#issuecomment-24244125)) > > Thanks, I actually missed that part of the prose, but I agree that it should > > have been removed. :-) > > > > My question was about this part of the prose (about the intrinsic value): > > "When read, the .value attribute always returns the intrinsic value for the > > current time." This basically has the same problems as the old > > computedValue property, which is the problem I was talking about in comment > > 2. > > It's not quite the same as computedValue, since at a specific time, it's a > very straightforward mapping and it's possible to get the exact value based > on the "scheduled" events (from setValueAtTime(), linearRampToValueAtTime(), > etc.). But then we will face the same problems discussed in this message: <http://lists.w3.org/Archives/Public/public-audio/2012OctDec/0623.html>... --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/issues/46#issuecomment-24244140
Received on Wednesday, 11 September 2013 14:32:54 UTC