W3C home > Mailing lists > Public > public-media-fragment@w3.org > February 2014

Re: Media Fragments - Video fragment temporal loop

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 28 Feb 2014 21:11:29 +1100
Message-ID: <CAHp8n2kD+YSOOOcLuXa7hF=L+NPMKaMvcvVG6+xf80R10Db8fQ@mail.gmail.com>
To: Philip Jägenstedt <philipj@opera.com>
Cc: Media Fragment <public-media-fragment@w3.org>, Leeroy <soupress@gmail.com>, Raphaël Troncy <raphael.troncy@eurecom.fr>, Eric Carlson <eric.carlson@apple.com>
On 28 Feb 2014 17:46, "Philip Jägenstedt" <philipj@opera.com> wrote:
> On Fri, Feb 28, 2014 at 6:54 AM, Silvia Pfeiffer
> <silviapfeiffer1@gmail.com> wrote:
> > On Fri, Feb 28, 2014 at 4:16 AM, Eric Carlson <eric.carlson@apple.com>
> >>
> >> On Feb 27, 2014, at 8:31 AM, Philip Jägenstedt <philipj@opera.com>
> >>
> >>> On Thu, Feb 27, 2014 at 10:53 PM, Raphaël Troncy
> >>> <raphael.troncy@eurecom.fr> wrote:
> >>>
> >>>> What about <video>? And let's not looking at corner cases such as
> >>>> People are sharing *real* fragments!
> >>>
> >>> The problem is the same with video, if you want to loop a particular
> >>> scene over and over you don't want a random number of frames from the
> >>> following scene to be shown just before the loop. This will happen if
> >>> the looping isn't implemented inside the media framework.
> >>>
> >>
> >>   For whatever it is worth, I agree with Philip - consistent and
accurate gapless looping is not possible without low level support from the
media engine.
> >
> > Isn't that true also for looping over full files? So doesn't that mean
> > that the @loop attribute is useless?
> As Eric pointed out there is a difference. Without media framework
> support looping a fragment will play beyond the loop point, while the
> looping the entire resource will pause for a random number of
> milliseconds at each loop. (I honestly don't know if the loop
> attribute is useful or not, since I've never seen it used outside of
> test cases and demos.)

Surely it can't be worse than what we are doing with MSE and HLS.

Also surely browsers will be better at keeping the delay between loops down
compared to apps doing it in JS.

> Will you be filing an HTML bug on the fragment end time issue? Would
> it help inform the discussion to have use counters for when fragment
> start and end times are applied in Blink?

If you could also count how many are using JS to imitate looping (given
that FAIK not all browsers support the loop attribute), then we would get
good numbers of use cases.

Received on Friday, 28 February 2014 10:11:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:48 UTC