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#3) by Marcus Geelnard (Opera) on W3C Bugzilla. Wed, 08 Aug 2012 11:39:16 GMT

I'm still a bit confused. The changes describe how the connect() method works. I think a better way to specify this is in the AudioParam section, with a complete description of how the final parameter value is calculated. This would include:

1) The .value attribute
2) The automation values (scheduled changes)
3) The connected inputs

My current assumption would be something like:

[.value attribute] + [automation curve] + sum(mono(inputs))

Also, the specification needs to define what the default values of each contributing factor are. For instance if no events are scheduled or if no inputs are connected.

Also, what happens if cancelScheduledValues() is called with time = 0 or -Infinity? Will the automation curve return to its default value, keep its current value, or throw an exception?

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