Initialize media timeline correctly for positive start times.

media/filters/ffmpeg_demuxer.h

Index: media/filters/ffmpeg_demuxer.h
diff --git a/media/filters/ffmpeg_demuxer.h b/media/filters/ffmpeg_demuxer.h
index 9680b26310cc8761a1fab4a25affd90a7bc3e1cd..d2855e0d97432d0c01617eb24e88ce3dc709196a 100644
--- a/media/filters/ffmpeg_demuxer.h
+++ b/media/filters/ffmpeg_demuxer.h
@@ -168,6 +168,7 @@ class MEDIA_EXPORT FFmpegDemuxer : public Demuxer {
   virtual void Seek(base::TimeDelta time, const PipelineStatusCB& cb) OVERRIDE;
   virtual base::Time GetTimelineOffset() const OVERRIDE;
   virtual DemuxerStream* GetStream(DemuxerStream::Type type) OVERRIDE;
+  virtual base::TimeDelta GetStartTime() const OVERRIDE;
   virtual Liveness GetLiveness() const OVERRIDE;
 
   // Calls |need_key_cb_| with the initialization data encountered in the file.
@@ -179,8 +180,9 @@ class MEDIA_EXPORT FFmpegDemuxer : public Demuxer {
   void NotifyCapacityAvailable();
   void NotifyBufferingChanged();
 
-  // The lowest demuxed timestamp.  DemuxerStream's must use this to adjust
-  // packet timestamps such that external clients see a zero-based timeline.
+  // The lowest demuxed timestamp.  If negative, DemuxerStreams must use this to
+  // adjust packet timestamps such that external clients see a zero-based
+  // timeline.

[scherkus (not reviewing), 2014/09/16 00:16:51]

can you refresh my memory as to what's the impact of having negative timestamps
vs. just letting them flow through?

[DaleCurtis, 2014/09/16 01:17:50]

The HTML5 specification says we must only expose positive timestamps, letting
them through would expose the original issue: http://crbug.com/377295

   base::TimeDelta start_time() const { return start_time_; }
 
  private: