diff options
| author | qinmin@chromium.org <qinmin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-07 00:02:18 +0000 |
|---|---|---|
| committer | qinmin@chromium.org <qinmin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-07 00:02:18 +0000 |
| commit | 03f7f46ea33a54b2e7c3d7f8cc8fb51cfcc370f3 (patch) | |
| tree | 753be9930e7f6a60fc430d25be9464641e0dca0c /chrome/app/resources/google_chrome_strings_gu.xtb | |
| parent | 41d8061535f1cd66721e45e5604fefdff687d720 (diff) | |
| download | chromium_src-03f7f46ea33a54b2e7c3d7f8cc8fb51cfcc370f3.zip chromium_src-03f7f46ea33a54b2e7c3d7f8cc8fb51cfcc370f3.tar.gz chromium_src-03f7f46ea33a54b2e7c3d7f8cc8fb51cfcc370f3.tar.bz2 | |
Use decoder's timestamp instead of the timestamp from AU during prerolling
When prerolling happens, MediaDecoderJob currently rolls to the timestamp from the access unit.
However, for video, the access unit's timestamp may not match that from the decoder due to reordering.
Even worse, the unit's timestamp may be greatly ahead of the presentation timestamp from the decoder since the decoder is still decoding previous access units. Some of the unit tests actually show this problem.
Fixed all the problematic unit tests along with this CL.
BUG=310823
Review URL: https://codereview.chromium.org/113963005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243210 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/app/resources/google_chrome_strings_gu.xtb')
0 files changed, 0 insertions, 0 deletions