Revert of Use system timestamp as capture timestamp

Revert of Use system timestamp as capture timestamp (patchset #1 id:1 of https://codereview.chromium.org/1671943003/ )

Reason for revert:
WebRTC part of the issue has been fixed.
Thus we can reland the camera timestamp CL.

Original issue's description:
> Use system timestamp as capture timestamp
>
> For rendering smoothness, we used camera timestamp as capture timestamp,
> but if the clockrate of the camera is different from the system clock,
> it will make audio-video out of sync. So we change it back so far.
>
> This CL is essentially a revert of
> https://codereview.chromium.org/1324683004/
> https://codereview.chromium.org/1421583007/
>
> P.S. An ideal solution is that we should take in camera
> timestamp, but smoothly aligned with system clock. But at
> this point, we should make a quick CL to resolve this issue.
>
> BUG=584015
>
> Committed: https://crrev.com/8e0974d2b27ab55a8df948b86804bf0f11c036e2
> Cr-Commit-Position: refs/heads/master@{#373966}

TBR=dalecurtis@chromium.org,pbos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=584015
Committed: https://crrev.com/10127cd472aa0e25de29b9debfbe1933f39ea7cd
Cr-Commit-Position: refs/heads/master@{#380721}

[qiangchen, 2016-03-10 20:54:03]

Created Revert of Use system timestamp as capture timestamp

[qiangchen, 2016-03-10 20:57:16]

Description was changed from

==========
Revert of Use system timestamp as capture timestamp (patchset #1 id:1 of
https://codereview.chromium.org/1671943003/ )

Reason for revert:
WebRTC part of the issue has been fixed.
Thus we can reland the camera timestamp CL.

Original issue's description:
> Use system timestamp as capture timestamp
> 
> For rendering smoothness, we used camera timestamp as capture timestamp,
> but if the clockrate of the camera is different from the system clock,
> it will make audio-video out of sync. So we change it back so far.
> 
> This CL is essentially a revert of
> https://codereview.chromium.org/1324683004/
> https://codereview.chromium.org/1421583007/
> 
> P.S. An ideal solution is that we should take in camera
> timestamp, but smoothly aligned with system clock. But at
> this point, we should make a quick CL to resolve this issue.
> 
> BUG=584015
> 
> Committed: https://crrev.com/8e0974d2b27ab55a8df948b86804bf0f11c036e2
> Cr-Commit-Position: refs/heads/master@{#373966}

TBR=dalecurtis@chromium.org,pbos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=584015
==========

to

==========
Revert of Use system timestamp as capture timestamp (patchset #1 id:1 of
https://codereview.chromium.org/1671943003/ )

Reason for revert:
WebRTC part of the issue has been fixed.
Thus we can reland the camera timestamp CL.

Original issue's description:
> Use system timestamp as capture timestamp
> 
> For rendering smoothness, we used camera timestamp as capture timestamp,
> but if the clockrate of the camera is different from the system clock,
> it will make audio-video out of sync. So we change it back so far.
> 
> This CL is essentially a revert of
> https://codereview.chromium.org/1324683004/
> https://codereview.chromium.org/1421583007/
> 
> P.S. An ideal solution is that we should take in camera
> timestamp, but smoothly aligned with system clock. But at
> this point, we should make a quick CL to resolve this issue.
> 
> BUG=584015
> 
> Committed: https://crrev.com/8e0974d2b27ab55a8df948b86804bf0f11c036e2
> Cr-Commit-Position: refs/heads/master@{#373966}

TBR=dalecurtis@chromium.org,pbos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=584015
==========

[qiangchen, 2016-03-10 20:57:16]

qiangchen@chromium.org changed reviewers:
- dalecurtis@chromium.org

[qiangchen, 2016-03-10 20:58:23]

qiangchen@chromium.org changed reviewers:
+ mcasas@chromium.org
- pbos@chromium.org

[qiangchen, 2016-03-10 20:59:25]

This is the Revert CL.
The change is identical with that CL.

[mcasas, 2016-03-10 23:17:44]

On 2016/03/10 20:59:25, qiangchenC wrote:
> This is the Revert CL.
> The change is identical with that CL.

You should ask the original reviewers or, since it
seems to be identical, just send it to the CQ (note
that you already have the TBR= line).

[qiangchen, 2016-03-10 23:26:54]

qiangchen@chromium.org changed reviewers:
- mcasas@chromium.org

[qiangchen, 2016-03-10 23:26:58]

The CQ bit was checked by qiangchen@chromium.org

[commit-bot: I haz the power, 2016-03-10 23:27:56]

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

[commit-bot: I haz the power, 2016-03-10 23:27:58]

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

[commit-bot: I haz the power, 2016-03-10 23:27:59]

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.

[qiangchen, 2016-03-10 23:36:45]

qiangchen@chromium.org changed reviewers:
+ dalecurtis@chromium.org

[qiangchen, 2016-03-10 23:36:45]

Hi, Dale

    This is a revert CL of a previous "revert".

    As danilchap@ fixed the webrtc part in
https://codereview.webrtc.org/1693443002 resolving Audio-Video out-of-sync
issue. We can switch back to use camera timestamps, as they are smoother. I've
tested, it works well.

Thanks.

[DaleCurtis, 2016-03-10 23:38:45]

lgtm

[qiangchen, 2016-03-10 23:40:50]

The CQ bit was checked by qiangchen@chromium.org

[commit-bot: I haz the power, 2016-03-10 23:41:25]

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

[commit-bot: I haz the power, 2016-03-11 04:35:05]

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

[commit-bot: I haz the power, 2016-03-11 04:35:06]

Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[qiangchen, 2016-03-11 20:37:50]

The CQ bit was checked by qiangchen@chromium.org

[commit-bot: I haz the power, 2016-03-11 20:38:35]

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

[commit-bot: I haz the power, 2016-03-11 20:44:52]

Description was changed from

==========
Revert of Use system timestamp as capture timestamp (patchset #1 id:1 of
https://codereview.chromium.org/1671943003/ )

Reason for revert:
WebRTC part of the issue has been fixed.
Thus we can reland the camera timestamp CL.

Original issue's description:
> Use system timestamp as capture timestamp
> 
> For rendering smoothness, we used camera timestamp as capture timestamp,
> but if the clockrate of the camera is different from the system clock,
> it will make audio-video out of sync. So we change it back so far.
> 
> This CL is essentially a revert of
> https://codereview.chromium.org/1324683004/
> https://codereview.chromium.org/1421583007/
> 
> P.S. An ideal solution is that we should take in camera
> timestamp, but smoothly aligned with system clock. But at
> this point, we should make a quick CL to resolve this issue.
> 
> BUG=584015
> 
> Committed: https://crrev.com/8e0974d2b27ab55a8df948b86804bf0f11c036e2
> Cr-Commit-Position: refs/heads/master@{#373966}

TBR=dalecurtis@chromium.org,pbos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=584015
==========

to

==========
Revert of Use system timestamp as capture timestamp (patchset #1 id:1 of
https://codereview.chromium.org/1671943003/ )

Reason for revert:
WebRTC part of the issue has been fixed.
Thus we can reland the camera timestamp CL.

Original issue's description:
> Use system timestamp as capture timestamp
> 
> For rendering smoothness, we used camera timestamp as capture timestamp,
> but if the clockrate of the camera is different from the system clock,
> it will make audio-video out of sync. So we change it back so far.
> 
> This CL is essentially a revert of
> https://codereview.chromium.org/1324683004/
> https://codereview.chromium.org/1421583007/
> 
> P.S. An ideal solution is that we should take in camera
> timestamp, but smoothly aligned with system clock. But at
> this point, we should make a quick CL to resolve this issue.
> 
> BUG=584015
> 
> Committed: https://crrev.com/8e0974d2b27ab55a8df948b86804bf0f11c036e2
> Cr-Commit-Position: refs/heads/master@{#373966}

TBR=dalecurtis@chromium.org,pbos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=584015
==========

[commit-bot: I haz the power, 2016-03-11 20:44:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-11 20:47:07]

Description was changed from

==========
Revert of Use system timestamp as capture timestamp (patchset #1 id:1 of
https://codereview.chromium.org/1671943003/ )

Reason for revert:
WebRTC part of the issue has been fixed.
Thus we can reland the camera timestamp CL.

Original issue's description:
> Use system timestamp as capture timestamp
> 
> For rendering smoothness, we used camera timestamp as capture timestamp,
> but if the clockrate of the camera is different from the system clock,
> it will make audio-video out of sync. So we change it back so far.
> 
> This CL is essentially a revert of
> https://codereview.chromium.org/1324683004/
> https://codereview.chromium.org/1421583007/
> 
> P.S. An ideal solution is that we should take in camera
> timestamp, but smoothly aligned with system clock. But at
> this point, we should make a quick CL to resolve this issue.
> 
> BUG=584015
> 
> Committed: https://crrev.com/8e0974d2b27ab55a8df948b86804bf0f11c036e2
> Cr-Commit-Position: refs/heads/master@{#373966}

TBR=dalecurtis@chromium.org,pbos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=584015
==========

to

==========
Revert of Use system timestamp as capture timestamp (patchset #1 id:1 of
https://codereview.chromium.org/1671943003/ )

Reason for revert:
WebRTC part of the issue has been fixed.
Thus we can reland the camera timestamp CL.

Original issue's description:
> Use system timestamp as capture timestamp
>
> For rendering smoothness, we used camera timestamp as capture timestamp,
> but if the clockrate of the camera is different from the system clock,
> it will make audio-video out of sync. So we change it back so far.
>
> This CL is essentially a revert of
> https://codereview.chromium.org/1324683004/
> https://codereview.chromium.org/1421583007/
>
> P.S. An ideal solution is that we should take in camera
> timestamp, but smoothly aligned with system clock. But at
> this point, we should make a quick CL to resolve this issue.
>
> BUG=584015
>
> Committed: https://crrev.com/8e0974d2b27ab55a8df948b86804bf0f11c036e2
> Cr-Commit-Position: refs/heads/master@{#373966}

TBR=dalecurtis@chromium.org,pbos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=584015

Committed: https://crrev.com/10127cd472aa0e25de29b9debfbe1933f39ea7cd
Cr-Commit-Position: refs/heads/master@{#380721}
==========

[commit-bot: I haz the power, 2016-03-11 20:47:09]

Patchset 1 (id:??) landed as
https://crrev.com/10127cd472aa0e25de29b9debfbe1933f39ea7cd
Cr-Commit-Position: refs/heads/master@{#380721}