Update the AudioParam value attribute correctly from timelines.

Update the AudioParam value attribute correctly from timelines.

The automation functions exponentialRampToValueAtTime,
setTargetAtTime, and setValueCurveAtTime were not correctly updating
the .value attribute of the AudioParam.  For the first two methods,
the computed value was one frame too far into the future.  For last
method, the return value was always the last curve element, which is
wrong.

BUG=574905
TEST=audioparam-update-value-attribute.html

Committed: https://crrev.com/4007885e576b357d43eb4bd78f03254267aa2a01
Cr-Commit-Position: refs/heads/master@{#376044}

[Raymond Toy, 2016-02-11 23:45:27]

rtoy@chromium.org changed reviewers:
+ hongchan@chromium.org

[Raymond Toy, 2016-02-11 23:45:27]

PTAL.

[Raymond Toy, 2016-02-11 23:45:56]

Description was changed from

==========
Update the AudioParam value attribute correctly from timelines.

The automation functions exponentialRampToValueAtTime,
setTargetAtTime, and setValueCurveAtTime were not correctly updating
the .value attribute of the AudioParam.  For the first two methods,
the computed value was one frame too far into the future.  For last
method, the return value was alwasy the last curve element, which is
wrong.

BUG=574905
TEST=audioparam-update-value-attribute.html
==========

to

==========
Update the AudioParam value attribute correctly from timelines.

The automation functions exponentialRampToValueAtTime,
setTargetAtTime, and setValueCurveAtTime were not correctly updating
the .value attribute of the AudioParam.  For the first two methods,
the computed value was one frame too far into the future.  For last
method, the return value was always the last curve element, which is
wrong.

BUG=574905
TEST=audioparam-update-value-attribute.html
==========

[Raymond Toy, 2016-02-11 23:46:35]

Patchset #1 (id:1) has been deleted

[hongchan, 2016-02-16 23:13:45]

lgtm

[Raymond Toy, 2016-02-16 23:45:35]

The CQ bit was checked by rtoy@chromium.org

[commit-bot: I haz the power, 2016-02-16 23:46:34]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1695573002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1695573002/40001

[commit-bot: I haz the power, 2016-02-17 03:50:46]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-02-17 03:50:47]

Try jobs failed on following builders:
  win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[Raymond Toy, 2016-02-17 21:07:19]

The CQ bit was checked by rtoy@chromium.org

[Raymond Toy, 2016-02-17 21:07:19]

The patchset sent to the CQ was uploaded after l-g-t-m from
hongchan@chromium.org
Link to the patchset: https://codereview.chromium.org/1695573002/#ps60001
(title: "Rebase and reduce printed precision some more")

[commit-bot: I haz the power, 2016-02-17 21:08:54]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1695573002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1695573002/60001

[commit-bot: I haz the power, 2016-02-18 00:14:16]

Description was changed from

==========
Update the AudioParam value attribute correctly from timelines.

The automation functions exponentialRampToValueAtTime,
setTargetAtTime, and setValueCurveAtTime were not correctly updating
the .value attribute of the AudioParam.  For the first two methods,
the computed value was one frame too far into the future.  For last
method, the return value was always the last curve element, which is
wrong.

BUG=574905
TEST=audioparam-update-value-attribute.html
==========

to

==========
Update the AudioParam value attribute correctly from timelines.

The automation functions exponentialRampToValueAtTime,
setTargetAtTime, and setValueCurveAtTime were not correctly updating
the .value attribute of the AudioParam.  For the first two methods,
the computed value was one frame too far into the future.  For last
method, the return value was always the last curve element, which is
wrong.

BUG=574905
TEST=audioparam-update-value-attribute.html
==========

[commit-bot: I haz the power, 2016-02-18 00:14:17]

Committed patchset #3 (id:60001)

[commit-bot: I haz the power, 2016-02-18 00:15:33]

Description was changed from

==========
Update the AudioParam value attribute correctly from timelines.

The automation functions exponentialRampToValueAtTime,
setTargetAtTime, and setValueCurveAtTime were not correctly updating
the .value attribute of the AudioParam.  For the first two methods,
the computed value was one frame too far into the future.  For last
method, the return value was always the last curve element, which is
wrong.

BUG=574905
TEST=audioparam-update-value-attribute.html
==========

to

==========
Update the AudioParam value attribute correctly from timelines.

The automation functions exponentialRampToValueAtTime,
setTargetAtTime, and setValueCurveAtTime were not correctly updating
the .value attribute of the AudioParam.  For the first two methods,
the computed value was one frame too far into the future.  For last
method, the return value was always the last curve element, which is
wrong.

BUG=574905
TEST=audioparam-update-value-attribute.html

Committed: https://crrev.com/4007885e576b357d43eb4bd78f03254267aa2a01
Cr-Commit-Position: refs/heads/master@{#376044}
==========

[commit-bot: I haz the power, 2016-02-18 00:15:34]

Patchset 3 (id:??) landed as
https://crrev.com/4007885e576b357d43eb4bd78f03254267aa2a01
Cr-Commit-Position: refs/heads/master@{#376044}