Fix MediaRecorder bitrate configuration bug

Fix MediaRecorder bitrate configuration bug

The MediaRecorder API specifies that bitrates be communicated in bits
per second, which is correctly plumbed through Chrome.  However, VPx
encoders expect its arguments to be specified in kilobits per second.
This resulted in specifying any bitrate via the javascript API to be
off by a thousand, resulting in enormous files.  Change it so we
convert bits -> kilobits by dividing by 1000
BUG=605750
R=mcasas@chromium.org

Review URL: https://codereview.chromium.org/1913233002

Cr-Commit-Position: refs/heads/master@{#389411}
(cherry picked from commit 0a58e7128c0559027991ae4671fb7b16274b7ba3)


NOTRY=true
NOPRESUBMIT=true

[mcasas, 2016-04-26 21:11:17]

Description was changed from

==========
Fix MediaRecorder bitrate configuration bug

The MediaRecorder API specifies that bitrates be communicated in bits
per second, which is correctly plumbed through Chrome.  However, VPx
encoders expect its arguments to be specified in kilobits per second.
This resulted in specifying any bitrate via the javascript API to be
off by a thousand, resulting in enormous files.  Change it so we
convert bits -> kilobits by dividing by 1000
BUG=605750

R=mcasas@chromium.org

Review URL: https://codereview.chromium.org/1913233002

Cr-Commit-Position: refs/heads/master@{#389411}
(cherry picked from commit 0a58e7128c0559027991ae4671fb7b16274b7ba3)
==========

to

==========
Fix MediaRecorder bitrate configuration bug

The MediaRecorder API specifies that bitrates be communicated in bits
per second, which is correctly plumbed through Chrome.  However, VPx
encoders expect its arguments to be specified in kilobits per second.
This resulted in specifying any bitrate via the javascript API to be
off by a thousand, resulting in enormous files.  Change it so we
convert bits -> kilobits by dividing by 1000
BUG=605750

R=mcasas@chromium.org

Review URL: https://codereview.chromium.org/1913233002

Cr-Commit-Position: refs/heads/master@{#389411}
(cherry picked from commit 0a58e7128c0559027991ae4671fb7b16274b7ba3)


NOTRY=true
NOPRESUBMIT=true
==========

[mcasas, 2016-04-26 21:11:28]

The CQ bit was checked by mcasas@chromium.org

[commit-bot: I haz the power, 2016-04-26 21:12:00]

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

[commit-bot: I haz the power, 2016-04-26 21:12:01]

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

[commit-bot: I haz the power, 2016-04-26 21:12:02]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[emircan, 2016-04-26 21:25:53]

emircan@chromium.org changed reviewers:
+ emircan@chromium.org

[emircan, 2016-04-26 21:25:53]

lgtm

[mcasas, 2016-04-26 21:26:06]

The CQ bit was checked by mcasas@chromium.org

[commit-bot: I haz the power, 2016-04-26 21:26:55]

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

[commit-bot: I haz the power, 2016-04-26 21:28:08]

Description was changed from

==========
Fix MediaRecorder bitrate configuration bug

The MediaRecorder API specifies that bitrates be communicated in bits
per second, which is correctly plumbed through Chrome.  However, VPx
encoders expect its arguments to be specified in kilobits per second.
This resulted in specifying any bitrate via the javascript API to be
off by a thousand, resulting in enormous files.  Change it so we
convert bits -> kilobits by dividing by 1000
BUG=605750

R=mcasas@chromium.org

Review URL: https://codereview.chromium.org/1913233002

Cr-Commit-Position: refs/heads/master@{#389411}
(cherry picked from commit 0a58e7128c0559027991ae4671fb7b16274b7ba3)


NOTRY=true
NOPRESUBMIT=true
==========

to

==========
Fix MediaRecorder bitrate configuration bug

The MediaRecorder API specifies that bitrates be communicated in bits
per second, which is correctly plumbed through Chrome.  However, VPx
encoders expect its arguments to be specified in kilobits per second.
This resulted in specifying any bitrate via the javascript API to be
off by a thousand, resulting in enormous files.  Change it so we
convert bits -> kilobits by dividing by 1000
BUG=605750

R=mcasas@chromium.org

Review URL: https://codereview.chromium.org/1913233002

Cr-Commit-Position: refs/heads/master@{#389411}
(cherry picked from commit 0a58e7128c0559027991ae4671fb7b16274b7ba3)


NOTRY=true
NOPRESUBMIT=true
==========

[commit-bot: I haz the power, 2016-04-26 21:28:09]

Committed patchset #1 (id:1)