Calculate JitterBufferDelayInMs in the new jitter buffer.

Calculate JitterBufferDelayInMs in the new jitter buffer.

JitterBufferDelayInMs is used for the WebRTC-NewVideoJitterBuffer finch
experiment, and therefore needs to be calculated.

BUG=webrtc:5514
Committed: https://crrev.com/be74270ebe61660e6f5512bc6eb5b200d7e334b4
Cr-Commit-Position: refs/heads/master@{#15313}

[philipel, 2016-11-29 10:24:33]

philipel@webrtc.org changed reviewers:
+ stefan@webrtc.org, terelius@webrtc.org

[terelius, 2016-11-29 12:09:15]

https://codereview.webrtc.org/2534093003/diff/1/webrtc/video/receive_statisti...
File webrtc/video/receive_statistics_proxy.cc (right):

https://codereview.webrtc.org/2534093003/diff/1/webrtc/video/receive_statisti...
webrtc/video/receive_statistics_proxy.cc:96: if
(!(field_trial::FindFullName("WebRTC-NewVideoJitterBuffer") ==
Shouldn't we add some corresponding metric if the new jitter buffer is used?
Maybe reduce the number of parenthesis by using "!=" instead?

[philipel, 2016-11-29 12:34:52]

https://codereview.webrtc.org/2534093003/diff/1/webrtc/video/receive_statisti...
File webrtc/video/receive_statistics_proxy.cc (right):

https://codereview.webrtc.org/2534093003/diff/1/webrtc/video/receive_statisti...
webrtc/video/receive_statistics_proxy.cc:96: if
(!(field_trial::FindFullName("WebRTC-NewVideoJitterBuffer") ==
On 2016/11/29 12:09:15, terelius wrote:
> Shouldn't we add some corresponding metric if the new jitter buffer is used?

See frame_buffer.cc:388.

> Maybe reduce the number of parenthesis by using "!=" instead?

Done :)

[terelius, 2016-11-29 12:59:53]

lgtm

[philipel, 2016-11-29 14:36:50]

The CQ bit was checked by philipel@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-29 14:37:03]

Dry run: 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-11-29 14:54:10]

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

[commit-bot: I haz the power, 2016-11-29 14:54:11]

Dry run: This issue passed the CQ dry run.

[stefan-webrtc, 2016-11-29 17:50:47]

lgtm

[philipel, 2016-11-30 09:30:04]

The CQ bit was checked by philipel@webrtc.org

[commit-bot: I haz the power, 2016-11-30 09:30:07]

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-11-30 09:31:40]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1480498204633910,
"parent_rev": "ef523abcbfefe94dad438c32a13beb05b05708f7", "commit_rev":
"0389f8a28949647e490c8f385fbc9c4866fcb5af"}

[commit-bot: I haz the power, 2016-11-30 09:31:43]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-11-30 09:31:51]

Description was changed from

==========
Calculate JitterBufferDelayInMs in the new jitter buffer.

JitterBufferDelayInMs is used for the WebRTC-NewVideoJitterBuffer finch
experiment, and therefore needs to be calculated.

BUG=webrtc:5514
==========

to

==========
Calculate JitterBufferDelayInMs in the new jitter buffer.

JitterBufferDelayInMs is used for the WebRTC-NewVideoJitterBuffer finch
experiment, and therefore needs to be calculated.

BUG=webrtc:5514

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

[commit-bot: I haz the power, 2016-11-30 09:31:52]

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