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#5) by Marcus Geelnard (Opera) on W3C Bugzilla. Tue, 21 Aug 2012 11:03:50 GMT

(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.

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