Remove frame rate and target bitrate from ProtectionBitrateCalculator::SetEncodingData

Remove frame rate and target bitrate from ProtectionBitrateCalculator::SetEncodingData
These arguments are not really known when calling SetEncodingData. They are still provided as argument to ProtectionBitrateCalculator::SetTargetRates though.

This cl is broken out from https://codereview.webrtc.org/2060403002/
BUG=webrtc:5687
Committed: https://crrev.com/c2c24f795eba0ba2a13bbd0d75f87696bd7a484b
Cr-Commit-Position: refs/heads/master@{#13429}

[perkj_webrtc, 2016-07-05 09:51:16]

perkj@webrtc.org changed reviewers:
+ stefan@webrtc.org

[perkj_webrtc, 2016-07-05 09:51:17]

please

[stefan-webrtc, 2016-07-08 12:04:38]

AFAICT this is a noop since UpdateMethod() is called in SetTargetRates.

lgtm

[perkj_webrtc, 2016-07-08 12:45:25]

The CQ bit was checked by perkj@webrtc.org

[commit-bot: I haz the power, 2016-07-08 12:45:30]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-07-08 14:46:11]

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

[commit-bot: I haz the power, 2016-07-08 14:46:15]

Try jobs failed on following builders:
  android_arm64_rel on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL)
  android_dbg on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL)

[perkj_webrtc, 2016-07-11 07:52:54]

The CQ bit was checked by perkj@webrtc.org

[commit-bot: I haz the power, 2016-07-11 07:52:57]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-07-11 08:47:39]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-07-11 08:47:41]

Description was changed from

==========
Remove frame rate and target bitrate from
ProtectionBitrateCalculator::SetEncodingData
These arguments are not really known when calling SetEncodingData. They are
still provided as argument to ProtectionBitrateCalculator::SetTargetRates
though.

This cl is broken out from https://codereview.webrtc.org/2060403002/
BUG=webrtc:5687
==========

to

==========
Remove frame rate and target bitrate from
ProtectionBitrateCalculator::SetEncodingData
These arguments are not really known when calling SetEncodingData. They are
still provided as argument to ProtectionBitrateCalculator::SetTargetRates
though.

This cl is broken out from https://codereview.webrtc.org/2060403002/
BUG=webrtc:5687

Committed: https://crrev.com/c2c24f795eba0ba2a13bbd0d75f87696bd7a484b
Cr-Commit-Position: refs/heads/master@{#13429}
==========

[commit-bot: I haz the power, 2016-07-11 08:47:42]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-11 08:47:42]

Patchset 2 (id:??) landed as
https://crrev.com/c2c24f795eba0ba2a13bbd0d75f87696bd7a484b
Cr-Commit-Position: refs/heads/master@{#13429}