Re: [web-audio-api] (AudioNodeAsAudioParam): AudioNode as input to AudioParam underdefined (#159)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17398#7) by Chris Rogers on W3C Bugzilla. Sat, 06 Oct 2012 00:56:58 GMT

(In reply to [comment #6](#issuecomment-24244592))
> (In reply to [comment #5](#issuecomment-24244587))
> > Much more detail for how AudioParam values are calculated added here:
> > https://dvcs.w3.org/hg/audio/rev/41db9905149d
> 
> Ah, that cleared things up :)  One thing that seems non-intuitive though is
> that reading the .value attribute does not produce the value that has been
> written to it. E.g. consider the following code:
> 
> myParam.value = 3;
> if (myParam.value != 3) alert("I'm confused");
> 
> According to the current scheme, it's entirely possible for the code to enter
> the alert-statement.
> 
> Wouldn't it be better if .value always returns the value that has been written
> to it, and then we could add a new method for reading the intrinsic value (e.g.
> getIntrinsicValue())?
> 
> BTW, with "current time" I assume you mean the value of
> AudioContext.currentTime when the attribute is read (?). Perhaps this should be
> defined somewhere.

I think we're in better shape now with:
https://dvcs.w3.org/hg/audio/rev/79d44e3f3ced
https://dvcs.w3.org/hg/audio/rev/3bddf0c97e77

I think "current time" should be more clear now that this text has moved, since very nearby text refers explicitly to AudioContext.currentTime

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