[Red5devs] Problem with ping request during (live) streaming
steven.gong at gmail.com
Wed Mar 15 01:20:22 EST 2006
On 3/15/06, Joachim Bauch <jojo at struktur.de> wrote:
> I have a little problem with live streaming through Red5:
> Occasionally the playback at the subscriber stops (i.e. the video is not
> updated any longer), however onMetaData events are triggered and the
> client sends the StreamBytesRead messages periodically. When I reconnect
> the client, the video starts playing again for a while.
You mean the screen freezes when playing a live video? I have never got this
problem, but I found sometimes the screen froze when I switch a stream on
the server side (I changed the code a little in order to achieve the goal of
switching a stream on the fly). The phenomenon is like this:
(a) On application start, I created a published stream "LiveNow" that can be
(b) A client X requests playing "LiveNow". (It should wait because no
(c) Another client Y publishes two stream "LiveP1" and "LiveP2" and connects
MultiSink of "LiveNow" to "LiveP1".
(d) X sees "LiveP1" playing.
(e) The third client Z switches the stream "LiveNow" from "LiveP1" to
(f) X's screen freezes.
Don't know if this has the same root cause as yours.
Almost everytime this issue is triggered, Red5 received a ping request
> containing the values 3, 1 and 100 before, so it looks as if the generated
> response is incorrect. Sometimes it takes only a few seconds until the
> ping is sent, sometimes everything works fine for several minutes.
> Has anybody seen this ping or knows what the correct response would be?
Maybe we can send this ping to FMS and see the output.
> Red5devs mailing list
> Red5devs at osflash.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Red5devs