On Wed, 18 Aug 2010, Silvia Pfeiffer wrote:
On Wed, Aug 18, 2010 at 11:13 AM, Ian Hickson i...@hixie.ch wrote:
Agreed. I've made the API clearly say that duration is the time at
the end, even in the case where the start is not actually zero, to
sidestep this issue somewhat. (The start
On Wed, 18 Aug 2010 09:44:30 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 18, 2010 at 11:13 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 24 May 2010, Philip Jägenstedt wrote:
I think we both agree but aren't understanding each other very well,
or
I'm
not
On Mon, Aug 23, 2010 at 11:03 PM, Philip Jägenstedt phil...@opera.com wrote:
It's too late, all scripted controls for video that display a timeline are
already using the duration property.
And they're probably using it as a duration not an end time. Doesn't
this change cause problems?
--
On Mon, 23 Aug 2010 13:15:00 +0200, Chris Double
chris.dou...@double.co.nz wrote:
On Mon, Aug 23, 2010 at 11:03 PM, Philip Jägenstedt phil...@opera.com
wrote:
It's too late, all scripted controls for video that display a
timeline are
already using the duration property.
And they're
On Wed, Aug 18, 2010 at 11:13 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 24 May 2010, Philip Jägenstedt wrote:
I think we both agree but aren't understanding each other very well, or
I'm
not thinking very clearly. People will write players assuming that
currentTime
starts at 0 and
I've defined an explicit concept of a media timeline and defined how you
use it, which should make a lot of video-related issues better.
On Mon, 17 May 2010, Odin Omdal H�rthe wrote:
I stream conferences using Ogg Theora+Vorbis using Icecast2. I have
built a site that shows the video and
On Mon, May 24, 2010 at 5:54 PM, Philip Jägenstedt phil...@opera.comwrote:
So from this I gather that either:
1. initialTime is always 0
or
2. duration is not the duration of resource, but the time at the end.
I wouldn't say that. If you can seek backwards to before the initial time,
On Mon, 24 May 2010 08:14:47 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Mon, May 24, 2010 at 5:54 PM, Philip Jägenstedt
phil...@opera.comwrote:
So from this I gather that either:
1. initialTime is always 0
or
2. duration is not the duration of resource, but the time at the
On Mon, May 24, 2010 at 10:13 PM, Philip Jägenstedt phil...@opera.comwrote:
Oh, so the idea is that the earlier data might actually be seekable, it's
just that the UA seeks to an offset, much like with media fragments? The
exception might be live streaming, where the duration is +Inf anyway.
On Mon, 24 May 2010 12:33:56 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Mon, May 24, 2010 at 10:13 PM, Philip Jägenstedt
phil...@opera.comwrote:
Oh, so the idea is that the earlier data might actually be seekable,
it's
just that the UA seeks to an offset, much like with
On Mon, May 24, 2010 at 4:14 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Mon, May 24, 2010 at 5:54 PM, Philip Jägenstedt phil...@opera.com
wrote:
So from this I gather that either:
1. initialTime is always 0
or
2. duration is not the duration of resource, but the time at the
On Mon, May 24, 2010 at 11:29 PM, Silvia Pfeiffer silviapfeiff...@gmail.com
wrote:
Here's how I've understood it would work with the attributes:
* currentTime is the video's timeline as described, so since we are at
offset (3), currentTime = t2.
* initialTime = t1, namely the offset at where
I think it rather important that the format define where you are in time,
precisely so that temporal fragments, or syncing with other material, can work.
For most video-on-demand, the program starts at zero and runs to its duration.
But for 'streaming', knowing 'where you are' in a stream
On Tue, May 18, 2010 at 9:46 PM, Silvia Pfeiffer
silviapfeiff...@gmail.comwrote:
To be honest, it doesn't make much sense to display the wrong time
in a player. If a video stream starts at 10:30am and goes for 30 min,
then a person joining the stream 10 min in should see a time of 10min
- or
On Mon, May 24, 2010 at 11:03 AM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Tue, May 18, 2010 at 9:46 PM, Silvia Pfeiffer silviapfeiff...@gmail.com
wrote:
To be honest, it doesn't make much sense to display the wrong time
in a player. If a video stream starts at 10:30am and goes for 30
On Mon, May 24, 2010 at 2:55 PM, Silvia Pfeiffer
silviapfeiff...@gmail.comwrote:
Just to clarify: what time would a video display as it is playing back
in the browser?
The currentTime+realTimeOffset (if any), where currentTime would
include any initialPlaybackOffset?
Yes.
Rob
--
He was
On Mon, 24 May 2010 03:03:15 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Tue, May 18, 2010 at 9:46 PM, Silvia Pfeiffer
silviapfeiff...@gmail.comwrote:
To be honest, it doesn't make much sense to display the wrong time
in a player. If a video stream starts at 10:30am and goes for
On Mon, May 24, 2010 at 1:52 PM, Philip Jägenstedt phil...@opera.com wrote:
On Mon, 24 May 2010 03:03:15 +0200, Robert O'Callahan rob...@ocallahan.org
wrote:
On Tue, May 18, 2010 at 9:46 PM, Silvia Pfeiffer
silviapfeiff...@gmail.comwrote:
To be honest, it doesn't make much sense to display
On Mon, May 24, 2010 at 3:52 PM, Philip Jägenstedt phil...@opera.comwrote:
On Mon, 24 May 2010 03:03:15 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
Here's how I think it should work:
-- currentTime (and related times, such as times in TimeRanges) range from
0
to 'duration'
--
On Mon, 24 May 2010 07:23:05 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Mon, May 24, 2010 at 3:52 PM, Philip Jägenstedt
phil...@opera.comwrote:
On Mon, 24 May 2010 03:03:15 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
Here's how I think it should work:
--
On Tue, May 18, 2010 at 8:23 PM, Odin Omdal Hørthe odin.om...@gmail.comwrote:
Justin Dolske's idea looks rather nice:
This seems like a somewhat unfortunate thing for the spec, I bet
everyone's
going to get it wrong because it won't be common. :( I can't help but
wonder if
it would be
On Tue, May 18, 2010 at 7:28 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Tue, May 18, 2010 at 8:23 PM, Odin Omdal Hørthe odin.om...@gmail.com
wrote:
Justin Dolske's idea looks rather nice:
This seems like a somewhat unfortunate thing for the spec, I bet
everyone's
going to get
On May 17, 2010, at 14:31 , Odin Omdal Hørthe wrote:
Hello!
I filed bugs at mozilla and in chromium because I want to sync real
time data stream to live video. Some of them told me to send it here
as well. :-)
It's only possible to get relative playtime with html5 in javascript. I
want
I think he means something similar to what QuickTime broadcaster and quicktime
streaming server does with a delay on a live stream or wowza media server with
flash media encoder when using h.264, unless I am misunderstanding something.
Is that correct Odin? Not sure how ice cast deals with it
On Tue, May 18, 2010 at 7:31 AM, Odin Omdal Hørthe odin.om...@gmail.com wrote:
Hello!
I filed bugs at mozilla and in chromium because I want to sync real
time data stream to live video. Some of them told me to send it here
as well. :-)
It's only possible to get relative playtime with html5
25 matches
Mail list logo
