diff options
author | rockot@chromium.org <rockot@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-04-18 16:11:58 +0000 |
---|---|---|
committer | rockot@chromium.org <rockot@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-04-18 16:11:58 +0000 |
commit | dc5662c95d6bbf3532bd91aa1ee4e5cbd890dc35 (patch) | |
tree | 0e6ee4a7293598fc41a89b14a34dafd2da70c8cc /media/ffmpeg | |
parent | 238c1f94c09dcc23f0c40549cfc8862deffa5610 (diff) | |
download | chromium_src-dc5662c95d6bbf3532bd91aa1ee4e5cbd890dc35.zip chromium_src-dc5662c95d6bbf3532bd91aa1ee4e5cbd890dc35.tar.gz chromium_src-dc5662c95d6bbf3532bd91aa1ee4e5cbd890dc35.tar.bz2 |
Revert 264766 "Simplify AudioSplicer logic which slots buffers b..."
Possible candidate for broken media_unittests:
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%28dbg%29%281%29/builds/30043/steps/media_unittests/logs/MediaSource_MP3_TimestampOffset_0
> Simplify AudioSplicer logic which slots buffers before or after a splice point.
>
> Since the first post splice buffer after the config change has a splice_timestamp()
> of kNoTimestamp() we can definitively say when we have the first post splice
> buffer instead of having to relying on a problematic timestamp match.
>
> The new code makes it so that clients must always call SetSpliceTimestamp() with
> kNoTimestamp() once the first post splice buffer is received.
>
> BUG=334493
> TEST=existing tests pass.
>
> Review URL: https://codereview.chromium.org/240123004
TBR=dalecurtis@chromium.org
Review URL: https://codereview.chromium.org/243263003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264802 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/ffmpeg')
0 files changed, 0 insertions, 0 deletions