diff options
| author | scherkus@chromium.org <scherkus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-21 00:54:17 +0000 |
|---|---|---|
| committer | scherkus@chromium.org <scherkus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-21 00:54:17 +0000 |
| commit | a37ebbc3c152f9e2ff6b1e1726cf6cd2ad4da8a0 (patch) | |
| tree | 4dd861b51dd194af1f7051a4213d350ab63325c8 /chrome/common | |
| parent | 59316ec0027a6e6eec0f71405edc8d2a53039db0 (diff) | |
| download | chromium_src-a37ebbc3c152f9e2ff6b1e1726cf6cd2ad4da8a0.zip chromium_src-a37ebbc3c152f9e2ff6b1e1726cf6cd2ad4da8a0.tar.gz chromium_src-a37ebbc3c152f9e2ff6b1e1726cf6cd2ad4da8a0.tar.bz2 | |
Don't update the clock if we don't have a reliable timestamp available.
Turns out vorbis packets only have an accurate timestamp every second or so while the rest of the packets have a timestamp of zero. Problem was we were overwriting |last_fill_buffer_time_| with zeros and then updating the clock, effectively causing a ton of drift.
Review URL: http://codereview.chromium.org/115593
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16561 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common')
0 files changed, 0 insertions, 0 deletions