1198205 - When an inspected node has automation, the displayed parameter values are "unrelated"/disconnected from the actual values

Status: RESOLVED INVALID

(DevTools Graveyard :: Web Audio Editor, defect)

Description

[Soledad Penades [:sole] [:spenades]]

This problem is two fold:

1) when a node has automation on its parameters (via setValueAtTime etc) the values we enter on the inspector for that node on those parameters (i.e. on the right hand side) are ignored as the automation takes precedence. I am guessing this could maybe be fixed by sending a cancel all events message to the node and then running a setValueAtTime "now" to insta fix it. Or at least show that there is automation happening (like e.g. Reason does it by highlighting the automated parameters in alien green) and that's why you can't edit the value

2) if the parameter value has been set with setValueAtTime but not with parameter.value, the inspector still shows the value from parameter.value. Which is not the one we're using. E.g. I created a gain node to build an LFO chain, then set gain.gain.setValueAtTime(100, now). I wanted to experiment with other values for gain to see how the LFO would sound, but the inspector shows me '1' which is the default gain value.

This is really counterproductive to using the inspector for experimenting / adjusting and generally having a more responsive development cycle.

Comment 1

[Jordan Santell [:jsantell] [@jsantell]]

While this is correct in that it displays the `get value()` it is definitely misleading. I think an automation icon on params that have it would be great because:

* its easy
* itll indicate which params to look at (when I fix intermittent in audio param view)
* more info on all params from a the node level

Comment 2

[BMO Automation]

The code behind DevTools:Web Audio Editor has gone away. Closing this bug as INVALID