Propagate input capture time in ViEEncoder::OnFrame.

Propagate input capture time in ViEEncoder::OnFrame.

BUG=webrtc:6977
Review-Url: https://codereview.webrtc.org/2763023002
Cr-Commit-Position: refs/heads/master@{#18351}
Committed: https://chromium.googlesource.com/external/webrtc/+/01d5a0b48d04f1d6cd8aee40d6e064a3d479f991

[nisse-webrtc, 2017-03-21 13:36:57]

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

[commit-bot: I haz the power, 2017-03-21 13:37:04]

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, 2017-03-21 13:45:16]

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

[commit-bot: I haz the power, 2017-03-21 13:45:17]

Dry run: Try jobs failed on following builders:
  linux_ubsan_vptr on master.tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/linux_ubsan_vptr/builds...)

[nisse-webrtc, 2017-05-29 13:10:59]

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

[nisse-webrtc, 2017-05-29 13:11:00]

PTAL, this fixes an old TODO from earlier timestamp refactoring.

[stefan-webrtc, 2017-05-30 09:48:13]

How sure are we that this is safe with for instance the problematic logitech
cameras we've had problems with before?

Should we take the safe route and enable it behind an field trial and look at
some stats in Chrome before we decide to turn it on by default?

[nisse-webrtc, 2017-05-30 10:45:47]

On 2017/05/30 09:48:13, stefan-webrtc wrote:
> How sure are we that this is safe with for instance the problematic logitech
> cameras we've had problems with before?

I think it's reasonably safe, the "new" timestamp is already propagated in the
ntp timestamp,
the change is that it is now propagated in timestamp_us, and it shouldn't differ
by more than a couple of ms from the current time that used to be written there.

But if you want to teach me how to do a field trial, we could do that too.

[nisse-webrtc, 2017-05-30 15:02:35]

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

[commit-bot: I haz the power, 2017-05-30 15:02:43]

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, 2017-05-30 16:11:43]

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

[commit-bot: I haz the power, 2017-05-30 16:11:44]

Dry run: This issue passed the CQ dry run.

[stefan-webrtc, 2017-05-31 13:27:14]

lgtm

We should monitor the av sync stats to ensure that this doesn't cause issues.

[nisse-webrtc, 2017-05-31 13:31:00]

The CQ bit was checked by nisse@webrtc.org

[commit-bot: I haz the power, 2017-05-31 13:31:05]

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, 2017-05-31 13:33:22]

CQ is committing da patch.

Bot data: {"patchset_id": 60001, "attempt_start_ts": 1496237460041190,
"parent_rev": "8b2b9efab68a55beb7112a60bdb80bcb8425f2e6", "commit_rev":
"01d5a0b48d04f1d6cd8aee40d6e064a3d479f991"}

[commit-bot: I haz the power, 2017-05-31 13:33:26]

Description was changed from

==========
Propagate input capture time in ViEEncoder::OnFrame.

BUG=webrtc:6977
==========

to

==========
Propagate input capture time in ViEEncoder::OnFrame.

BUG=webrtc:6977

Review-Url: https://codereview.webrtc.org/2763023002
Cr-Commit-Position: refs/heads/master@{#18351}
Committed:
https://chromium.googlesource.com/external/webrtc/+/01d5a0b48d04f1d6cd8aee40d...
==========

[commit-bot: I haz the power, 2017-05-31 13:33:27]

Committed patchset #4 (id:60001) as
https://chromium.googlesource.com/external/webrtc/+/01d5a0b48d04f1d6cd8aee40d...