Comment #11 on issue 16508 by [email protected]: Implement a proper
clock for the media pipeline
http://code.google.com/p/chromium/issues/detail?id=16508
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=22807
------------------------------------------------------------------------
r22807 | [email protected] | 2009-08-07 15:28:47 -0700 (Fri, 07 Aug
2009) | 12 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/branches/195/src/media/base/mock_filters.h?r1=22807&r2=22806
M
http://src.chromium.org/viewvc/chrome/branches/195/src/media/base/pipeline_impl.cc?r1=22807&r2=22806
M
http://src.chromium.org/viewvc/chrome/branches/195/src/media/base/pipeline_impl_unittest.cc?r1=22807&r2=22806
Merge 21937 - Nice and easy fix for the media clock interpolating past the
duration.
I considered adding duration to Clock itself, but that felt like it would
pollute Clock's simple purposes of keeping track of time. Furthermore, by
keeping duration checking in PipelineImpl we can handle future scenarios
such as streaming media where clock really should run forever.
BUG=16508
TEST=currentTime should never exceed duration
Review URL: http://codereview.chromium.org/159573
[email protected]
Review URL: http://codereview.chromium.org/164196
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
