[Media, Video] Update WMPI when the pipeline gets a new average keyframe distance.

[Media, Video] Update WMPI when the pipeline gets a new average keyframe distance.

BUG=688618
TEST=manually followed the repro steps from the bug

Review-Url: https://codereview.chromium.org/2688383006
Cr-Commit-Position: refs/heads/master@{#450186}
Committed: https://chromium.googlesource.com/chromium/src/+/eecec52c10dffeebd35d273a8999388f98089b80

[whywhat, 2017-02-13 22:29:09]

avayvod@chromium.org changed reviewers:
+ watk@chromium.org

[whywhat, 2017-02-13 22:29:10]

PTaL

[whywhat, 2017-02-13 22:29:15]

The CQ bit was checked by avayvod@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-02-13 22:29:57]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[watk, 2017-02-13 22:54:33]

Did you consider having the distance average outlive decoder_stream? It's
slightly inconsistent that we keep the average after a seek, but don't after a
suspend. 

I guess ReportStatistics would have to report a keyframe distance once for every
new keyframe, and RendererWrapper would average them.

That's pretty weird though, so this lgtm.

[commit-bot: I haz the power, 2017-02-14 00:05:55]

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

[commit-bot: I haz the power, 2017-02-14 00:05:56]

Dry run: This issue passed the CQ dry run.

[whywhat, 2017-02-14 01:17:08]

On 2017/02/13 at 22:54:33, watk wrote:
> Did you consider having the distance average outlive decoder_stream? It's
slightly inconsistent that we keep the average after a seek, but don't after a
suspend. 
> 
> I guess ReportStatistics would have to report a keyframe distance once for
every new keyframe, and RendererWrapper would average them.
> 
> That's pretty weird though, so this lgtm.

I thought about keeping a cached value in WMPI or PipelineImpl and only update
it with something coming from the stream that's not a kInfinity hoping that if
the source changes, Pipeline is recreated or at least I could reset the value
then.

[whywhat, 2017-02-14 01:17:16]

The CQ bit was checked by avayvod@chromium.org

[commit-bot: I haz the power, 2017-02-14 01:18:20]

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

[commit-bot: I haz the power, 2017-02-14 01:25:16]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487035036975950, "parent_rev":
"352682e3c9a3d4b9a6b2147e9b8573b449f71b37", "commit_rev":
"eecec52c10dffeebd35d273a8999388f98089b80"}

[commit-bot: I haz the power, 2017-02-14 01:26:14]

Description was changed from

==========
[Media, Video] Update WMPI when the pipeline gets a new average keyframe
distance.

BUG=688618
TEST=manually followed the repro steps from the bug
==========

to

==========
[Media, Video] Update WMPI when the pipeline gets a new average keyframe
distance.

BUG=688618
TEST=manually followed the repro steps from the bug

Review-Url: https://codereview.chromium.org/2688383006
Cr-Commit-Position: refs/heads/master@{#450186}
Committed:
https://chromium.googlesource.com/chromium/src/+/eecec52c10dffeebd35d273a8999...
==========

[commit-bot: I haz the power, 2017-02-14 01:26:17]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/eecec52c10dffeebd35d273a8999...