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
