using netStream.time on rtmp live stream(broadcaster!=receiver)

[*_leif_*]

I am trying to synchronize a live stream (which is broadcasted from the flash
player plugin) with some scripted actions. The problem is, that the displayed
frames of the rtmp stream do not correlate to the netStream.time property on
the receiver side. In fact, i do not understand at all, how the property is
rendered on the receiver, since i can not recognize any dependencies to e.g.
bufferLength.
Does anybody now, how it is calculated? I tried with Red5 and Wowza and they
seem to behave similar. I guess, FMS would not make any difference (if so:
lease let me know!), since i assume that the property is rendered during the
encoding process i.e. by the plugin.

[JayCharles]

I'm not entirely sure I understand the question, but it seems that what you
want to do is trigger actionscript events at certain times in the live stream.

Typically, I would use NetStream.send() for this sort of thing, but since I
don't know how you have your application set up, I can't say for sure whether
that's the best solution for you.

Can you describe things in a little more detail? When you say that the
netstream.time property and the "displayed frames" do not correlate, what do
you mean?

[*_leif_*]

Hello Jay,

thank you for your answer! NetStream.send() seems to be at least a possibility
to solve my problem with a workaround.

I just want to synchronize the time information of the up- and downstream:
both should have the same time information when they show the same visual
content (which i called "frame" in the former post).
What i would suppose the netstream.time to be is that if i shake my camera on
upstream.time=10.0 then downstream.time should equal 10.0 when this camera
shaking is played back. This is the behaviour that i am used to from streaming
prerecorded FLVs. But with live streams things work out diffferently.
In fact my downstream.time is bigger than upstream.time. And i can not imagine
how this can be. If i streamed up for let's say 20 seconds and i start the
downstream after about 10 seconds, i would expect my downstream.time to start
with 10 seconds and then increase continually. But against this, my
downstream.time starts with something above 20. How can this be? Or back to my
initial question: how is the downstream.time rendered?
This behaviour seems not to be dependent on the downstream.bufferTime.

With netStream.send() i could send the upstream.time information via the
upstream to render an offset for downstream.time on receiver side. This should
work (have to check it), but is a workaround, no "clean" solution.