| View previous topic :: View next topic |
| Author |
Message |
Anonymous Guest
|
Posted: Sat Aug 19, 2006 10:01 am Post subject: Disconnect of listeners after DJ change |
|
|
Hello all,
any idea or experience how to prevent client disconnetcs by changing of DJs?
The DJs changes are very fast, approx. 2 - 5 seconds, one goes offl, the next klicks on connect and start the live stream. Both sending the same bitrate, but the listener have to reconnect after the change, means they get discconect from the server.
Regards, Adam |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sat Aug 19, 2006 12:14 pm Post subject: |
|
|
The disconnecting of listeners is expected as long as you don't have an active fallback specified. The fallback mount can be a file or a locally fed playlist as long as it matches the format of the streams from the DJs. Lokk at the mount options for fallback-mount and fallback-override.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sat Aug 19, 2006 1:27 pm Post subject: |
|
|
Thanks Karl, this I tested already, but using a fallback file the strean server could be 24/7 onair if clients are connected night and day, listening to a loop.
You must also put the fallback.mp3 under the web-DIR, not in a cusotms DIR on the Server you'd like.
For intro file you can set ../../custom-nr/intro.mp3 (starting from web dir) and move to your DIR, but for fallback file thats not possbile, only subdirs under the "web-dir".
Web- and Admin are shared for all running ICEcastbut customers specific files like config.xml, intro.mp3 (and also fallback.mp3) are in home-dirs.
I thought there's maybe an parameter (as in SHOUTcast) where you can set "not to disconnect listeners autoamatically" when source is not longer down than the configured duration in seconds.
Regards, Adam |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sat Aug 19, 2006 2:01 pm Post subject: |
|
|
While webroot can be shared, we don't impose that, in fact for any cases where there are custom on-demand files a per-customer webroot is often the best approach.
There is no parameter like you suggested in icecast for a very good reason. It's a waste of resources which often means the listener doesn't receive anything when that situation occurs and they often disconnect themselves anyway.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sat Aug 19, 2006 4:52 pm Post subject: |
|
|
Ok Karl, thx for your comments and suggestions.
If there is a bigger request for using fallback function, I will make an indivdual copy of the web-dir for each user.
Regards from Germany, Adam |
|
| Back to top |
|
 |
|