W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2007

[whatwg] media element playback rates

From: Kevin Calhoun <kcalhoun@apple.com>
Date: Mon, 5 Nov 2007 07:44:54 -0800
Message-ID: <8B4C03E0-5C96-439A-9177-82B2B2D29B33@apple.com>

On Nov 2, 2007, at 11:47 PM, Ian Hickson wrote:

> On Fri, 2 Nov 2007, Kevin Calhoun wrote:
>>
>> A consideration in raising this issue now is that in our  
>> prototyping we
>> rediscovered the need for the media engine to be informed in advance,
>> whenever possible, of the rate at which it will be required to  
>> play, in
>> order to prepare itself appropriately.
>
> How far in advance? Would passing an argument to play() satisfy this?
> (i.e. can it be immediately before playback begins, or does it have  
> to be
> measurably earlier?)

Indefinitely earlier -- allowing the media to pass through arbitrary  
states as needed before playback at the requested rate is ready.

>
>> In the alternative model Dave described, the same operations you  
>> enumerated
>> are also readily performed as below [...]
>
> With the proposal, I don't see how you can set the speed in one  
> controller
> and then have another controller do fast-forward and then have the  
> first
> controller resume play again, which is a design requirement for this  
> API.

Multiple controllers of the same media, hmmm. Can you say more about  
these requirements?

- Kevin Calhoun
   Apple Inc./QuickTime
Received on Monday, 5 November 2007 07:44:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:47:42 GMT