From: Yvan Gagnon <[EMAIL PROTECTED]>
Subject: Re: detecting server malfunction
If I'm not mistaken, when an encoder disconnects from a server for whatever
reason, the backup "off the air" .rm file that's in the \encoder folder does
NOT interrupt the broken live stream. Listeners who are tuning in to the
live broadcast get disconnected and receive the standard "connection lost"
(or whatever) message like usual and need to reconnect. Only people who are
tuning in to the broadacast after the encoder disconnects will get the "off
the air" stream. Am I mistaken?
There's been talk here in this forum about including multiple lines in a
.ram or .smi file that all point to the same stream, so that if one
disconnects, it'll just move on to the next stream in the list:
rtsp://my.server.com/encoder/live.rm
rtsp://my.server.com/encoder/live.rm
rtsp://my.server.com/encoder/live.rm
rtsp://my.server.com/encoder/live.rm
So in theory, if the encoder disconnects, the client connection / player
will just move on to the next stream, which would be the "off the air"
stream in some cases until the encoder's connection to the server is
restored and the live stream resumes. I've experimented with this using an
.smi file, only it seems as though each clip listed has to be buffered first
prior to playing, and in most cases, that create choppy audio as a person's
RAM gets overloaded with pre-buffered clips. This, however, might be
because my .smi file is set up to crossfade between each of the clips, in
which case pre-buffering would more than likely be necessary.
What is the definitive solution for this? I would like to use an .smi file
to deliver my live broadcast, yet I want to be able to specify the multiple,
same clips (as indicated above) to ensure that a listener doesn't get
totally disconnected and prompted with an ugly gray box telling him that
everything stopped working. Would anyone here know the best way to go about
that?
thanks,
-- [EMAIL PROTECTED]
RealForum wrote:
> From: GlenD <[EMAIL PROTECTED]>
> Subject: Re: detecting server malfunction
>
> Under Win NT, I used the Peformance Monitor sometimes whenI wanted to
> monitor an encoder or server. I set an alarm that would go off when the
> server output bandwidth dropped below a certain level, then I'd check it
> if it did. You can also put a file in the Content dir of your
> Realsserver that has the exact same name of the incoming encoder
> filename, and telling users to call you. Use PowerPoint to make a slate
> that announces that the encoder has died, and to call you at ... Use
> the RealPresenter plugin to make a .rm file. Set the timing to one
> slide per second and have at least six identical announcement slides -
> this allows later slides to clear up the (often smeared) first slide.
