> On Sep 1, 2015, at 4:03 , Robert O'Callahan wrote:
>
> On Tue, Sep 1, 2015 at 8:02 PM, Kevin Marks wrote:
>
>> QuickTime supports full variable speed playback and has done for well over
>> a decade. With bidirectionally predicted frames you need a
On Tue, Sep 1, 2015 at 10:55 AM, David Singer wrote:
>
> > On Sep 1, 2015, at 10:47 , Yay295 wrote:
> >
> > On Tue, Sep 1, 2015 at 11:30 AM, David Singer wrote:
> > > On Sep 1, 2015, at 4:03 , Robert O'Callahan
>
On Tue, Sep 1, 2015 at 11:57 AM, David Singer wrote:
>
> > On Sep 1, 2015, at 11:36 , Kevin Marks wrote:
> > > I suppose the browser could generate this data the first time it reads
> through the video. It would use a lot less memory. Though that sounds
> On Sep 1, 2015, at 11:36 , Kevin Marks wrote:
> > I suppose the browser could generate this data the first time it reads
> > through the video. It would use a lot less memory. Though that sounds like
> > a problem for the browsers to solve, not the standard.
>
> There
On Tue, Sep 1, 2015 at 11:30 AM, David Singer wrote:
> > On Sep 1, 2015, at 4:03 , Robert O'Callahan
> wrote:
> >> On Tue, Sep 1, 2015 at 8:02 PM, Kevin Marks
> wrote:
> >> QuickTime supports full variable speed playback and has
> On Sep 1, 2015, at 10:47 , Yay295 wrote:
>
> On Tue, Sep 1, 2015 at 11:30 AM, David Singer wrote:
> > On Sep 1, 2015, at 4:03 , Robert O'Callahan wrote:
> >> On Tue, Sep 1, 2015 at 8:02 PM, Kevin Marks wrote:
>
On Tue, 1 Sep 2015, henry.st...@bblfish.net wrote:
>
> As the WhatWG only recenly moved to Github members here may not have
> noticed that has been deprecated.
>
> I opened https://github.com/whatwg/html/issues/67 to give space for the
> discussion. It is a pitty that this was closed so
On Wed, Sep 2, 2015 at 5:30 AM, David Singer wrote:
> On Sep 1, 2015, at 4:03 , Robert O'Callahan wrote:
> > How about a hard but realistic (IMHO) case: 4K video (4096 x 2160), 25
> fps,
> > keyframe every 10s. Storing all those frames takes 250 x 4096 x
QuickTime supports full variable speed playback and has done for well over
a decade. With bidirectionally predicted frames you need a fair few buffers
anyway, so generalising to full variable wait is easier than posters above
claim - you need to work a GOP at a time, but memory buffering isn't the
As the WhatWG only recenly moved to Github members here may not have noticed
that has been deprecated.
I opened https://github.com/whatwg/html/issues/67 to give space for the
discussion. It is a pitty that this was closed so quickly ( within an hour )
without giving members and the public (
On Mon, Aug 31, 2015 at 9:48 PM, Domenic Denicola wrote:
> From: Eric Carlson [mailto:eric.carl...@apple.com]
>
>> FWIW, Safari supports negative playback rates on the desktop and on iOS.
>>
>> ...
>>
>> The crash Garrett noted in Safari 8 is a bug that “only" happens with
On Tue, Sep 1, 2015 at 8:02 PM, Kevin Marks wrote:
> QuickTime supports full variable speed playback and has done for well over
> a decade. With bidirectionally predicted frames you need a fair few buffers
> anyway, so generalising to full variable wait is easier than
12 matches
Mail list logo