- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 5 Apr 2012 17:52:08 +0000 (UTC)
On Thu, 5 Apr 2012, Philip J?genstedt wrote: > On Wed, 04 Apr 2012 20:56:03 +0200, Ian Hickson <ian at hixie.ch> wrote: > > On Wed, 4 Apr 2012, Philip J?genstedt wrote: > > > > > > > > > > In current Opera and Firefox the timeline is always normalized > > > > > to start at 0, so the time that corresponds to 0 in the original > > > > > timeline would be at a negative currentTime. > > > > > > > > I still don't really understand what you mean by "start" here. > > > > > > What I mean with "normalized to start at 0" is that when playing the > > > whole resource > > > > Now I don't understand what you mean by "whole resource". :-) > > > > If a TV station starts broadcasting in October, and you join the > > stream in February, the "whole resource" is many months long. Where's > > your zero? > > > > (I guess it's academic if you plan on changing; I'm just curious.) > > Oh, "whole resource" is a bit of a misnomer, I really mean "everything > that we received". We don't make that distinction internally, since over > HTTP there's no way to tell the difference between a streaming resource > and a static resource served by a server that doesn't support byte > ranges. The timeline is shifted by the timestamp of the first audio or > video sample in the stream, such that currentTime is initially 0. The > plan is to remove that adjustment. Ah, I see. Thanks for clarifying. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 5 April 2012 10:52:08 UTC