Re: Minimum and Maximum value properties for AudioParam

Indeed.  Chris Rogers removed them in the spec in April 2013:
https://github.com/WebAudio/web-audio-api/commit/afc427a147eeff5342bba173d4c32dc5a3fbcefb.
I didn't do anything around min/max/computedValue as part of AudioWorker.

On Tue, Sep 30, 2014 at 2:51 AM, Chinmay Pendharkar <notthetup@gmail.com>
wrote:

> OK. Looking through the commit history, I saw these two issues.
>
> https://github.com/WebAudio/web-audio-api/issues/46
>
> https://github.com/WebAudio/web-audio-api/issues/175
>
> Seems that it was decided to remove these properties in 2013.
>
> Thanks.
>
> -Chinmay
>
>
>
> On Tue, Sep 30, 2014 at 5:31 PM, Chinmay Pendharkar <notthetup@gmail.com>
> wrote:
>
>> Hi all,
>>
>> I was going through the spec today when I discovered that during the
>> updates for the AudioWorker spec, the minValue and maxValue properties of
>> AudioParam were removed from the AudioParam interface definition.
>>
>> Is this something that was overlooked or is this the part of the new
>> design for the AudioWorker spec?
>>
>> -Chinmay
>>
>
>