On Thu, 26 Feb 1998 15:59:15 +0100 (MET),
Andreas Zisowsky <zisowsky@fokus.gmd.de> said:
> 1. Since the action SetCounterPosition is allowed for non-active
> Streams, I guess the Activation behaviour takes the CounterPosition
> into account and starts the stream at the given position, right?
Yes.
> Since the attribute CounterPosition is the "current temporal
> position", it will point to the end of the stream, when it is
> finished. What about the next "Run"? The Deactivation behaviour
> does not specify, if CounterPosition is reset to the beginning of
> the stream or reset to the last position set by SetCounterPosition.> So, to replay the stream again, it is necessary to call
> SetCounterPosition (... 0) before every "Run", correct?
If you would like to restart the stream which is terminated normally,
you have to reset CounterPosition by action.
> 2. In the SetCounterPosition action is mentioned that it does not
> generate any Stream events. Hence, a SetCounterPosition behind the
> end of the currently active Stream even does not generate a
> StreamStopped event?
Yes, but PoU in this section mentioned, "NewCounterPosition shall
indicate a valid position within the target Stream", so you can't
set it behind the end of the Stream.
> 3. If a SetCounterEndPosition is set, then the value of Looping is
> ignored, correct?
My understanding, it is still alive, when current CounterPosion has
not reached NewCounterEndPosition. (but not mentioned in standard)
The position is already passed, Steam is stopped and looping is
ignored.(derived from SetCounterEndPosition 37.4)
-----
Yoshiharu Dewa
Pioneer Corp. Corporated Research and Development lab.
E-Mail: dewa@crdl.pioneer.co.jp
URL: http://www.pioneer.co.jp/crdl/staff/dewa/profile.html