Set correct timestamp in PepperMediaStreamAudioTrack.

Set correct timestamp in PepperMediaStreamAudioTrack.

BUG=476589
Committed: https://crrev.com/609e56235d62d3b1f18202ddff440f0e4f0b711c
Cr-Commit-Position: refs/heads/master@{#327291}

[Peng, 2015-04-14 12:11:37]

penghuang@chromium.org changed reviewers:
+ bbudge@chromium.org

[Peng, 2015-04-14 12:11:38]

PTAL. Thanks.

[bbudge, 2015-04-14 12:19:07]

Hi Peng, thanks for working on this.
I would like to make this change, but I think we have to figure out whether this
will break other users of PPB_AudioBuffer. I commented on the bug about UMA
stats for this API.

[Peng, 2015-04-14 15:52:24]

On 2015/04/14 12:19:07, bbudge wrote:
> Hi Peng, thanks for working on this.
> I would like to make this change, but I think we have to figure out whether
this
> will break other users of PPB_AudioBuffer. I commented on the bug about UMA
> stats for this API.

Any idea about how to figure it out? I cannot find any code uses it in google3.

I guess if some users want to use the timestamp, they probably
they will find and report this bug. Otherwise probably they never used
the timestamp. WDYT?

BTW, pp::VideoFrame::GetTimestamp() returns correct timestamp.

[bbudge, 2015-04-14 17:09:55]

On 2015/04/14 15:52:24, Peng wrote:
> On 2015/04/14 12:19:07, bbudge wrote:
> > Hi Peng, thanks for working on this.
> > I would like to make this change, but I think we have to figure out whether
> this
> > will break other users of PPB_AudioBuffer. I commented on the bug about UMA
> > stats for this API.
> 
> Any idea about how to figure it out? I cannot find any code uses it in
google3.
> 
> I guess if some users want to use the timestamp, they probably
> they will find and report this bug. Otherwise probably they never used
> the timestamp. WDYT?
> 
> BTW, pp::VideoFrame::GetTimestamp() returns correct timestamp.

I'm worried that someone is using the timestamp in milliseconds and will regress
if we suddenly divide by 1000. I'll ask around to see if anyone knows who is
using it.

[bbudge, 2015-04-27 23:05:32]

Peng, why don't you go ahead and land this? I think it must be Hotwords that's
using the API, and they don't seem to use the timestamp.
LGTM

[Peng, 2015-04-28 14:26:05]

The CQ bit was checked by penghuang@chromium.org

[commit-bot: I haz the power, 2015-04-28 14:26:50]

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

[commit-bot: I haz the power, 2015-04-28 15:12:02]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-28 15:12:59]

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