- From: Ehsan Akhgari <ehsan.akhgari@gmail.com>
- Date: Mon, 22 Apr 2013 15:45:34 -0400
- To: "public-audio@w3.org" <public-audio@w3.org>
Received on Monday, 22 April 2013 19:46:44 UTC
The current spec codifies the reduction value for DynamicsCompressorNode as a read-only AudioParam. That would not actually prevent content from writing to that value, you could easily do: node.reduction.value = 10; Or even worse, scheduling automation events on the reduction argument. I think this is really confusing, and probably all we need here is a read-only float argument. Or am I missing something? -- Ehsan <http://ehsanakhgari.org/>
Received on Monday, 22 April 2013 19:46:44 UTC