On Mon, 9 Feb 1998, Emmanuel BEUQUE wrote:
> Is the StreamPlaying event of any interest compared to IsRunning (or
> IsAvailable) ?
Yes, ist is an asynchronous event that is generated when the stream _really_
starts playing. The start of an MHEG-5 stream object is not necessary at
exact the same time when the stream is delivered to the client.
> The streamStopped event definition seems not clearer to me :
> [...]
> As the standard says "the last piece of *content* data", I would considered
> that this event is generated as if there were a counterTrigger on the last
> time code of the stream. Does this mean that the StreamStopped event should
> be generated each time the stream loops, if its looping attribute specify
> this, even if the stream continue playing ?
> In this case (stream looping), shall a streamPlaying event be generated
> immediately after the streamStopped event ?
Interesting question. I am not sure myself. I would say that in case of
looping the StreamStopped event is generated when the last piece of data of
the stream has been presented to the user and the stream has finished the
last loop.
Then the stream stops.
> "Note that the RunningStatus of the Stream object is not affected by the
> occurrence of a StreamStopped event."
>
> OK, so this clarify that the stream is not deactivated when the stream is
> finished and has stopped playing.
This just clarifies that the RunningStatus of the the stream is not changed
automatically.
> But may a streamStopped event be generated if the stream is deactivated
> before the last frame has been shown ?
Yes, because the last piece of data has been presented and the stream
stops.
Maybe it helps if you regard the stream as a streamed file (which it actually
is most of the time...) when the stream is "closed" the streaming ends.
Andreas
-- o _ Andreas Kraft (\_|_) GMD FOKUS, kraft@fokus.gmd.de, +49 30 3463-7232 T> ] [ The sky is the limit