If not it might wait until it becomes active (and the regular program/playlist continues like normally).
Once the watched URL becomes active and alive the ModStream-Player might mute or suspend the currently running program and play the monitored URL stream.
This until the ModStream Player is stopped.
To do the above, two control-commands are provided. A START and a STOP command.
The START command starts the ModStream-Player and thus starts monitoring the given URL stream.
The STOP commands stops the monitoring and/or playing of such stream and closes the ModStream-Player.
See below for the detailed syntax.
The START/STOP commands can be either issued manually (e.g. via user command buttons) or automatically (e.g. via appropriate Program Scheduler entries).
As explained, the MODStream-Watcher is a feature to e.g. enable automatic remote moderators or external broadcasts to tune in to a dedicated streaming server (e.g. a SHOUTcast server). Eg. a remote moderator is streaming his live show from a distant location, eg. from his remote location to a specific/dedicated moderator streaming server.
So the MODStream-Watcher allows you to check, if that specific/dedicated moderator streaming server is currently online (meaning a DJ is currently streaming his live show) - if yes, that MODStream will be played and a current program will be suspended.
You define your regular program as is within the program scheduler.
E.g. assume this by scheduling a full 24 by 7 program.
This includes those 'special' programs which are typically 'hosted' by your remote moderators/DJs.
Let's say there is one 'special' program which starts at 10am and ends at 11am - but is normally hosted 'remotely' by a DJ.
You anyhow define such a program within the scheduler (just in case the remote speaker is suddenly unavailable).
But in addition you define certain 'control-commands' to exectute when such program is starting/stopping.
With these control-commands you can actually start/stop the MODStream feature for that special program.
To do so...
Within the 'Program Editor' click on the 'Control-Commands' button...
In the following dialog specify the following:
For "Program Starting":
Code: Select all
1st: the URL address to monitor
2nd: max. playtime in seconds (when 0 it plays forever until the STOP command)
3rd: stopPlaylist, true to turn AutoPlay off
4th: startWithNextTrack, false to start immediate
5th: songTitle, optional initial song title
For "Program Stopped":
Code: Select all
Note: replace the <url> with the full streaming server Url of the remote server to listen to!
What is now happening is the following:
When the 'special' program is about to be starting the control-command "MODSTREAM_WATCHER_START <url>|0|true|true" is executed.
This command will actually start the MODStream-Player and starts listening to the given <url>.
If the <url> is live and active it will connect to it and play it (the other parameters tell the system to 'suspend' any currently running playlist if the MODStream is playing).
If the <url> is not available or live, the MODStream-Player will wait and try to (re)connect - and any regular program/playlist will continue to play.
This will happen until the "MODSTREAM_WATCHER_STOP" command is called.
As such in between a "MODSTREAM_WATCHER_START" and "MODSTREAM_WATCHER_STOP" command any remote speaker can kind of 'tune-in" at the given <url> and if, any regular program is suspend...and finally resumed when either the remote speaker disconnects or the STOP command is given.